ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suraj Singh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
Date Fri, 17 May 2019 17:11:00 GMT

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

Suraj Singh commented on IGNITE-11312:

Hi there Stanislav,

I had gone through the code base and understood your problem. To resolve this issue, Is your
ask is to write documentation highlighting this issue by enforcing the person to add _ignite.jdbc_
before similar things or to make some code change to fix it?



> 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

View raw message