[jira] [Commented] (HBASE-8145) TestHCM flaky: java.lang.IllegalArgumentException: Row length is 0

["stack (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-8145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606762#comment-13606762 ] 

stack commented on HBASE-8145:
------------------------------

I have fix coming in hbase-7905 If null key, skips the row in the test.  In general null row should fail fast.  It just took a while weeding out all usages in tests (I think I have it now over in hbase-7905)
                
> TestHCM flaky: java.lang.IllegalArgumentException: Row length is 0
> ------------------------------------------------------------------
>
>                 Key: HBASE-8145
>                 URL: https://issues.apache.org/jira/browse/HBASE-8145
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.96.0
>            Reporter: nkeywal
>            Assignee: nkeywal
>            Priority: Trivial
>             Fix For: 0.96.0
>
>
> I will check for 0.95.
> {code}
>     for (HRegion region : regions) {
>       if (!region.getRegionInfo().getEncodedName().equals(toMove.getRegionInfo().getEncodedName())
>           && Bytes.BYTES_COMPARATOR.compare(region.getRegionInfo().getStartKey(), ROW_X) < 0) {
>         otherRow = region.getRegionInfo().getStartKey();
>         break;
>       }
>     }
> {code}
> We're likely to get sometimes the startKey of the first region here, and that's an empty byte array. This make the put creation to fail, since there is now (with HBASE-8101) a check on the empty rows at put creation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira