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.
Attachments
Issue Links
- is broken by
-
IGNITE-5711 SQL: It should be possible to execute SQL queries over cache with no indexed types
-
- Resolved
-
- links to