[
https://issues.apache.org/jira/browse/HBASE-8693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692489#comment-13692489
]
Nick Dimiduk commented on HBASE-8693:
-------------------------------------
A note regarding variable length encodings. Variable vs fixed-width encodings
was a highlighted point during conversations around HBASE-7221 and HBASE-7692.
These data type implementations make exclusive use of the {{OrderedBytes}}
encodings. That is because my thinking around them thus far is focused on use
as rowkeys and column qualifiers. However, this requirement isn't strictly
necessary for use in values. I noticed a rough analogy in Postgres's data type
implementation is the distinction between the encoding used to store data and
the encoding used for an index entry.
Do you think we should have a similar kind of dichotomy for encoding into
order-preserving context vs non-order-preserving context? My initial thinking
is probably not (due to additional API surface area), but I want to have the
conversation.
> 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
>
>
--
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
