[
https://issues.apache.org/jira/browse/IGNITE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711236#comment-16711236
]
Ray commented on IGNITE-10569:
------------------------------
[~vozerov]
The easiest way to fix this bug is to ignore cases when comparing schema name
in JdbcRequestHandler.matches method.
Please take a look at the patch and let me know if this is the correct fix.
> 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)
