hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8693) Implement extensible type API based on serialization primitives
Date Wed, 26 Jun 2013 21:43:20 GMT

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

Nick Dimiduk commented on HBASE-8693:
-------------------------------------

bq. Should this work be in hbase-common rather than in hbase-client?

Initial conversations required the type stuff not be in common. I agree, it makes more sense
there and I think that community opinion is changing. The current implementation doesn't bring
in any dependencies, so it should be painless.

bq. What is Order here?

{{Order}} is a component from the {{OrderedBytes}} implementation (see patch on HBASE-8201).
It enables users to store data sorted in ascending or descending order. Right now it's mostly
a vestigial appendage; I don't know how the data types API wants to expose and consume this
functionality. I'm hoping to gain insight from Phoenix, Kiji, &c in future reviews.

bq. When would I use isCoercibleTo?

This comes from examination of Phoenix's {{PDataType}}. My understanding is, in the absence
of secondary indices, the query planner can use type coercion to its advantage. This is the
part of the data type API that I understand the least. I'm hoping for more clarity from [~giacomotaylor].

bq. I see a read on Union4

Sounds like a bug to me.

bq. How I describe a Struct outside of a Struct..?

Examples to follow.

bq. Whats a Binary?

Equivalent to SQL BLOB. This is how a user can inject good old fashion {{byte[]}}s into a
{{Struct}} or {{Union}}.

bq. Do we need all these types?

Great question. That conversation is happening up on HBASE-8089. My preference is no, but
I think the SQL guys want more of these for better interoperability between them.
                
> 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

Mime
View raw message