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-8089) Add type support
Date Thu, 08 Aug 2013 19:49:48 GMT

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

stack commented on HBASE-8089:

bq. An HBase that ships with an API for describing data types and implementations of a set
of common definitions takes the next step in interoperability.

So you are thinking more than just a client-side utility lib but an actual facade that does
typing (though it is all client-side) as in for example TypedHTable that does something like
typedHTable.put(new Put(row).addInteger(12345)) and int i = typedHTable.get(new Get(row).getInteger());?
 HBase internally is still all byte arrays but it'd have this new class that made it look
like we could exploit this typing info server-side (e.g. better compression)?  I suppose I'd
have to register a serializer w/ this new TypedHTable too?  Would the serializer be per table?

> Add type support
> ----------------
>                 Key: HBASE-8089
>                 URL: https://issues.apache.org/jira/browse/HBASE-8089
>             Project: HBase
>          Issue Type: New Feature
>          Components: Client
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>             Fix For: 0.98.0
>         Attachments: HBASE-8089-types.txt, HBASE-8089-types.txt, HBASE-8089-types.txt,
HBASE-8089-types.txt, hbase data types WIP.pdf
> This proposal outlines an improvement to HBase that provides for a set of types, above
and beyond the existing "byte-bucket" strategy. This is intended to reduce user-level duplication
of effort, provide better support for 3rd-party integration, and provide an overall improved
experience for developers using HBase.

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

View raw message