[
https://issues.apache.org/jira/browse/PHOENIX-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid resolved PHOENIX-329.
----------------------------------
Resolution: Fixed
Bulk resolve of closed issues imported from GitHub. This status was reached by
first re-opening all closed imported issues and then resolving them in bulk.
> A few issues of Delete when conn.autocommit is set to off
> ---------------------------------------------------------
>
> Key: PHOENIX-329
> URL: https://issues.apache.org/jira/browse/PHOENIX-329
> Project: Phoenix
> Issue Type: Task
> Reporter: Raymond Liu
>
> Take following code for example
> conn.setAutoCommit(false);
> query = "UPSERT INTO test_table(row, col1) VALUES('row1', 2)";
> statement = conn.prepareStatement(query);
> statement.executeUpdate();
> query = "DELETE FROM test_table WHERE row='row1'";
> statement = conn.prepareStatement(query);
> statement.executeUpdate();
> conn.commit();
> issue1 : after operation row1 will be added. for the DELETE operation is not
> run at all due to scan do not return row1 which is not commited yet.
> issue2: if row1 is already there before these op. then it will lead to
> exception. in MutationState.join(), For there are bugs in the code when
> replace new row value, when new value is empty for a row which means delete
> row, it should skip the join procedure and use new value directly.
> Will provide a patch for issue2
--
This message was sent by Atlassian JIRA
(v6.2#6252)
