Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New FileActionsVisitor and NonFileActionsVisitor visitors #737

Open
sebastiantia opened this issue Mar 11, 2025 · 0 comments · May be fixed by #738
Open

New FileActionsVisitor and NonFileActionsVisitor visitors #737

sebastiantia opened this issue Mar 11, 2025 · 0 comments · May be fixed by #738
Labels
enhancement New feature or request

Comments

@sebastiantia
Copy link
Collaborator

sebastiantia commented Mar 11, 2025

Please describe why this is necessary.

These changes are part of checkpoint write support.

To build a V1 checkpoint, we need to:

  1. Perform Log Segment Replay to retrieve all action batches for the table's state
  2. Each batch has to be scanned and filtered to only include actions to be written to the V1 checkpoint file.

The FileActionsVisitor and NonFileActionsVisitor visitors are both leveraged on every batch.

The reason the functionality is split into two separate visitors is for extensibility purposes regarding V2 checkpoints

Describe the functionality you are proposing.

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
1 participant