[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471276#comment-16471276 ] Hudson commented on PHOENIX-4534: - ABORTED: Integrated in Jenkins build PreCommit-PHOENIX-Build #1879 (See [https://builds.apache.org/job/PreCommit-PHOENIX-Build/1879/]) PHOENIX-4534 upsert/delete/upsert for the same row corrupts the (ssa: rev 9566c78bd8aaace54aaebf34171f0d837ad7c0b7) * (edit) phoenix-core/src/main/java/org/apache/phoenix/hbase/index/covered/filter/ApplyAndFilterDeletesFilter.java PHOENIX-4534 upsert/delete/upsert for the same row corrupts the indexes (ssa: rev 0bcb872ba7bb74e3131a339440e38f9689471388) * (edit) phoenix-core/src/main/java/org/apache/phoenix/hbase/index/scanner/FilteredKeyValueScanner.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/hbase/index/covered/filter/ApplyAndFilterDeletesFilter.java * (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/MutableIndexIT.java > 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: 4.14.0, 5.0.0 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 4.15.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470796#comment-16470796 ] Sergey Soldatov commented on PHOENIX-4534: -- [~jamestaylor] That's 1.4/2.0 HBase specific. Not required for other branches. > 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: 4.14.0, 5.0.0 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 4.15.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470762#comment-16470762 ] James Taylor commented on PHOENIX-4534: --- Thanks, [~sergey.soldatov]! Is it required in any other 4.x branches? > 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: 4.14.0, 5.0.0 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 4.15.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470757#comment-16470757 ] Sergey Soldatov commented on PHOENIX-4534: -- [~jamestaylor] cherry-picked to master. Thanks for tracking it! > 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: 4.14.0, 5.0.0 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 4.15.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470696#comment-16470696 ] James Taylor commented on PHOENIX-4534: --- Was this committed, [~sergey.soldatov]? Is it specific to HBase 2.0? > 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: 4.14.0, 5.0.0 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 4.15.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462705#comment-16462705 ] James Taylor commented on PHOENIX-4534: --- I'm not seeing this committed to any of the 4.x or master branches. Is it needed, [~rajeshbabu], [~elserj], [~sergey.soldatov]? Sounds like it's need maybe only in master which is on HBase 1.4? > 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: 4.14.0, 5.0.0 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 4.14.0, 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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431394#comment-16431394 ] Josh Elser commented on PHOENIX-4534: - Great digging, Sergey! > 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: 4.14.0, 5.0.0 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 4.14.0, 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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431377#comment-16431377 ] Sergey Soldatov commented on PHOENIX-4534: -- Just confirmed that with v3 patch applied PartialIndexRebuilderIT#testWriteWhileRebuilding passed. > 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: 4.14.0, 5.0.0 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 4.14.0, 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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431360#comment-16431360 ] 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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337315#comment-16337315 ] Rajeshbabu Chintaguntla commented on PHOENIX-4534: -- Pushed to 5.x branch. > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336880#comment-16336880 ] Sergey Soldatov commented on PHOENIX-4534: -- LGTM. +1 > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335541#comment-16335541 ] Rajeshbabu Chintaguntla commented on PHOENIX-4534: -- In these four I am already looking into this {noformat} ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.LocalIndexSplitMergeIT {noformat} > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335537#comment-16335537 ] Rajeshbabu Chintaguntla commented on PHOENIX-4534: -- [~sergey.soldatov] Those failures are not related to the patch. They are failing even without patch as well. In the previous comments I have given 4 test cases failing always. {noformat} failed these unit tests: ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.LocalIndexSplitMergeIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.OrderByIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.RowValueConstructorIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.IndexMetadataIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.DefaultColumnValueIT {noformat} > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335508#comment-16335508 ] Sergey Soldatov commented on PHOENIX-4534: -- Not sure whether it's related or not, but got a failure on ongoing verify run on master: {noformat} [ERROR] Tests run: 24, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 136.754 s <<< FAILURE! - in org.apache.phoenix.end2end.DefaultColumnValueIT [ERROR] testDefaultIndexed(org.apache.phoenix.end2end.DefaultColumnValueIT) Time elapsed: 8.916 s <<< FAILURE! java.lang.AssertionError at org.apache.phoenix.end2end.DefaultColumnValueIT.testDefaultIndexed(DefaultColumnValueIT.java:978) {noformat} > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335478#comment-16335478 ] Sergey Soldatov commented on PHOENIX-4534: -- [~rajeshbabu] Great. Looks reasonable. Let me run some tests first. It should fix number of index related IT tests in 5.x branch and I really hope that would not break anything in master. > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335462#comment-16335462 ] Rajeshbabu Chintaguntla commented on PHOENIX-4534: -- [~sergey.soldatov] uploaded final patch with the tests including for multiple column families as well. Please review. > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332868#comment-16332868 ] Rajeshbabu Chintaguntla commented on PHOENIX-4534: -- [~sergey.soldatov] Here are the test failures in master branch which are failing without the patch also. Will do patch cleanup and upload new one. {noformat} [http://issues.apache.org/jira/secure/attachment/12906811/PHOENIX-4534_v2.patch] failed these unit tests: ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.LocalIndexSplitMergeIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.OrderByIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.RowValueConstructorIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.IndexMetadataIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.DefaultColumnValueIT {noformat} > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.0 > > Attachments: PHOENIX-4534.patch, PHOENIX-4534_v2.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332182#comment-16332182 ] Rajeshbabu Chintaguntla commented on PHOENIX-4534: -- uploaded patch works with master branch. Let's see all tests goes fine with the patch. > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.0 > > Attachments: PHOENIX-4534.patch, PHOENIX-4534_v2.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)
[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331767#comment-16331767 ] Sergey Soldatov commented on PHOENIX-4534: -- [~rajeshbabu] at first glance that would work. Possible we may want to get a patch for master branch and let jenkins check whether any of UT/IT fails? > 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 >Reporter: Romil Choksi >Assignee: Rajeshbabu Chintaguntla >Priority: Critical > Labels: HBase-2.0 > Fix For: 5.0 > > Attachments: PHOENIX-4534.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)