You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2013/08/08 01:50:48 UTC

[jira] [Commented] (HBASE-8863) Enhance data type API with type vs type comparison methods

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

Nick Dimiduk commented on HBASE-8863:
-------------------------------------

Additional consideration from [~giacomotaylor]'s comment on [RB|https://reviews.apache.org/r/12069/]

{quote}
For Phoenix, we need in addition to this:
- getMaxLength (for numeric types this is the precision, for string types this is the max allowed size)
- getScale (for numeric types).
These return null if no max length and/or scale was provided. This is for type declarations like this:
CREATE TABLE t (c1 VARCHAR(10), c2 DECIMAL(10,2), c3 VARCHAR, c4 DECIMAL);
where VARCHAR(10) would have a maxLength of 10, and DECIMAL(10,2) would have a maxLength of 10 and a scale of 2. The others would return null for these methods.

It's possible that we could manage this ourselves one layer up, but I just wanted to bring it up.
{quote}
                
> Enhance data type API with type vs type comparison methods
> ----------------------------------------------------------
>
>                 Key: HBASE-8863
>                 URL: https://issues.apache.org/jira/browse/HBASE-8863
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: Nick Dimiduk
>             Fix For: 0.95.2
>
>
> The data types defined in HBASE-8693 should be suitable for use in query planning engines operating against HBase. The working example being Phoenix's [PDataType|https://github.com/forcedotcom/phoenix/blob/master/src/main/java/com/salesforce/phoenix/schema/PDataType.java] and its {{isCoercibleTo}} and {{isComparableTo}} methods.

--
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