You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched in the issues and found nothing similar.
Motivation
When the partition expires, all ManifestEntry of the corresponding partition will be read into the memory, and then a new ManifestEntry whose FileKind is Delete will be generated. When the file of the expired partition is very large (hundreds of thousands), this will occupy a lot of memory.
In addition, when there may be conflicts in the commit, the files of the changed partitions will also be read into the memory for conflict checking.
Solution
We may not need to read it completely into memory, but return it in a stream.
Anything else?
No response
Are you willing to submit a PR?
I'm willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Search before asking
Motivation
When the partition expires, all
ManifestEntry
of the corresponding partition will be read into the memory, and then a newManifestEntry
whoseFileKind
isDelete
will be generated. When the file of the expired partition is very large (hundreds of thousands), this will occupy a lot of memory.In addition, when there may be conflicts in the commit, the files of the changed partitions will also be read into the memory for conflict checking.
Solution
We may not need to read it completely into memory, but return it in a stream.
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: