You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/08 13:12:00 UTC
[jira] [Commented] (IGNITE-10569) Null meta information when
getting meta for a customized schema cache through JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946840#comment-16946840 ]
Maxim Muzafarov commented on IGNITE-10569:
------------------------------------------
Moved to 2.9 due to inactivity. Please, feel free to move it back if you will be able to complete the ticket by 2.8 code freeze date, December 2, 2019.
> 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 Liu
> Assignee: Ray Liu
> 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
(v8.3.4#803005)