[
https://issues.apache.org/jira/browse/PHOENIX-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662501#comment-16662501
]
Geoffrey Jacoby commented on PHOENIX-4988:
------------------------------------------
[~lhofhansl] - [~vincentpoon], [~tdsilva] and I were just talking about this
the other day when Vincent ran this bug by us. There's a ton of complexity that
Phoenix does when preparing mutable (i.e server-side) index updates, and much
of it is meant for perf optimization (by not sending redundant or obsolete
index updates to a remote RS) rather than for correctness.
Whether this optimization is worth the complexity is I think an open question.
> Incorrect index rowkey generated when updating only non-indexed columns after
> a delete
> --------------------------------------------------------------------------------------
>
> Key: PHOENIX-4988
> URL: https://issues.apache.org/jira/browse/PHOENIX-4988
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0
> Reporter: Vincent Poon
> Assignee: Vincent Poon
> Priority: Critical
> Fix For: 4.14.1
>
> Attachments: PHOENIX-4988.v1.4.x-HBase-1.4.patch,
> PHOENIX-4988.v1.master.patch
>
>
> The following steps result in an incorrect index rowkey being generated after
> an index update to a non-indexed column.
> create table test (k VARCHAR NOT NULL PRIMARY KEY, v1 VARCHAR, v2 VARCHAR)
> create index test_ind ON test (v2)
> upsert into test (k,v1,v2) VALUES ('testKey','v1_1','v2_1');
> delete from test;
> upsert into test (k,v1,v2) VALUES ('testKey','v1_2','v2_2');
> delete from test;
> upsert into test (k,v1) VALUES ('testKey','v1_3');
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
