cshannon commented on issue #5014: URL: https://github.com/apache/accumulo/issues/5014#issuecomment-2495492062
@keith-turner - I've started to look into this and prototype something with a new column qual that will be added to the [split](https://github.com/apache/accumulo/blob/676989a1e39dbbaf2ff8e2e881e239c5b2a839b8/core/src/main/java/org/apache/accumulo/core/metadata/schema/MetadataSchema.java#L438) family that was added and a few questions come to mind on how we want to handle marking the tablets: 1. Should we always require a split type to be set or is absent valid? 2. This relates to my first question and I'm wondering if it makes sense to always store the split type (either user or system) or if it makes more sense to just mark a tablet if it's user generated and for system splits there would just be an absent marker. This could depend on if we ever plan to have more than 2 types at some point. 3. For new tables I was thinking we'd either just mark them as system or absent depending on if absent is valid. For merges I am guessing we'd do the same? after the merge mark it as system generated or unset it etc. -- 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]
