You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/11/06 06:18:01 UTC
[jira] [Resolved] (HBASE-13944) Prefix_Tree seeks to null if the
seeked Cell is greater than the last key in the file
[ https://issues.apache.org/jira/browse/HBASE-13944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-13944.
---------------------------
Resolution: Won't Fix
hbase-prefix-tree was removed in hbase2. Resolving as won't fix.
> Prefix_Tree seeks to null if the seeked Cell is greater than the last key in the file
> -------------------------------------------------------------------------------------
>
> Key: HBASE-13944
> URL: https://issues.apache.org/jira/browse/HBASE-13944
> Project: HBase
> Issue Type: Bug
> Components: prefixtree, Scanners
> Affects Versions: 1.0.0, 1.0.1, 1.1.0, 0.98.13, 1.0.1.1, 1.1.0.1
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Minor
> Fix For: 2.0.0
>
>
> When using any DBE other than Prefix_Tree when the internal scanners seek to a key greater than the last key in the file, when we do scanner.getKeyValue() we get the last key in the file, whereas PrefixTree seeks to null. This is a behaviour change. May be in the actual scan case we may not end up in this scenario, need to check with a testcase. But the test in TestSeekTo.testSeekTo() has a clear illustration of this problem.
> Will take this up after the current activities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)