[
https://issues.apache.org/jira/browse/IGNITE-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-11368:
---------------------------------------
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.processors.odbc.jdbc.JdbcMetadataInfo#getIndexesMeta
was:
As of now indexes information for ODBC/JDBC drivers get by another way then
system SQL view INDEXES. Need to use single source of the information to have
consistent picture.
So, ODBC/JDBC drivers should use the same source as SQL view INDEXES
(org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewIndexes)
> use the same information about indexes for ODBC 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
> Priority: Major
> Labels: newbie
> Fix For: 2.9
>
>
> 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.processors.odbc.jdbc.JdbcMetadataInfo#getIndexesMeta
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
