[
https://issues.apache.org/jira/browse/IGNITE-18418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Gagarkin updated IGNITE-18418:
-----------------------------------
Description:
# Create a separate ignite-jdbc module
# Move the code base of jdbc to the new module (IgniteJdbcDriver,
JdbcConnection, JdbcResultSet, etc)
# The new module should depend on client-common, client-handler modules
# Create Maven/Gradle tasks to build a fat jar of ignite-jdbc and publish it
was:
# Create a separate ignite-jdbc module
# Move the code base of jdbc to the new module (IgniteJdbcDriver,
JdbcConnection, JdbcResultSet, etc)
# The new module should depend on ignite-client, client-common, client-handler
modules
# Create Maven/Gradle tasks to build a fat jar of ignite-jdbc and publish it
Consider an option to create ignite-jdbc-client and get rid of using
ignite-client in ignite-jdbc module.
> Create a separate ignite-jdbc module
> ------------------------------------
>
> Key: IGNITE-18418
> URL: https://issues.apache.org/jira/browse/IGNITE-18418
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
> Reporter: Ivan Gagarkin
> Priority: Major
>
> # Create a separate ignite-jdbc module
> # Move the code base of jdbc to the new module (IgniteJdbcDriver,
> JdbcConnection, JdbcResultSet, etc)
> # The new module should depend on client-common, client-handler modules
> # Create Maven/Gradle tasks to build a fat jar of ignite-jdbc and publish it
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
