Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-5969

HRI.getRegionName/AsString are inconsistent for regions with the old encoding scheme

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      HRI.getRegionName and getRegionNameAsString don't give consistent results for regions created with the old encoding scheme. See Aravind's comment in HBASE-5929 on how a region was appended with ".1290583321" when its HRI was queried with getRegionNameAsString and, once passed to HBA, wasn't able to compact it (I checked .META. and it doesn't have that last part so it must come from getRegionName).

      This one might be a little hard to fix if we're already dependent on the broken behavior of getRegionName.

        Activity

        Hide
        posix4e Alex Newman added a comment -

        Does it make sense to focus on just fixing getRegionNameAsString for the META entry in the root table?

        Show
        posix4e Alex Newman added a comment - Does it make sense to focus on just fixing getRegionNameAsString for the META entry in the root table?
        Hide
        jdcryans Jean-Daniel Cryans added a comment -

        If it doesn't break anything, sure.

        Show
        jdcryans Jean-Daniel Cryans added a comment - If it doesn't break anything, sure.

          People

          • Assignee:
            Unassigned
            Reporter:
            jdcryans Jean-Daniel Cryans
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:

              Development