[
https://issues.apache.org/jira/browse/ACCUMULO-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782518#comment-13782518
]
Corey J. Nolet commented on ACCUMULO-1732:
------------------------------------------
It would be nice to have an integration test suit to verify behavior like this.
I'm not seeing a good spot for putting an AccumuloInputFormatIT. Any ideas? I'm
thinking a new package in the test module but maybe I'm overlooking something.
> Resolve table name to table id once in Accumulo input format
> ------------------------------------------------------------
>
> Key: ACCUMULO-1732
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1732
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Keith Turner
> Assignee: Corey J. Nolet
> Priority: Minor
>
> AccumuloInputFormat (and I suspect AccumuloOutputFormat) sends the table name
> to each mapper. The mapper uses this table name to create a scanner. In the
> case of the following events a map reduce job could read from two different
> table ids.
> # start M/R job reading table A
> # rename table A (tableId=1) to table C
> # rename table B (tableId=2) to table A
> If the input format passed table id 1 to the mappers, then the renames would
> not cause a problem.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
