[ https://issues.apache.org/jira/browse/HBASE-8317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Corgan updated HBASE-8317: ------------------------------- Attachment: HBASE-8317-v1.patch > Seek returns wrong result with PREFIX_TREE Encoding > --------------------------------------------------- > > Key: HBASE-8317 > URL: https://issues.apache.org/jira/browse/HBASE-8317 > Project: HBase > Issue Type: Bug > Affects Versions: 0.95.0 > Reporter: chunhui shen > Assignee: chunhui shen > Attachments: HBASE-8317-v1.patch, hbase-trunk-8317.patch > > > TestPrefixTreeEncoding#testSeekWithFixedData from the patch could reproduce > the bug. > An example of the bug case: > Suppose the following rows: > 1.row3/c1:q1/ > 2.row3/c1:q2/ > 3.row3/c1:q3/ > 4.row4/c1:q1/ > 5.row4/c1:q2/ > After seeking the row 'row30', the expected peek KV is row4/c1:q1/, but > actual is row3/c1:q1/. > I just fix this bug case in the patch, > Maybe we can do more for other potential problems if anyone is familiar with > the code of PREFIX_TREE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira