[
https://issues.apache.org/jira/browse/IGNITE-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628392#comment-17628392
]
Ignite TC Bot commented on IGNITE-11368:
----------------------------------------
{panel:title=Branch: [pull/10316/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10316/head] Base: [master] : New Tests
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}JDBC Driver{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=6890773]]
* {color:#013220}IgniteJdbcDriverTestSuite:
JdbcThinMetadataSelfTest.testIndexMetadataMatchesSystemView - PASSED{color}
{color:#00008b}Calcite SQL{color} [[tests
11|https://ci2.ignite.apache.org/viewLog.html?buildId=6890322]]
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsOneFieldSearchWithNull - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsWithCorrelate - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsOneFieldSearchRangeOptimization -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsSeveralFieldsSearch - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsMaxComplexity - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsDynamicParams - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsOneFieldSearchDeduplication -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsOneFieldSearch - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsDescOrdering - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsTypeConversion - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SearchSargOnIndexPlannerTest.testBoundsOneFieldSingleTuple - PASSED{color}
... and 0 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6890402&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
> Fix For: 2.15
>
> 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)
