[
https://issues.apache.org/jira/browse/PHOENIX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073959#comment-14073959
]
James Taylor commented on PHOENIX-1107:
---------------------------------------
First impression is that it looks like one big hack (no offense :-) ). Is there
a missing feature in HBase that would help us here?
Also, regarding the destination system only getting the table edits and not
needing the index edits: what APIs does the replay go through? I'm guessing
they're HBase APIs, not Phoenix APIs in which case the index updates wouldn't
happen.
What would a patch look like if we did replicate the index updates?
> Support mutable indexes over replication
> ----------------------------------------
>
> Key: PHOENIX-1107
> URL: https://issues.apache.org/jira/browse/PHOENIX-1107
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 3.1, 4.1
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Attachments: phoenix-1107-3.0.v0
>
>
> Mutable indexes don't support usage with replication. For starters, the
> replication WAL Listener checks the family of the edits, which can throw a
> NPE for the IndexedKeyValue
--
This message was sent by Atlassian JIRA
(v6.2#6252)
