You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Lev Agafonov (Jira)" <ji...@apache.org> on 2019/09/30 04:35:00 UTC

[jira] [Assigned] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names

     [ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lev Agafonov reassigned IGNITE-11312:
-------------------------------------

    Assignee: Lev Agafonov  (was: Suraj Singh)

> 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: 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)