[
https://issues.apache.org/jira/browse/PHOENIX-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097552#comment-14097552
]
Jesse Yates commented on PHOENIX-1166:
--------------------------------------
I'm asking that we don't commit this until someone actually finds out why this
is necessary.
I can see the need for a workaround if its really that big of an improvement
(with a TODO, as you mentioned), but that big of a gap seems like something
systemically wrong (which would also mean an HBase JIRA).
Also, what's the impact for non-local, mutable secondary indexes when the
target region moves between the lookup and the write? I don't see any error
handling for that case, which could cause false failures.
> Avoid HTable creation in coprocessors to write into local index table
> ---------------------------------------------------------------------
>
> Key: PHOENIX-1166
> URL: https://issues.apache.org/jira/browse/PHOENIX-1166
> Project: Phoenix
> Issue Type: Bug
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Fix For: 5.0.0, 4.1
>
> Attachments: PHOENIX-1166.patch
>
>
> Since data table regions and local index regions colocated, we can get index
> region directly from RS online regions and write to it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
