Details
-
Improvement
-
Status: Open
-
Trivial
-
Resolution: Unresolved
-
M4.5
-
None
-
None
Description
Some things we should do in the near future:
Now that we don't have leader/replica transactions we (likely) don't need the separation between transaction state and driver, so those two could consolidated.
A few other things which are common to all transactions, additionally, should moved to driver.
The code to set the timestamp on the response uses PB reflection and is smelly.
Attachments
Attachments
Issue Links
- is related to
-
KUDU-419 Evaluate necessity of various locks in transaction/transactiondriver
-
- In Progress
-