apache / apache/accumulo

Replace AFS.verifyReserved with a condition

Open
#4,908 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
1.2k
Forks
487
Avg merge
4d 5h
Merged PRs (30d)
13

Description

**Is your feature request related to a problem? Please describe.**
With the changes from https://github.com/apache/accumulo/pull/4524/, reservations are now indicated in a column for UserFateStore. For writes like push(), pop(), etc. that require the transaction to be reserved, could instead add a condition to the FateMutator that ensures the FateId is reserved.

**Describe the solution you'd like**
A new method added to FateMutator that adds the condition that the FateId is reserved: `FateMutator requireReserved();`. verifyReserved() would no longer be needed for UserFateStore, but would still be needed for MetaFateStore.

This should wait until after https://github.com/apache/accumulo/issues/4907 is completed

Contributor guide

Open the contributing guide

Research direction

Start by reading the FateMutator, UserFateStore, and MetaFateStore code around requireReserved() and verifyReserved(), then review the prerequisite issue 4907. Done means UserFateStore uses a reservation condition for operations such as push() and pop(), while MetaFateStore still uses verifyReserved().

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
databases, distributed-systems
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.