ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lev Agafonov (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
Date Fri, 04 Oct 2019 06:31:00 GMT

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

Lev Agafonov commented on IGNITE-11312:

[~isapego], could you please do a final review?

> 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

View raw message