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

Posted to issues@ignite.apache.org by "Iurii Gerzhedovich (Jira)" <ji...@apache.org> on 2024/05/31 07:30:00 UTC

[jira] [Assigned] (IGNITE-22193) Move IgniteJdbcDriver to non internal package

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

Iurii Gerzhedovich reassigned IGNITE-22193:
-------------------------------------------

    Assignee: Iurii Gerzhedovich

> Move IgniteJdbcDriver to non internal package
> ---------------------------------------------
>
>                 Key: IGNITE-22193
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22193
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Iurii Gerzhedovich
>            Assignee: Iurii Gerzhedovich
>            Priority: Major
>              Labels: ignite-3
>
> Right now we have org.apache.ignite.internal.jdbc.IgniteJdbcDriver which is placed in `internal' package. Most database utilities working with JDBC drivers show the name to users, e.g. DBeaver.
> This approach is not user-friendly. Let's move the class to `org.apache.ignite.jdbc` package



--
This message was sent by Atlassian Jira
(v8.20.10#820010)