[
https://issues.apache.org/jira/browse/IGNITE-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282718#comment-15282718
]
Andrey Gura commented on IGNITE-2382:
-------------------------------------
Users are already able specify client type. This possibility introduced due to
an thin client implementation. Client type depends on JDBC URL. In order to use
thick client JDBC URL should start with {{jdbc:ignite://}} string, and for thin
client - {{jdbc:ignite:cfg://}}. See also javadoc for {{IgniteJdbcDriver}}
class.
Also usage of thick client is documented on readme.io (for versions 1.3 and
earlier). Usage of thin client is documented on readme.io (for versions 1.4 and
later).
Could you please describe mentioned case?
> 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)
