-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Are there plans to support merge on read mode #276
Comments
Hello @397090770 Today delta can solve merge on read use cases. In order to accomplish this, we create two tables and one view. |
@joewiden - are you proposing a solution - by layering on top of Delta lake? or are these Delta lake constructs? I think, the solution you proposed CANNOT be a general-purpose solution for MERGE ON READ due to the below reasons:
I think your solution - caters to a very specific scenario - that you wanted to solve. Pls let me know if that is not the case. I believe, generally, these intricate data problems are solved at the database (here big data lake) layer - not on the application layer! |
Any difference in Delta Lake 2.x ? |
Hi @dohongdayi - no, Delta 2.1 does not yet natively support MOR. The good news is that one of MOR's dependencies, deletion vectors, is on the H2 roadmap here: #1307 if you'd like to push for this feature please add a comment and upvote it :) |
四年了 还不支持? |
For information, Deletion Vectors for Read operations are supported since Delta Lake 2.3.0 (released April 2023). |
As we know, Delta Lake is currently a copy on write mode, this mode is useful for write less and read more scenarios, But it is not very friendly to write more and read less scenarios, So I want to know if there is such a plan to support read on merge mode.
The text was updated successfully, but these errors were encountered: