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-10569) Null meta information when getting meta for a customized schema cache through JDBC driver
Date Thu, 06 Dec 2018 10:16:00 GMT

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

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

GitHub user ldzhjn opened a pull request:

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

    IGNITE-10569 Null meta information when getting meta for a customized schema cache through
JDBC driver

    

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

    $ git pull https://github.com/ldzhjn/ignite IGNITE-10569

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

    https://github.com/apache/ignite/pull/5588.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 #5588
    
----
commit bf1cfda30da82a17dd279271f8415b5c14412016
Author: rayliu <rayliu@...>
Date:   2018-12-06T10:14:28Z

    Fix bug

----


> Null meta information when getting meta for a customized schema cache through JDBC driver
> -----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-10569
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10569
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc
>            Reporter: Ray
>            Assignee: Ray
>            Priority: Major
>             Fix For: 2.8
>
>
> When I create a cache with customized schema(not PUBLIC), then query the column meta
information through thin JDBC driver it will return null.
>  
> Analysis:
> The cases of schema name is different in GridQueryTypeDescriptor and CacaheConfiguration.
> So the schema validation
> if (!matches(table.schemaName(), req.schemaName()))
> in method JdbcRequestHandler.getColumnsMeta will not pass.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message