You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2016/05/12 15:50:13 UTC

[jira] [Issue Comment Deleted] (IGNITE-2382) Force client mode in JDBC driver and provide default configuration file

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

Andrey Gura updated IGNITE-2382:
--------------------------------
    Comment: was deleted

(was: Implemented. Added tests. Waiting for TC.

Still need to test with Zeppelin.)

> Force client mode in JDBC driver and provide default configuration file
> -----------------------------------------------------------------------
>
>                 Key: IGNITE-2382
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2382
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey Gura
>            Assignee: Andrey Gura
>            Priority: Minor
>             Fix For: 1.6
>
>
> # There is no reason to start server node during creation JDBC connection. So client mode should be forced.
> # If user didn't specify any configuration file in JDBC URL then default configuration file should be used.
> # Remove multicast IP finder from example because it is default IP finder.
> Also need  sample step-by-step guide with a sample configuration. This configuration should include a couple of data types, like Person and Organization, define indexes for them, etc.
> This guide should include:
> # Start Ignite Servers
> # Populate data - should have example with configuration.
> # Query data using JDBC driver - example code and, if needed, configuration to support it.
> See laso discussion here: http://apache-ignite-developers.2346864.n4.nabble.com/What-is-jdbc-ignite-cfg-td5573.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)