[
https://issues.apache.org/jira/browse/HBASE-14895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044397#comment-15044397
]
ramkrishna.s.vasudevan commented on HBASE-14895:
------------------------------------------------
bq.After bulk load and compaction we dont need inform the readers. After a
flush, which results in exactly one file, the notify mechanism can pass that
file's detail also?
True. Doing that way one thing that we can avoid is that though we notify the
readers on flush only still when a new scanner is created and that time if a
file was already comapcted the new heap will have the flushed file and the
older file that was compacted will be removed and we will have the new
comapcted file in the heap. Hence we need the above logic to determine the
exact new files so that we can seek on all of them.
Passing the file name on flush is a good suggestion where we will not end up in
a situation where there is a new file in the resetted heap that has come out of
compaction or bulk load.
> Seek only to the newly flushed file on scanner reset on flush
> -------------------------------------------------------------
>
> Key: HBASE-14895
> URL: https://issues.apache.org/jira/browse/HBASE-14895
> Project: HBase
> Issue Type: Sub-task
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 2.0.0
>
> Attachments: HBASE-14895.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
