You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Pavlov (Jira)" <ji...@apache.org> on 2022/11/03 10:10:00 UTC
[jira] [Updated] (IGNITE-11368) use the same information about indexes for JDBC drivers as for system view INDEXES
[ https://issues.apache.org/jira/browse/IGNITE-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Pavlov updated IGNITE-11368:
-----------------------------------
Fix Version/s: 2.14
> use the same information about indexes for JDBC drivers as for system view INDEXES
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-11368
> URL: https://issues.apache.org/jira/browse/IGNITE-11368
> Project: Ignite
> Issue Type: Task
> Components: jdbc, odbc, sql
> Reporter: Yury Gerzhedovich
> Assignee: Ilya Shishkov
> Priority: Major
> Labels: ise, newbie
> Fix For: 2.14
>
> Attachments: indexes_sqlline.txt
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)