[
https://issues.apache.org/jira/browse/IGNITE-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725144#comment-16725144
]
Pavel Kuznetsov commented on IGNITE-9989:
-----------------------------------------
1) We are able to get rid of old compute job that used to collect metadata
(sometimes in a wrong way) and unify logic with thin driver, I think it's
better to remove that old job in this ticket. This will affect other metadata
code in the v2.
2) New logic eliminated problem IGNITE-10645 which is currently in patch
avaliable state.
> 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)
