Csaba Ringhofer has uploaded this change for review. ( http://gerrit.cloudera.org:8080/18583
Change subject: IMPALA-11335: allocate WriteId before taking locks during INSERT to ACID tables ...................................................................... IMPALA-11335: allocate WriteId before taking locks during INSERT to ACID tables It turned out that in case of INSERT HMS uses the writeId during lock creation to save it and use it to cleanup aborted / timeouted transactions. See the Jira for more details. Testing: - It is tricky to test this, so no new test was added. Hive should check whether there is already a new writeId for a table during lock creation and return an error if not - this would ensure that the correct behavior of Impala is tested. Change-Id: Ic13b8822662474a0d2d4d1a31f12745159c758f4 --- M fe/src/main/java/org/apache/impala/service/Frontend.java 1 file changed, 2 insertions(+), 2 deletions(-) git pull ssh://gerrit.cloudera.org:29418/Impala-ASF refs/changes/83/18583/1 -- To view, visit http://gerrit.cloudera.org:8080/18583 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: Ic13b8822662474a0d2d4d1a31f12745159c758f4 Gerrit-Change-Number: 18583 Gerrit-PatchSet: 1 Gerrit-Owner: Csaba Ringhofer <csringho...@cloudera.com>
