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

[Feature] support delete record when merge engine is partial-update #3048

Closed
1 of 2 tasks
AkisAya opened this issue Mar 19, 2024 · 2 comments · Fixed by #3602
Closed
1 of 2 tasks

[Feature] support delete record when merge engine is partial-update #3048

AkisAya opened this issue Mar 19, 2024 · 2 comments · Fixed by #3602
Labels
enhancement New feature or request

Comments

@AkisAya
Copy link

AkisAya commented Mar 19, 2024

Search before asking

  • I searched in the issues and found nothing similar.

Motivation

for now it's not allowed to delete records in a partial-update table. even though a retract with sequence group is ok, but it is not a real delete action. suppose i want to execute a batch sql like delete from xxx_table where id = xx, it will throw an exception. i wonder if this delete feature is able to be complemented or not. if it can be achieved, will it be on the roadmap or if it can not be achieved can anyone explains a little bit why. thank you.

Solution

No response

Anything else?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@AkisAya AkisAya added the enhancement New feature or request label Mar 19, 2024
@AkisAya
Copy link
Author

AkisAya commented Mar 19, 2024

it seems i can use insert overwrite my_table select * from my_table where !(my_condition) as a workaournd of delete from my_table where <my_condition>

@JingsongLi
Copy link
Contributor

JingsongLi commented May 11, 2024

Now 0.8 Spark SQL supports COW Delete for partial-update.

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
Development

Successfully merging a pull request may close this issue.

2 participants