[
https://issues.apache.org/jira/browse/HBASE-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776697#action_12776697
]
ryan rawson commented on HBASE-1841:
------------------------------------
I dont think we want to be throwing exceptions like that during writing, we'd
be preventing flushing and compactions, the former potentially causing data
loss in pre-HDFS-265, and the latter wedging up a hbase install.
As for the key order in the index, there were some calls that depended on the
choice of the first key in the block to work, specifically 'seekBefore'. By
changing the block index, this call won't work anymore in all cases. I should
know, I started out with a 'last key' block index, but had to switch to 'first
key' to make seekBefore work.
> If multiple of same key in an hfile and they span blocks, may miss the
> earlier keys on a lookup
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-1841
> URL: https://issues.apache.org/jira/browse/HBASE-1841
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Attachments: HBASE-1841-step1.patch, HBASE-1841-step2.patch
>
>
> See HBASE-818 for description by Schubert Zhang -- discovered by him doing a
> code review of hfile.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
