[ 
https://issues.apache.org/jira/browse/IGNITE-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618772#comment-17618772
 ] 

Ignite TC Bot commented on IGNITE-11368:
----------------------------------------

{panel:title=Branch: [pull/10316/head] Base: [master] : Possible Blockers 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests 1 TIMEOUT , Out Of Memory Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=6837422]]
* IgniteCacheTestSuite2: 
IgniteCacheClientNodeChangingTopologyTest.testPessimisticTx - Test has low fail 
rate in base branch 0,0% and is not flaky

{panel}
{panel:title=Branch: [pull/10316/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6836092&buildTypeId=IgniteTests24Java8_RunAll]

> 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)

Reply via email to