[
https://issues.apache.org/jira/browse/HBASE-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113371#comment-14113371
]
Andrew Purtell commented on HBASE-11837:
----------------------------------------
This one is bizarre. I can reproduce the problem. If I change
CoprocessorEnvironment#getTable to simply do a 'new HTable(tableName)' that
doesn't fix the problem, but as far as I can tell will do what HTablePool
would. If I uncomment James' workaround in the Phoenix code indeed using
HTablePool to create a table does work around the issue.
> Scanner from RegionCoprocessorEnvironment.getTable(TableName) returns no
> local data
> -----------------------------------------------------------------------------------
>
> Key: HBASE-11837
> URL: https://issues.apache.org/jira/browse/HBASE-11837
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
> Affects Versions: 0.98.4
> Reporter: James Taylor
> Attachments: PHOENIX-1208-torepro.patch
>
>
> Might be fixed as a byproduct of the fix for HBASE-11766.
> Here's what I'm seeing:
> - From an endpoint coprocessor on SYSTEM.CATALOG table
> - Rows exist in the table, but are all in a single region
> - Scan is a new, empty scan created like this: new Scan()
> - The following scanner *does* return data:
> {code}
> RegionScanner scanner = region.getScanner(scan);
> {code}
> - The following scanner *does not* return any data:
> {code}
> HTableInterface hTable = env.getTable(region.getTableDesc().getTableName());
> {code}
> - The following scanner *does* return data:
> {code}
> HTablePool pool = new HTablePool (env.getConfiguration(),1);
> HTableInterface hTable = pool.getTable("SYSTEM.CATALOG");
> {code}
> [~jeffreyz], [~apurtell]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
