[
https://issues.apache.org/jira/browse/IGNITE-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7528:
-----------------------------------
Fix Version/s: (was: 2.6)
2.7
> 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.7
>
>
> 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)
