[
https://issues.apache.org/jira/browse/PHOENIX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073861#comment-14073861
]
Jesse Yates commented on PHOENIX-1107:
--------------------------------------
The other option is to write out own WAL listener for replication. It would
take into account the index rows and then ignore updating the replication
scopes. However, that means we need start to diverge from HBase (again, could
do a patch so future versions don't need our custom replicator, but use this
one for released versions).
Code-wise, its a pretty small change (subclass Replication.java and override
visitLogEntryBeforeWrite) but functionally adds overhead as Phoenix users then
need to update their configs and roll their cluster, diverging from the
'standard' HBase configs...At least I think that's all that would be required.
> 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)
