[HBASE-10091] Exposing HBase DataTypes to non-Java interfaces

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Component/s: Client
• Assignee: Unassigned
• Reporter: Nick Dimiduk
• Created: 05/Dec/13 23:18
• Updated: 16/Jun/22 05:50
• Resolved: 11/Jun/22 20:22

Description

Access to the DataType implementations introduced in HBASE-8693 is currently limited to consumers of the Java API. It is not easy to specify a data type in non-Java environments, such as the HBase shell, REST or Thrift Gateways, command-line arguments to our utility MapReduce jobs, or in integration points such as a (hypothetical extension to) Hive's HBaseStorageHandler. See examples where this limitation impedes in HBASE-8593 and HBASE-10071.

I propose the implementation of a type definition DSL, similar to the language defined for Filters in HBASE-4176. By implementing this in core HBase, it can be reused in all of the situations described previously. The parser for this DSL must support arbitrary type extensions, just as the Filter parser allows for new Filter types to be registered at runtime.

Issue Links

• relates to: HBASE-8593 Type support in ImportTSV tool
• relates to: HIVE-3211 Enhance hbase column mapping strategy to support complicated structures
• relates to: HBASE-10071 Backport HBASE-6592 to 0.94 branch
• relates to: HBASE-4176 Exposing HBase Filters to the Thrift API
• relates to: HIVE-6411 Support more generic way of using composite key for HBaseHandler