-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Kernel][Snapshots] Kernel Table API to read arbitrary snapshots #2581
Comments
Hey @abhishekrb19 I'm actually working on this now, I'll link you on the PR when it's ready. Cross-linking this with #2275 for reference. |
Thank you, @allisonport-db! Looking forward to that functionality. |
@abhishekrb19 can i ask what is your interest this feature? or Kernel in general? Are you planning to integrate with Kernel? |
@abhishekrb19 Actually, never mind my questions, I looked at the PR apache/druid#15755 you linked. This is amazing, you have already used Delta Kernel to integrate Delta Lake support in Apache Druid! Can I ask how and when this support is going to be released? |
@tdas, thanks! We plan to include this in the upcoming Druid 29 release (date TBD). |
@abhishekrb19 thank you for the info. in 3.1, we made a few API changes, and added data skipping support. are you interested in using 3.1? If so, we can chat and help out. Would love to get your feedback in general about using Kernel the APIs. |
@tdas, yes, 3.1.0 looks exciting, the PR to upgrade the connector in Druid is here: apache/druid#15842 |
Resolved by #2607 |
Feature request
Which Delta project/connector is this regarding?
Related to the Druid-Delta Lake connector apache/druid#15755. Currently in 3.0.0, the
Table
interface only supports reading the latest snapshot. I see the same for the pre-release version 3.1.0. How feasible would it be to add support for reading arbitrary snapshots in the Delta Kernel?Willingness to contribute
The Delta Lake Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature?
The text was updated successfully, but these errors were encountered: