-
Notifications
You must be signed in to change notification settings - Fork 291
Incremental Changelog Scan #240
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
Comments
This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible. |
This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale' |
Reopening issue as it was marked stale. |
This would be great. In the meantime I naively hacked this to get newly appended rows -- seems to work for my use case. iceberg-python/pyiceberg/table/__init__.py Lines 1929 to 1937 in 861c563
|
Feature Request / Improvement
Hello,
The Java API supports performing a table scan for just the incremental changes between two snapshots: https://iceberg.apache.org/javadoc/latest/org/apache/iceberg/IncrementalChangelogScan.html
How feasible would it be to support the same in PyIceberg? Are there any special considerations to make?
Thanks!
The text was updated successfully, but these errors were encountered: