[
https://issues.apache.org/jira/browse/HBASE-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740352#comment-13740352
]
Eli Collins commented on HBASE-8089:
------------------------------------
Thanks Nick. Probably worth a broader discussion. The view in HBASE-7941 that
HBase is a database and should therefore provide types is pretty different from
Bigtable's design:
"In many ways, Bigtable resembles a database: it shares many implementation
strategies with databases... but Bigtable provides a different interface than
such systems. Bigtable does not support a full relational data model; instead,
it provides clients with a simple data model that supports dynamic control over
data layout and format, and allows clients to reason about the locality
properties of the data represented in the underlying storage... Bigtable also
treats data as uninterpreted strings, although clients often serialize various
forms of structured and semi-structured data into these strings. Clients can
control the locality of their data through careful choices in their schemas."
While you could preserve the flexibility here while providing one
implementation of a type model in HBase I think it's an explicit, existing
design decision to have HBase support multiple distinct type models in higher
level systems. And if those systems want to share code and type models that's
great, but IMO HBase is a storage system w/o an explicit type model by design,
and we start to lose the above benefits as we bring type awareness into core
HBase components like the RS.
> 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
