[jira] [Commented] (HBASE-17339) Scan-Memory-First Optimization for Get Operations

["Eshcar Hillel (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-17339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857616#comment-15857616 ] 

Eshcar Hillel commented on HBASE-17339:
---------------------------------------

new patch is available
Summary of changes:
* (TODO 1 above) init maxFlushedTimestamp from store file timestams (if any)
* (TODO 2) memoryScanOptimization is a table property
* added tests through TestAcidGuarantees

> Scan-Memory-First Optimization for Get Operations
> -------------------------------------------------
>
>                 Key: HBASE-17339
>                 URL: https://issues.apache.org/jira/browse/HBASE-17339
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Eshcar Hillel
>            Assignee: Eshcar Hillel
>         Attachments: HBASE-17339-V01.patch, HBASE-17339-V02.patch, HBASE-17339-V03.patch, HBASE-17339-V03.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.15#6346)