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

Eli Collins commented on HBASE-8089:
------------------------------------

Hey Nick,

It might be worth updating this jira to reflect the latest state of the work. 
IIUC this work is about proving a client-side library that does the 
order-preserving serialization, that higher level projects (eg Phoenix & Kiji) 
can use for row keys and column qualifiers. Per the other jiras, cell 
serialization, defining types, and schema are out of scope. These are left to 
higher-level systems which may make different choices (eg in terms of how to 
create compound keys) and may have different type models, but at least will be 
able to share serialization.

IMO it's worth considering creating a separate project for this as this is 
genuinely useful outside HBase (eg container formats) and would benefit from 
multiple language implementations (the serialization here is language agnostic 
right?) and so the HBase project may end up being a clunky place to maintain 
things.

Thanks,
Eli
                
> Add type support
> ----------------
>
>                 Key: HBASE-8089
>                 URL: https://issues.apache.org/jira/browse/HBASE-8089
>             Project: HBase
>          Issue Type: New Feature
>          Components: Client
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>             Fix For: 0.98.0
>
>         Attachments: HBASE-8089-types.txt, HBASE-8089-types.txt, 
> HBASE-8089-types.txt, HBASE-8089-types.txt, hbase data types WIP.pdf
>
>
> This proposal outlines an improvement to HBase that provides for a set of 
> types, above and beyond the existing "byte-bucket" strategy. This is intended 
> to reduce user-level duplication of effort, provide better support for 
> 3rd-party integration, and provide an overall improved experience for 
> developers using HBase.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to