[
https://issues.apache.org/jira/browse/PHOENIX-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17065151#comment-17065151
]
Hudson commented on PHOENIX-5673:
---------------------------------
FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #3632 (See
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/3632/])
PHOENIX-5673 : The mutation state is silently getting cleared on the
(chinmayskulkarni: rev 788e7530b2224882df161e2353d3d8d9b7b6eec7)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixStatement.java
* (edit)
phoenix-core/src/test/java/org/apache/phoenix/execute/MutationStateTest.java
* (edit) phoenix-core/src/test/java/org/apache/phoenix/schema/MutationTest.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/exception/SQLExceptionCode.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/execute/MutationState.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/MutationStateIT.java
* (edit)
phoenix-core/src/test/java/org/apache/phoenix/index/IndexMaintainerTest.java
> The mutation state is silently getting cleared on the execution of any DDL
> --------------------------------------------------------------------------
>
> Key: PHOENIX-5673
> URL: https://issues.apache.org/jira/browse/PHOENIX-5673
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.15.0
> Reporter: Sandeep Guggilam
> Assignee: Siddhi Mehta
> Priority: Critical
> Labels: beginner, newbie
> Fix For: 4.16.0
>
> Attachments: PHOENIX-5673.4.x-HBase-1.3.v1.patch,
> PHOENIX-5673.4.x-HBase-1.3.v2.patch, PHOENIX-5673.4.x-HBase-1.3.v3.patch,
> PHOENIX-5673.4.x-HBase-1.3.v7.patch, PHOENIX-5673.master.v4.patch,
> PHOENIX-5673.master.v5.patch, PHOENIX-5673.master.v6.patch
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> When we execute any DDL statement, the mutations state is rolled back
> silently without informing the user. It should probably throw an exception
> saying that the mutation state is not empty when executing any DDL. See the
> below example:
>
> Steps to reproduce:
> create table t1 (pk varchar not null primary key, mycol varchar)
> upsert into t1 (pk, mycol) values ('x','x');
> create table t2 (pk varchar not null primary key, mycol varchar)
> When we try to execute the above statements and do a conn.commit() at the
> end, it would silently rollback the upsert statement when we execute the
> second create statement and you wouldn't see the ('x', 'x') values in the
> first table. Instead it should probably throw an exception saying that the
> mutation state is not empty
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
