dethi commented on PR #6473: URL: https://github.com/apache/hbase/pull/6473#issuecomment-2480527441
> So the problem is allocation? > > What if we just store the region name some where so we do not need to construct it every time? That’s another option yes. To me it felt like the encoded name was a better attribute because it’s always the same size and short. Whereas the region name is highly dependent on the table data itself. The encoded region name is also what is used as a label/attribute in the per-region metrics. For example, our region name tend to be quite long because our rowkeys are arbitrary long filesystem-like path, encoded in a binary format (message pack). -- 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: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
