ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9989) JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME
Date Tue, 06 Nov 2018 15:04:00 GMT

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

ASF GitHub Bot commented on IGNITE-9989:
----------------------------------------

GitHub user pavel-kuznetsov opened a pull request:

    https://github.com/apache/ignite/pull/5308

    IGNITE-9989: Fixed jdbc v2 PK metadata

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-9989

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5308.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5308
    
----
commit c8521cb526367a2d9448dcb7e1ca500e8494b74b
Author: Pavel Kuznetsov <palmihal@...>
Date:   2018-11-06T00:01:46Z

    ignite-9989: Draft of the fix.
    
    In jdbc v2, now we avoid using distributed task that fetches metadata to
    get PK metadata. We use existing cache descriptors instead.

commit 1e7b3f1947da236b071465c661525ffbe40af06b
Author: Pavel Kuznetsov <palmihal@...>
Date:   2018-11-06T14:39:11Z

    ignite-9989: Updated tests to work with many tables.
    
    Backported test for primary keys metadata from metadata test of jdbc
    thin driver. This change made IGNITE-10118 highlighted.

commit f12c8549b0de14a3dbecc464d5f19d927560ca56
Author: Pavel Kuznetsov <palmihal@...>
Date:   2018-11-06T14:50:01Z

    ignite-9989: Jdbc v2 PK meta refactoring.
    
    javadoc, moved method to QueryUtils.

----


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

Mime
View raw message