[
https://issues.apache.org/jira/browse/HBASE-8693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693632#comment-13693632
]
stack commented on HBASE-8693:
------------------------------
Should this work be in hbase-common rather than in hbase-client? They are
client facility at first but one day they might go server-side. Also, easier
adding to hbase-common than to hbase-client. Unless they have dependencies?
What is Order here?
+ /**
+ * Write instance <code>v</code> into buffer <code>b</code>.
+ */
+ public abstract void write(ByteBuffer b, T v, Order ord);
When would I use isCoercibleTo?
I see a read on Union4 but not a write. That intentional? The union3 will
take care of it? Ditto union3...
How I describe a Struct outside of a Struct (JSON to describe how to make one?)
Whats a Binary?
Agree that example usage would help.
Do we need all these types?
Good stuff N.
I think you should post today's slides here too; they are good on the
high-level.
> 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
