[Feature] It may be a memory bottleneck when read all manifests.
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 396
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.
### Motivation
Snapshot.dataManifests() will read all the ManifestFileMeta in memory . If there are too many files in a table ,it may cause oom. And when ManifestFileMeta.merge() to merge the manifests , the merge map is also a memory container , which will case the same problem.
I think we can use a spillable container to save manifests .
### Solution
_No response_
### Anything else?
_No response_
### Are you willing to submit a PR?
- [X] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing Snapshot.dataManifests() and ManifestFileMeta.merge(), the entry points named in the issue, to see where all manifest metadata and the merge map are held in memory. Done should address the reported out-of-memory risk for tables with many files; the issue names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100