[ https://issues.apache.org/jira/browse/HBASE-17339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15783549#comment-15783549 ]
stack commented on HBASE-17339: ------------------------------- Sounds good. The '... is applicable...' in the above is that the table was marked that it is a monotonically increasing table? Would be cool if the attribute were done in alignment w/ scheme described over in HBASE-10247 (though there'd be only this option). Thanks [~eshcar] > Scan-Memory-First Optimization for Get Operation > ------------------------------------------------ > > Key: HBASE-17339 > URL: https://issues.apache.org/jira/browse/HBASE-17339 > Project: HBase > Issue Type: Improvement > Reporter: Eshcar Hillel > Attachments: HBASE-17339-V01.patch > > > The current implementation of a get operation (to retrieve values for a > specific key) scans through all relevant stores of the region; for each store > both memory components (memstores segments) and disk components (hfiles) are > scanned in parallel. > We suggest to apply an optimization that speculatively scans memory-only > components first and only if the result is incomplete scans both memory and > disk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)