forked from apache/accumulo
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Single node META FATE data (apache#5127)
- Moved all the fate data for a single `META` transaction into a single ZK node - Pushed all the data into `NodeValue` (renamed to `FateData`) - Previously, `FateData` stored `TStatus`, `FateReservation`, and `FateKey`. Now additionally stores the `REPO` stack and `TxInfo`. - Status enforcement added to `MetaFateStore` (previously only possible for `UserFateStore`). - Moved `testFateInitialConfigCorrectness()` from `UserFateStoreIT` to `UserFateIT` - Renamed `UserFateStoreIT` to `UserFateStatusEnforcementIT` (now extends a new class `FateStatusEnforcementIT`) - Now only tests status enforcement (previously status enforcement + `testFateInitialConfigCorrectness()`) - Created `MetaFateStatusEnforcementIT` (extends `FateStatusEnforcementIT`) - Tests that the new status enforcement in `MetaFateStore` works - Created `FateStoreUtil`, moving the `createFateTable()` util here, created `MetaFateZKSetup` inner class here (the counterpart to `createFateTable()` for `UserFateStore` but sets up ZooKeeper for use in `MetaFateStore`) - Deleted `UserFateStoreIT`s (now `UserFateStatusEnforcementIT`) method `injectStatus` replacing with the existing `setStatus` which does the same thing - Changed `StackOverflowException` to instead be a `RuntimeException` (previously `Exception`) - Deleted unnecessary preexisting catch and immediate re-throw of a `StackOverflowException` in `MetaFateStore.FateTxStoreImpl.push(repo)` - Cleaned up and refactored `MetaFateStore` methods which mutate existing FateData; now reuse same pattern across these methods: all call new method `MetaFateStore.mutate()`
- Loading branch information
1 parent
e73a27d
commit 2abf5b1
Showing
16 changed files
with
811 additions
and
573 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.