[
https://issues.apache.org/jira/browse/IGNITE-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618774#comment-17618774
]
Ilya Shishkov edited comment on IGNITE-11368 at 10/17/22 5:41 PM:
------------------------------------------------------------------
[~timonin.maksim], [~jooger], can you take a look, please:
https://github.com/apache/ignite/pull/10316 ?
Above failure are unrelated to the fix.
was (Author: shishkovilja):
[~timonin.maksim], [~jooger], can you take a look, please?
Above failure are unrelated to the fix.
> 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
> Attachments: indexes_sqlline.txt
>
> Time Spent: 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)
