[
https://issues.apache.org/jira/browse/HBASE-8693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-8693:
--------------------------------
Attachment: KijiFormattedEntityId.java
I had a look over the kiji-schema project. They have a much more developed
sense of schema than anything I've proposed, which makes me think I'm still on
the right track. I haven't been through it end-to-end, but I took a stab at
implementing a piece of their stack using this data types API. It looks to me
like the bit they use to implement HBase rowkeys.
I don't know how it would wire up into their Avro IDL, but it looks like they
could open up the restrictions on their RowKeyFormat2.ComponentType to support
any HDataType implementation if so desired. Here's the example.
> 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,
> 0001-HBASE-8693-Extensible-data-types-API.patch,
> 0001-HBASE-8693-Extensible-data-types-API.patch,
> 0002-HBASE-8693-example-Use-DataType-API-to-build-regionN.patch,
> KijiFormattedEntityId.java
>
>
--
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
