Metadata constraint checker makes incorrect assumption about location
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
**Describe the bug**
In MetadataConstraints it [assumes](https://github.com/apache/accumulo/blob/ab996d0d26df4b2ed2c1874289d5b785ecbe2686/server/base/src/main/java/org/apache/accumulo/server/constraints/MetadataConstraints.java#L311-L315) that when a location column is seen that the entire tablet is being copied. Looking in the 4.0.0 code this does not appear to be the case, it may not be the case in earlier versions.
**Expected behavior**
The code that makes this assumption should be removed because it allows odd metadata mutations through that are not expected.
Contributor guide
Research direction
Start in server/base/src/main/java/org/apache/accumulo/server/constraints/MetadataConstraints.java, especially lines 311-315, and trace how location columns are handled. Compare that behavior with the 4.0.0 code referenced in the issue; done means the incorrect full-table-copy assumption is removed and unexpected metadata mutations no longer pass through.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100