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.

Sign up for GitHub

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

Jump to bottom

Fallback to atomicOp for deletion processors when it cannot be batch #4272

Open
wey-gu opened this issue May 20, 2022 · 0 comments
Open

Fallback to atomicOp for deletion processors when it cannot be batch #4272

wey-gu opened this issue May 20, 2022 · 0 comments
Labels
type/enhancement Type: make the code neat or more efficient

Comments

@wey-gu
Copy link
Contributor

wey-gu commented May 20, 2022

Introduction
Is it feasible to do exactly the same change to insert for delete cases as it was in #3926 , else, deletion should be retried from client-side when conflict error encountered, which is inconsistent to our changes applied on insert cases.

Thanks!

ref: https://nebulagraph.slack.com/archives/CSK0RSBFT/p1652860674390819

Contents

Related work

#3926
@wey-gu wey-gu added the type/enhancement Type: make the code neat or more efficient label May 20, 2022
@wey-gu wey-gu mentioned this issue May 21, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/enhancement Type: make the code neat or more efficient
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wey-gu