[
https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16879133#comment-16879133
]
Evgenii Zhuravlev commented on IGNITE-11312:
--------------------------------------------
[~surajsn], do you plan to implement this fix? I know that community is
interested in it, so, if you can't implement it, maybe it makes sense to give
an opportunity for someone else to step in and contribute it to the project.
> 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
>
> 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
(v7.6.3#76005)
