[
https://issues.apache.org/jira/browse/HBASE-8693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713011#comment-13713011
]
Nick Dimiduk commented on HBASE-8693:
-------------------------------------
To be fair, sort order also is of concern in column names. My choice of the
word "schema" was unfortunate in my previous comment. I should have said "no
composite structure is written into the concatenation." Because HBase's only
native data type is byte[], encodings are necessary for any application value
other than byte[], wherever it hits a rowkey, qualifier, or value.
It's quite out of scope for my purposes, but I'm curious what you think about
the future direction with schema. I think the Phoenix and Kiji folk will have
some good insights.
> Implement extensible type API based on serialization primitives
> ---------------------------------------------------------------
>
> Key: HBASE-8693
> URL: https://issues.apache.org/jira/browse/HBASE-8693
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.95.2
>
> Attachments: 0001-HBASE-8693-Extensible-data-types-API.patch,
> 0001-HBASE-8693-Extensible-data-types-API.patch,
> 0001-HBASE-8693-Extensible-data-types-API.patch,
> 0002-HBASE-8693-example-Use-DataType-API-to-build-regionN.patch
>
>
--
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
