[
https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431360#comment-16431360
]
Advertising
Sergey Soldatov commented on PHOENIX-4534:
------------------------------------------
Looks like those changes have been done in HBase 1.4 as well. And that's the
reason why master branch has a number of failures with indexes related to
upsert/delete/upsert row. [~elserj] that's one of the problems I mentioned
earlier.
> upsert/delete/upsert for the same row corrupts the indexes
> ----------------------------------------------------------
>
> Key: PHOENIX-4534
> URL: https://issues.apache.org/jira/browse/PHOENIX-4534
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Romil Choksi
> Assignee: Rajeshbabu Chintaguntla
> Priority: Critical
> Labels: HBase-2.0
> Fix For: 5.0.0
>
> Attachments: PHOENIX-4534.patch, PHOENIX-4534_v2.patch,
> PHOENIX-4534_v3.patch
>
>
> If we delete and upsert again the same row, the corresponding index has a
> null value.
> {noformat}
> 0: jdbc:phoenix:> create table a (id integer primary key, f float);
> No rows affected (2.272 seconds)
> 0: jdbc:phoenix:> create index i1 on a (f);
> No rows affected (5.769 seconds)
> 0: jdbc:phoenix:> upsert into a values (1,0.5);
> 1 row affected (0.021 seconds)
> 0: jdbc:phoenix:> select * from i1;
> +------+------+
> | 0:F | :ID |
> +------+------+
> | 0.5 | 1 |
> +------+------+
> 1 row selected (0.016 seconds)
> 0: jdbc:phoenix:> delete from a where id = 1;
> 1 row affected (0.009 seconds)
> 0: jdbc:phoenix:> select * from i1;
> +------+------+
> | 0:F | :ID |
> +------+------+
> +------+------+
> No rows selected (0.015 seconds)
> 0: jdbc:phoenix:> upsert into a values (1,0.5);
> 1 row affected (0.008 seconds)
> 0: jdbc:phoenix:> select * from i1;
> +-------+------+
> | 0:F | :ID |
> +-------+------+
> | null | 1 |
> +-------+------+
> 1 row selected (0.013 seconds)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
