[
https://issues.apache.org/jira/browse/PHOENIX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154078#comment-14154078
]
Jesse Yates commented on PHOENIX-1107:
--------------------------------------
I don't think any form of this solution is really a good idea. I'd much rather
say "please upgrade to 0.98 and Phoenix 4.x" than want to support a hack of
this nature. The proposed solution was a sketch of a possibility, but the
discussion here has lead me to believe that its probably not a great idea to
actually pursue going forward. The problem is not that it doesn't work, but
rather that supporting it becomes very painful over time.
Unless you (or some other users) are currently running 0.94 + Phoenix 3.x with
indexes and really really want replication, I'd say we should just leave this
issue as-is.
That said, your changes look pretty good, but that's just based on a visual
inspection, not anything really rigorous (which is what we have to do if we
want to check this in).
> 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.V1.patch, phoenix-1107-3.0.v0,
> phoenix-1107-master-passes.patch
>
>
> 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.3.4#6332)
