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

use the same information about indexes for JDBC drivers as for system view INDEXES

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.15
    • jdbc, odbc, sql

    Description

      As of now indexes information for JDBC drivers get by another way then system SQL view INDEXES. Need to use single source of the information to have consistent picture.

      So, JDBC drivers should use the same source as SQL view INDEXES (org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewIndexes)
      Start point for JDBC index metadata is org.apache.ignite.internal.jdbc2.JdbcDatabaseMetadata#getIndexInfo

      Also order of result should be correspond Javadoc ('ordered by NON_UNIQUE, TYPE, INDEX_NAME, and ORDINAL_POSITION') - at present it is not so.

      Attachments

        1. indexes_sqlline.txt
          6 kB
          Ilya Shishkov

        Issue Links

          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-17285 Ambiguous output of INDEXES SytemView if cache is created via DDL

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-9490 Connection.getMetaData.getIndexInfo method doesn't return PK indexes

          • Major - Major loss of function.
          • Resolved
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-15424 Calcite engine. Move schema management infrastructure to the core module

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #10316

          Activity

            People

              shishkovilja Ilya Shishkov
              jooger Iurii Gerzhedovich
              Votes:
              0 Vote for this issue
              Watchers:
              4 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 - 2h 10m
                  2h 10m