ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Pavlukhin (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
Date Wed, 30 Oct 2019 09:13:00 GMT

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

Ivan Pavlukhin commented on IGNITE-11312:
-----------------------------------------

Or it is even better to merge fresh master to your PR and rerun TC bot, as it is good to run
automated javadoc checks as well.

> 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: Lev Agafonov
>            Priority: Major
>              Labels: newbie
>             Fix For: 2.8
>
>          Time Spent: 20m
>  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)

Mime
View raw message