[jira] [Commented] (HIVE-18864) WriteId high water mark (HWM) is incorrect if ValidWriteIdList is obtained after allocating writeId by current transaction.

2018-03-06 Thread Eugene Koifman (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-18864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388106#comment-16388106 ] Eugene Koifman commented on HIVE-18864: --- Yes, you are right. If you "fix" writeID_H

[jira] [Commented] (HIVE-18864) WriteId high water mark (HWM) is incorrect if ValidWriteIdList is obtained after allocating writeId by current transaction.

2018-03-06 Thread Sankar Hariappan (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-18864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387519#comment-16387519 ] Sankar Hariappan commented on HIVE-18864: - [~ekoifman] That is precisely the prob

[jira] [Commented] (HIVE-18864) WriteId high water mark (HWM) is incorrect if ValidWriteIdList is obtained after allocating writeId by current transaction.

2018-03-05 Thread Eugene Koifman (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-18864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387081#comment-16387081 ] Eugene Koifman commented on HIVE-18864: --- Alternatively, write_HWM should always be s