keith-turner commented on issue #5014:
URL: https://github.com/apache/accumulo/issues/5014#issuecomment-2495554338
> I think this is fine but I'm wondering how we make it easy for a user to
mark splits. We might need a new command line tool or something to make it
simple to mark them. In fact, I could use a use case where a user decides maybe
there's some tablets they don't want merged (even if originally system created)
and they could use the tool not just for upgrades but for marking those to
prevent merging too.
Also wondering about unmarking them. The TabletInformation API couild be
used to get information about the markings. Then just need to figure out what
the APIs and shell commands are for marking and unmarking them. Could be
similar to APIs and shell commands for makring tablet availability.
> This could depend on if we ever plan to have more than 2 types at some
point.
Maybe instead of marking how a split was created we mark a splits
mergability. That could have the following three states.
1. ALWAYS : User or system initiated merge can merge this split away
2. USER : Only a user initiated merge can merge this split away
3. NEVER : Nothing can merge this split away and if a user merge operations
is initiated on it then the merge operation would fail
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
