[jira] Updated: (HBASE-2756) MetaScanner.metaScan doesn't take configurations

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated HBASE-2756:
--------------------------------------

    Attachment: HBASE-2756.patch

Patch that passes the configuration object to HTable, and that adds a unit test for the multi clusters case. It also requires a fix that will be included soon in HBASE-2741.

> MetaScanner.metaScan doesn't take configurations
> ------------------------------------------------
>
>                 Key: HBASE-2756
>                 URL: https://issues.apache.org/jira/browse/HBASE-2756
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.21.0
>
>         Attachments: HBASE-2756.patch
>
>
> HBASE-2468 added a bunch of code in MetaScanner.metaScan, and this particular line is wrong:
> {code}
> +    // if row is not null, we want to use the startKey of the row's region as
> +    // the startRow for the meta scan.
> +    if (row != null) {
> +      HTable metaTable = new HTable(HConstants.META_TABLE_NAME);   <<<<<<<<<<<<<<<<<
> +      Result startRowResult = metaTable.getRowOrBefore(startRow,
> +          HConstants.CATALOG_FAMILY);
> +      if (startRowResult == null) {
> {code}
> If the user specified any new configuration in his code, like ZK's parent znode, then it will miss it. This should use the HTable constructor that takes a Configuration and pass the one it already has.
> I found this with my TestReplication test in HBASE-2223.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.