You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/12/28 23:52:49 UTC

[jira] [Updated] (PHOENIX-2453) Make prepared statement creation delegate to org.apache.phoenix.jdbc.PhoenixConnection#prepareStatement(java.lang.String)

     [ https://issues.apache.org/jira/browse/PHOENIX-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-2453:
----------------------------------
    Fix Version/s: 4.7.0

> Make prepared statement creation delegate to org.apache.phoenix.jdbc.PhoenixConnection#prepareStatement(java.lang.String)
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-2453
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2453
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.5.2
>            Reporter: Clement Escoffier
>             Fix For: 4.7.0
>
>         Attachments: PHOENIX-2453.patch
>
>
> This issue is about making the prepare statement creation methods delegate to org.apache.phoenix.jdbc.PhoenixConnection#prepareStatement(java.lang.String) in order to avoid exception in applications and clients using this method.
> For the context, the issue was raised by a user of vert.x (http://vertx.io). This user tries to connect the vertx-jdbc-client to phoenix. A vert.x application cannot use directly the JDBC driver because it promotes an asynchronous and non-blocking development model (while jdbc interactions are blocking). The vertx-jdbc-client is using ` `prepareStatement(String sql, int autoGeneratedKeys)` which throws an exception. 
> A solution would be to delegate the method to the "simplest" version (just "sql") and ignore the effect of the passed parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)