-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Feature Request: Support mergeSchema option when using Spark MERGE INTO #5556
Comments
For reference, the issue here is that the user wants to be able to use I'm not sure of a way to support that presently. If somebody does know, please comment 🙂 |
It would be great help if someone could help in achieving this functionality.. We are struggling to do this thing manually... |
Just an FYI but I would update the title to be The hints might not be something we can add without changing Spark, but the core of the idea is that you need Removing the implementation constraint from the title might attract more eyeballs / bring more ideas to the table (as ultimately you don’t care about anything other than needing |
Also, what about a table property? Does the table experience writes where you explicitly do not want Generally, I think For the long run, I’m going to bring up adding a merge into API to the dataframe / dataset API in Spark. But that could take a while. We might be able to provide implicit classes so that it’s do-able using the dataframe API in just Iceberg, but in the long run that should be moved to Spark (though that doesn’t solve your immediate problem, I know). |
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' |
Not stale |
This is definitely something we'd be interested in - We are doing something similar with Glue and would like to be able to support schema evolution with a This is a very similar architecture to what we're doing - https://aws.amazon.com/blogs/big-data/automate-replication-of-relational-sources-into-a-transactional-data-lake-with-apache-iceberg-and-aws-glue/ |
Reopening due to interest in this |
@kbendick is this still on your radar? If not could you give me some direction on where I could start to look at. |
Any updates on this feature? I also have a strong interest in iceberg providing this solution. |
Anyone who would like to work on the issue is welcome to, there is currently no one I know working on it. |
Delta Lake has the ability to set |
Is it still being worked on? It would be nice if we can have either:
|
Feature Request / Improvement
Hi Team,
I am using Iceberg in my project and I found a big thing which is missing from Iceberg which is easily available in Apache Hudi and Deltalake that is "merge schema". If possible this feature need to added into the Iceberg. I am attaching my last ticket which is explaining the problem that I am facing.Please find the below ticket for the refrence.
#5548
@rdblue any thoughts on this?
Query engine
Spark
The text was updated successfully, but these errors were encountered: