[
https://issues.apache.org/jira/browse/ACCUMULO-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783599#comment-13783599
]
ASF subversion and git services commented on ACCUMULO-1732:
-----------------------------------------------------------
Commit 10b4eb8206ab4395ef2d4df375b52a7ffe77d655 in branch
refs/heads/ACCUMULO-391 from [~sonixbp]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=10b4eb8 ]
ACCUMULO-1732 Using table id in RangeInputSplit so that it can be resolved back
to "working" table name in mappers. Scanner uses the "working" table name while
everything else can still safely use the original configured table name.
> 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)
