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

Require more batch operations for TransactionClient #327

Open
blacktear23 opened this issue Jan 16, 2022 · 1 comment
Open

Require more batch operations for TransactionClient #327

blacktear23 opened this issue Jan 16, 2022 · 1 comment
Labels
enhancement New feature or request good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Comments

@blacktear23
Copy link

Require more batch operations for TransactionClient such as RawClient did. Such as:

  • batch_put
  • batch_scan
  • batch_delete
  • delete_range
@ekexium
Copy link
Collaborator

ekexium commented Jan 17, 2022

Hi, do you need them in your application?

batch_scan in transaction API is not supported by TiKV. If you really want it, please submit a feature request to tikv/tikv.

For optimistic transactions, batch_delete and batch_put are equivalent to multiple deletes and puts .
For pessimistic transactions, a more efficient way is first lock_keys and then do multple deletes or puts. Maybe we could provide an friendlier interface to do this.

There exists a delete_range request supported by TiKV, and client-rust hasn't implemented it.

@ekexium ekexium added enhancement New feature or request good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

2 participants