[
https://issues.apache.org/jira/browse/HBASE-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644873#comment-13644873
]
Nick Dimiduk commented on HBASE-8089:
-------------------------------------
The advantages I see for following SQLite4 include:
- Serialized values are marked with their type as an initial byte. This is
advantageous as serialized values can be sniffed and deserialized by tools
ignorant of the application schema.
- Numeric types (integral and real numbers) are all normalized to identical
encoding. This allows them to be compared directly and provides more
flexibility to users.
- A C language implementation and tools are readily available for validation,
providing test scenarios and as near-complete implementation when we're ready
to work on the non-JVM client.
The primary detriment I see with using their encoding is the limitation on
disallowing null bytes in Strings. The same restriction applies to blobs except
for those used as the last value in a compound key. IIRC, this restriction is
identical to that imposed by Phoenix.
> 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,
> 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
