[
https://issues.apache.org/jira/browse/HBASE-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412504#comment-13412504
]
ramkrishna.s.vasudevan commented on HBASE-6336:
-----------------------------------------------
@Stack
bq.If so, why we write a flush file if no KVs?
Yes we are writing an emtpy now. Incase of compaction we are creating an empty
file. So once the region is split we compact, so there an empty file is
created for an empty region.
See HBASE-6059 - Replaying recovered edits would make deleted data exist again
There i had a concern on creating an empty store file, but it was needed. So
you feel any problem there Stack?
> Split point should not be equal with start row or end row
> ---------------------------------------------------------
>
> Key: HBASE-6336
> URL: https://issues.apache.org/jira/browse/HBASE-6336
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: chunhui shen
> Assignee: chunhui shen
> Fix For: 0.96.0
>
> Attachments: HBASE-6336.patch
>
>
> Should we allow split point equal with region's start row or end row?
> {code}
> // if the midkey is the same as the first and last keys, then we cannot
> // (ever) split this region.
> if (this.comparator.compareRows(mk, firstKey) == 0 &&
> this.comparator.compareRows(mk, lastKey) == 0) {
> if (LOG.isDebugEnabled()) {
> LOG.debug("cannot split because midkey is the same as first or " +
> "last row");
> }
> {code}
> Here, I think it is a mistake.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
