Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-5744

Ignore non user caches when automatically choosing a queryable cache inside JDBC driver

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 2.1
    • 2.1
    • jdbc, sql
    • None

    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

          Activity

            People

              al.psc Alexander Paschenko
              al.psc Alexander Paschenko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m