hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10091) Exposing HBase DataTypes to non-Java interfaces
Date Thu, 13 Mar 2014 23:11:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934275#comment-13934275

stack commented on HBASE-10091:

Tell me more about how this would work?

hbase:int would map to org.apache.hadoop.hbase.types.RawInt in the DSL

Each language would have to have an interpreter for the DSL?

There is some overlap with  how types are called out in avro/pb IDLs?

> Exposing HBase DataTypes to non-Java interfaces
> -----------------------------------------------
>                 Key: HBASE-10091
>                 URL: https://issues.apache.org/jira/browse/HBASE-10091
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: Nick Dimiduk
> 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.

This message was sent by Atlassian JIRA

View raw message