[
https://issues.apache.org/jira/browse/PHOENIX-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324812#comment-15324812
]
Hudson commented on PHOENIX-2489:
---------------------------------
FAILURE: Integrated in Phoenix-master #1252 (See
[https://builds.apache.org/job/Phoenix-master/1252/])
PHOENIX-2489 Support sequence metadata access through DatabaseMetaData
(jamestaylor: rev f88cbf8390b5a2f44a60cb9e585de5d2f08cefdb)
*
phoenix-core/src/it/java/org/apache/phoenix/end2end/QueryDatabaseMetaDataIT.java
*
phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixDatabaseMetaData.java
*
phoenix-core/src/main/java/org/apache/phoenix/filter/BooleanExpressionFilter.java
*
phoenix-core/src/main/java/org/apache/phoenix/filter/MultiKeyValueComparisonFilter.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/ValueSchema.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/UnionCompiler.java
> Support sequence metadata access through DatabaseMetaData interface
> -------------------------------------------------------------------
>
> Key: PHOENIX-2489
> URL: https://issues.apache.org/jira/browse/PHOENIX-2489
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.8.0
>
> Attachments: PHOENIX-2489.patch, PHOENIX-2489_v2.patch
>
>
> Our SYSTEM.SEQUENCE table is not accessible through the standard
> DatabaseMetaData API. Though there are no specific APIs around sequences,
> [~julianhyde] gave me the excellent idea of modeling a sequence as another
> table type. This would fit in very well, including support for accessing
> tenant-specific sequences.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)