[jira] Commented: (HBASE-1249) Rearchitecting of server, client, API, key format, etc for 0.20

["Erik Holstad (JIRA)" <ji...@apache.org>]

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

Erik Holstad commented on HBASE-1249:
-------------------------------------

I thing that was shown in Jonathan's fine looking example.pdf is the notion of a timestamp for the storefile so that we could use that to find out if there is anything in there that might be of interest for the query. I looked at how storefiles are created today and it looks like they have a sequenceid/logCacheFlushId which to me just looks like in incremented value at the HR level, so all storefiles in a store have unique keys. So to me it looks like it would be possible to use a timestamp here instead and use that information to speed up the get queries. The new id would be set to the latest timestamp of the inserts in the flushed memcache or something like that.

> Rearchitecting of server, client, API, key format, etc for 0.20
> ---------------------------------------------------------------
>
>                 Key: HBASE-1249
>                 URL: https://issues.apache.org/jira/browse/HBASE-1249
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Jonathan Gray
>            Assignee: Erik Holstad
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: HBASE-1249-Example-v1.pdf, HBASE-1249-Example-v2.pdf, HBASE-1249-GetQuery-v1.pdf, HBASE-1249-GetQuery-v2.pdf, HBASE-1249-GetQuery-v3.pdf, HBASE-1249-StoreFile-v1.pdf
>
>
> To discuss all the new and potential issues coming out of the change in key format (HBASE-1234): zero-copy reads, client binary protocol, update of API (HBASE-880), server optimizations, etc...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.