Introduce require_files for tracking the add files in table state #594
+119
−38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Since #454 dev is stopped. We aim to gradually address that issue.
Firstly, this PR. The changes introduces
require_files
which similar torequire_tombstones
, filters out any files if the flag is set tofalse
. Hence the table state will end up with metadata only. This is a perfect behavior for append only apps (like kafka delta ingest for example).Secondly, the catch is the how to create a checkpoint, because we need both adds & removes for that. One possible approach is a create checkpoint in another process, which is applicable. However we can omit that and do in process if we apply the work from #454. E.g. by operating on arrow/record batch objects to reduce memory usage / decentralization just enough to read/create checkpoint.
Thirdly, if 2nd step is successful, we can leverage that experience to finish/enhance the idea from #454
Related Issue(s)
A follow up of #445. But here we introduce ignoring of add files.