You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "ctubbsii (via GitHub)" <gi...@apache.org> on 2023/10/20 08:32:09 UTC
Re: [I] Place limit on fence begin and end row size. [accumulo]
ctubbsii commented on issue #3795:
URL: https://github.com/apache/accumulo/issues/3795#issuecomment-1772309614
The actual fencing is going to follow the tablet split points, unless there's some other source for the fencing ranges that I don't know about... ? If they follow the split points, then there's no reason to believe any problems due to size are going to be more substantial than the normal tablet split point sizes, right?
One size optimization is to omit specifying the range when the range is the current tablet's range. If the range is empty, the current tablet is enough to specify its bounds. It only needs to be specified when there is a range that falls within the bounds (from a previous merge). This will make fencing ranges in metadata unnecessary for the vast majority of files. Only files that were previously involved in a merge would actually need to have a fencing range serialized in their metadata.
--
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: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org