[
https://issues.apache.org/jira/browse/IGNITE-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Paschenko updated IGNITE-5744:
----------------------------------------
Description:
This is related to IGNITE-5711.
When user supplies no cache name in JDBC connection params, we try to use all
caches, including system ones, as candidate query caches, this must be
explicitly forbidden.
Failing test:
{{org.apache.ignite.jdbc.JdbcNoDefaultCacheTest#testNoCacheNameQuery}},
apparently did not fail on TC because of inconsistent map iteration order.
was:
This is related to IGNITE-5711.
When user supplies no cache name in JDBC connection params, we try to use all
caches, including system ones, as candidate query caches, this must be
explicitly forbidden.
> Ignore non user caches when automatically choosing a queryable cache inside
> JDBC driver
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-5744
> URL: https://issues.apache.org/jira/browse/IGNITE-5744
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
> Affects Versions: 2.1
> Reporter: Alexander Paschenko
> Assignee: Alexander Paschenko
> Priority: Critical
> Fix For: 2.2
>
>
> This is related to IGNITE-5711.
> When user supplies no cache name in JDBC connection params, we try to use all
> caches, including system ones, as candidate query caches, this must be
> explicitly forbidden.
> Failing test:
> {{org.apache.ignite.jdbc.JdbcNoDefaultCacheTest#testNoCacheNameQuery}},
> apparently did not fail on TC because of inconsistent map iteration order.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
