[IGNITE-9989] JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6
• Fix Version/s: 2.8
• Component/s: jdbc
• Assignee: Pavel Kuznetsov
• Reporter: Pavel Kuznetsov
• Created: 24/Oct/18 13:25
• Updated: 11/Feb/19 16:58
• Resolved: 01/Feb/19 13:30

Description

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

Issue Links

• is blocked by: IGNITE-10645 SQL properties ownership flag should be set at configuration parsing, not query execution.
• is blocked by: IGNITE-6173 SQL: do not start caches on client nodes
• is duplicated by: IGNITE-10118 JDBC v2: metadata.getSchemas returns cache names instead of schema names
• relates to: IGNITE-9606 JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
• links to: GitHub Pull Request #5716
• links to: GitHub Pull Request #5716