[
https://issues.apache.org/jira/browse/HBASE-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-8089:
--------------------------------
Attachment: HBASE-8089-types.txt
Updated spec document. Supported types changed a little, and a spec is outlined
for the basics.
Biggest open questions include:
- should null values be required for each type or is it enough to support
reading a null marker via the STRUCT/UNION implementation?
- how to handle String and byte[] types. Orderly goes to great pains to encode
values, Phoenix restricts the context in which they can be used.
> 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
> Attachments: HBASE-8089-types.txt, HBASE-8089-types.txt
>
>
> 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
