[
https://issues.apache.org/jira/browse/PHOENIX-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251039#comment-14251039
]
James Taylor commented on PHOENIX-1541:
---------------------------------------
Not sure of the exact structure, but we could have an interface for the
TypeSystem with the current Phoenix type system being an implementation. Then
the TypeSystem may have an enum that defines the possible types? Is this
different from the java.sql.Types - maybe a superset, as we already have our
"unsigned types" that don't fit. And this may get further extended if we wanted
to introduce a map type. Maybe an enum that lists all the possible types with
an indication of whether or not they're "optionally" implementable by a new
type system.
Nick probably has ideas around this. Probably more important to get the
RowKeySchema operations incorporated into the model first, though.
> Provide common interface to find different types (reintroduce PDataType enum)
> -----------------------------------------------------------------------------
>
> Key: PHOENIX-1541
> URL: https://issues.apache.org/jira/browse/PHOENIX-1541
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Dave Hacker
>
> [~jamestaylor] and I were just talking about how with the new change to
> remove PDataType enum its harder to now discover all the types the system
> supports.
> Not entirely sure what is going into the work to support the bundled HBase
> type system but It may be better to keep the enum around (have it implement
> the type interface and just delegate to the implementation class from the
> enum given the configured type system.
> [~ndimiduk] not sure what you think.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
