[
https://issues.apache.org/jira/browse/IGNITE-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684965#comment-16684965
]
Ignite TC Bot commented on IGNITE-9989:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2301909]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
BPlusTreeFakeReuseSelfTest.testTestRandomPutRemoveMultithreaded_2_50_1 - 0,0%
fails in last 100 master runs.
{color:#d04437}MVCC Cache{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2301960]]
* IgniteCacheMvccTestSuite:
CacheMvccReplicatedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups0_CoordinatorFails
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2301981]]
* IgniteBinaryObjectsCacheTestSuite3:
GridCacheWriteBehindStoreMultithreadedSelfTest.testPutGetRemoveWithoutCoalescing
- 0,0% fails in last 100 master runs.
{color:#d04437}PDS (Direct IO) 2{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2301996]]
{color:#d04437}Java Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2301930]]
{color:#d04437}Compute (Affinity Run){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2301915]]
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2302018&buildTypeId=IgniteTests24Java8_RunAll]
> JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME
> -----------------------------------------------------------------------------
>
> Key: IGNITE-9989
> URL: https://issues.apache.org/jira/browse/IGNITE-9989
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Pavel Kuznetsov
> Assignee: Pavel Kuznetsov
> Priority: Major
> Labels: jdbc
>
> Jdbc v2 driver has hardcoded values for meta attibutes :
> COLUMN_NAME = _KEY
> KEY_SEQ = 1
> PK_NAME = _KEY
> But this values should be different for different tables.
> how to reproduce:
> 1) connect to the cluser using jdbcv2 driver
> 2) CREATE TABLE TAB (ID LONG, SEC_ID LONG, VAL LONG, PRIMARY KEY(ID, SEC_ID))
> 3) check result of connection.getMetadata().getPrimaryKeys()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
