[
https://issues.apache.org/jira/browse/PHOENIX-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393827#comment-14393827
]
Hudson commented on PHOENIX-1799:
---------------------------------
SUCCESS: Integrated in Phoenix-3.0-hadoop1 #381 (See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/381/])
PHOENIX-1799 Provide parameter metadata for prepared create table statements
(jtaylor: rev a828537d398a602015e144aa67cc1af6d8e54cb2)
* phoenix-core/src/test/java/org/apache/phoenix/compile/QueryMetaDataTest.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/CreateTableCompiler.java
> Provide parameter metadata for prepared create table statements
> ---------------------------------------------------------------
>
> Key: PHOENIX-1799
> URL: https://issues.apache.org/jira/browse/PHOENIX-1799
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Nick Dimiduk
> Assignee: James Taylor
> Fix For: 5.0.0, 3.3.1, 4.3.1, 4.4.0
>
> Attachments: PHOENIX-1799.patch
>
>
> While working on PHOENIX-971, I ran into an issue in our IT code where we
> support prepared CREATE TABLE statements with bound parameters. It seems we
> don't provide any ParameterMetaData, other than knowledge about the number of
> bind slots. In turn, Calcite is unable to describe the statement's signature
> over RPC. This ticket proposes we infer ParameterMetaData for this statement
> case so that we can allow all tests to run vs the query server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
