[jira] [Updated] (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: Fix Version/s: (was: 1.7) 1.6 > 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)
[jira] [Updated] (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: Description: # 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 was: # 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. See laso discussion here: http://apache-ignite-developers.2346864.n4.nabble.com/What-is-jdbc-ignite-cfg-td5573.html > 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)
[jira] [Updated] (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: Description: # 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. See laso discussion here: http://apache-ignite-developers.2346864.n4.nabble.com/What-is-jdbc-ignite-cfg-td5573.html was: #. 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. See laso discussion here: http://apache-ignite-developers.2346864.n4.nabble.com/What-is-jdbc-ignite-cfg-td5573.html > 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. > 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)
