You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2018/04/16 15:47:00 UTC

[jira] [Updated] (IGNITE-7528) JDBC thin: set query options on per-statement level

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

Andrey Gura updated IGNITE-7528:
--------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> JDBC thin: set query options on per-statement level
> ---------------------------------------------------
>
>                 Key: IGNITE-7528
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7528
>             Project: Ignite
>          Issue Type: Task
>          Components: jdbc
>            Reporter: Vladimir Ozerov
>            Priority: Major
>             Fix For: 2.6
>
>
> We have a number of query options which are set on connection string and are applied to every request executed on top this connection. This includes "distributedJoins", "enforceJoinsOrder", "colocated", etc.. This is not very flexible because user have to construct different connection strings for different set of options. 
> JDBC API mitigates this problem with {{Statement.unwrap()}} method. Ultimately it allows to case {{Statement}} object to vendor-specific class where any additional methods could be exposed. 
> Let's create public wrappers for out statements where it would possible to set necessary options. When set, we will add them to query requests thus overriding connection string counterparts.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)