[jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907365#action_12907365 ] Steven Noels commented on HBASE-1485: - Thanks all! > Wrong or indeterminate behavior when there are duplicate versions of a column > - > > Key: HBASE-1485 > URL: https://issues.apache.org/jira/browse/HBASE-1485 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.20.0 >Reporter: Jonathan Gray >Assignee: Pranav Khaitan > Fix For: 0.90.0 > > Attachments: HBASE-1485-v9.patch, TestCellUpdates.java > > > As of now, both gets and scanners will end up returning all duplicate > versions of a column. The ordering of them is indeterminate. > We need to decide what the desired/expected behavior should be and make it > happen. > Note: It's nearly impossible for this to work with Gets as they are now > implemented in 1304 so this is really a Scanner issue. To implement this > correctly with Gets, we would have to undo basically all the optimizations > that Gets do and making them far slower than a Scanner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906942#action_12906942 ] Pranav Khaitan commented on HBASE-1485: --- This is resolved. The fixed patch and explanation for this has been posted at https://review.cloudera.org/r/780/. Let me know if there are further questions. Thanks again Evert, for making us aware of this case! > Wrong or indeterminate behavior when there are duplicate versions of a column > - > > Key: HBASE-1485 > URL: https://issues.apache.org/jira/browse/HBASE-1485 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.20.0 >Reporter: Jonathan Gray >Assignee: Pranav Khaitan > Fix For: 0.90.0 > > Attachments: TestCellUpdates.java > > > As of now, both gets and scanners will end up returning all duplicate > versions of a column. The ordering of them is indeterminate. > We need to decide what the desired/expected behavior should be and make it > happen. > Note: It's nearly impossible for this to work with Gets as they are now > implemented in 1304 so this is really a Scanner issue. To implement this > correctly with Gets, we would have to undo basically all the optimizations > that Gets do and making them far slower than a Scanner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906856#action_12906856 ] Evert Arckens commented on HBASE-1485: -- I understand that the delete case isn't related to this jira. It would have been better to put it in a separate unit test. > Wrong or indeterminate behavior when there are duplicate versions of a column > - > > Key: HBASE-1485 > URL: https://issues.apache.org/jira/browse/HBASE-1485 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.20.0 >Reporter: Jonathan Gray >Assignee: Pranav Khaitan > Fix For: 0.90.0 > > Attachments: TestCellUpdates.java > > > As of now, both gets and scanners will end up returning all duplicate > versions of a column. The ordering of them is indeterminate. > We need to decide what the desired/expected behavior should be and make it > happen. > Note: It's nearly impossible for this to work with Gets as they are now > implemented in 1304 so this is really a Scanner issue. To implement this > correctly with Gets, we would have to undo basically all the optimizations > that Gets do and making them far slower than a Scanner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906850#action_12906850 ] Pranav Khaitan commented on HBASE-1485: --- Thanks Evert, for point this out. As Jonathan mentioned, the behavior remains the same for the delete case. I will look more into the flushing case and keep you updated. > Wrong or indeterminate behavior when there are duplicate versions of a column > - > > Key: HBASE-1485 > URL: https://issues.apache.org/jira/browse/HBASE-1485 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.20.0 >Reporter: Jonathan Gray >Assignee: Pranav Khaitan > Fix For: 0.90.0 > > Attachments: TestCellUpdates.java > > > As of now, both gets and scanners will end up returning all duplicate > versions of a column. The ordering of them is indeterminate. > We need to decide what the desired/expected behavior should be and make it > happen. > Note: It's nearly impossible for this to work with Gets as they are now > implemented in 1304 so this is really a Scanner issue. To implement this > correctly with Gets, we would have to undo basically all the optimizations > that Gets do and making them far slower than a Scanner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906849#action_12906849 ] Evert Arckens commented on HBASE-1485: -- The attached test TestCellUpdates.java also intializes a new HBaseTestingUtility for each test method. Setting this up only once for the whole test class causes issues when triggering the major compaction which I haven't been able to pinpoint yet. > Wrong or indeterminate behavior when there are duplicate versions of a column > - > > Key: HBASE-1485 > URL: https://issues.apache.org/jira/browse/HBASE-1485 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.20.0 >Reporter: Jonathan Gray >Assignee: Pranav Khaitan > Fix For: 0.90.0 > > Attachments: TestCellUpdates.java > > > As of now, both gets and scanners will end up returning all duplicate > versions of a column. The ordering of them is indeterminate. > We need to decide what the desired/expected behavior should be and make it > happen. > Note: It's nearly impossible for this to work with Gets as they are now > implemented in 1304 so this is really a Scanner issue. To implement this > correctly with Gets, we would have to undo basically all the optimizations > that Gets do and making them far slower than a Scanner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906847#action_12906847 ] Jonathan Gray commented on HBASE-1485: -- Great stuff Evert. This is really helpful. In the delete case, this is still the expected behavior. This patch doesn't change anything with regards to insertions past deletions. > Wrong or indeterminate behavior when there are duplicate versions of a column > - > > Key: HBASE-1485 > URL: https://issues.apache.org/jira/browse/HBASE-1485 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.20.0 >Reporter: Jonathan Gray >Assignee: Pranav Khaitan > Fix For: 0.90.0 > > Attachments: TestCellUpdates.java > > > As of now, both gets and scanners will end up returning all duplicate > versions of a column. The ordering of them is indeterminate. > We need to decide what the desired/expected behavior should be and make it > happen. > Note: It's nearly impossible for this to work with Gets as they are now > implemented in 1304 so this is really a Scanner issue. To implement this > correctly with Gets, we would have to undo basically all the optimizations > that Gets do and making them far slower than a Scanner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906620#action_12906620 ] Pranav Khaitan commented on HBASE-1485: --- Patch for this issue posted at https://review.cloudera.org/r/780/ > Wrong or indeterminate behavior when there are duplicate versions of a column > - > > Key: HBASE-1485 > URL: https://issues.apache.org/jira/browse/HBASE-1485 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.20.0 >Reporter: Jonathan Gray >Assignee: Pranav Khaitan > Fix For: 0.90.0 > > > As of now, both gets and scanners will end up returning all duplicate > versions of a column. The ordering of them is indeterminate. > We need to decide what the desired/expected behavior should be and make it > happen. > Note: It's nearly impossible for this to work with Gets as they are now > implemented in 1304 so this is really a Scanner issue. To implement this > correctly with Gets, we would have to undo basically all the optimizations > that Gets do and making them far slower than a Scanner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905772#action_12905772 ] stack commented on HBASE-1485: -- Hurray! > Wrong or indeterminate behavior when there are duplicate versions of a column > - > > Key: HBASE-1485 > URL: https://issues.apache.org/jira/browse/HBASE-1485 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.20.0 >Reporter: Jonathan Gray >Assignee: Pranav Khaitan > Fix For: 0.90.0 > > > As of now, both gets and scanners will end up returning all duplicate > versions of a column. The ordering of them is indeterminate. > We need to decide what the desired/expected behavior should be and make it > happen. > Note: It's nearly impossible for this to work with Gets as they are now > implemented in 1304 so this is really a Scanner issue. To implement this > correctly with Gets, we would have to undo basically all the optimizations > that Gets do and making them far slower than a Scanner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877589#action_12877589 ] ryan rawson commented on HBASE-1485: Right now Get = 1 row Scans, thus making this issue at least twice as easy :-) > Wrong or indeterminate behavior when there are duplicate versions of a column > - > > Key: HBASE-1485 > URL: https://issues.apache.org/jira/browse/HBASE-1485 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.20.0 >Reporter: Jonathan Gray > Fix For: 0.21.0 > > > As of now, both gets and scanners will end up returning all duplicate > versions of a column. The ordering of them is indeterminate. > We need to decide what the desired/expected behavior should be and make it > happen. > Note: It's nearly impossible for this to work with Gets as they are now > implemented in 1304 so this is really a Scanner issue. To implement this > correctly with Gets, we would have to undo basically all the optimizations > that Gets do and making them far slower than a Scanner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
