[
https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937437#comment-16937437
]
Ignite TC Bot commented on IGNITE-11312:
----------------------------------------
{panel:title=Branch: [pull/6900/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4632091&buildTypeId=IgniteTests24Java8_RunAll]
> JDBC: Thin driver doesn't reports incorrect property names
> ----------------------------------------------------------
>
> Key: IGNITE-11312
> URL: https://issues.apache.org/jira/browse/IGNITE-11312
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
> Reporter: Stanislav Lukyanov
> Assignee: Suraj Singh
> Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> JDBC driver reports the properties it supports via getPropertyInfo method. It
> currently reports the property names as simple strings, like
> "enforceJoinOrder". However, when the properties are processed on connect
> they are looked up with prefix "ignite.jdbc", e.g.
> "ignite.jdbc.enforceJoinOrder".
> Because of this UI tools like DBeaver can't properly pass the properties to
> Ignite. For example, when "enforceJoinOrder" is set to true in "Connection
> settings" -> "Driver properties" menu of DBeaver it has no effect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
