Re: How to configure a cluster as a persistent, replicated SQL database

Hi Jose I was asking how can I configure Oracle DB as persistent layer. At the moment I am using the Ignite native persistence as persistent layer, but I would like to use Oracle DB as persistent layer. How can I do this, what changes I should do to the config file. My config file looks like

Re: How to configure a cluster as a persistent, replicated SQL database

Hi Naveen, I managed to get everything up a and running...but for my testing, I have not been connecting from code. I have been using DBeaver to connect using SQL via the JDBC driver(s). Jose -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to configure a cluster as a persistent, replicated SQL database

Hi Jose Did it work for you ? I had the same question. I wanted to use JDBC client driver to connect to Ignite cluster. I am trying to use Java Would you be able ot share the code snippet if you are using java to connect to the ignite cluster thru JDBC client driver Thanks Naveen -- Sent

Re: How to configure a cluster as a persistent, replicated SQL database

Okay - figured it out... Had to prefix the 'PUBLIC' schema to the table name during the CREATE TABLE query: CREATE TABLE PUBLIC.City(... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to configure a cluster as a persistent, replicated SQL database

Hi Denis, I inserted a cache definition in the config of all the nodes, as recommended. Then activated the cluster and connected using the client JDBC driver, specifying the cache name in the connection string... it connected successfully. But when I submit a CREATE TABLE query, I receive the

Re: How to configure a cluster as a persistent, replicated SQL database

Jose, Currently you have to specify a cache name in the connection URL, that will be used to run SQL queries on. I'm not sure where it's a bug or a feature, but here is the ticket for fixing this: https://issues.apache.org/jira/browse/IGNITE-6481 For now you have to specify a cache name, that you

Re: How to configure a cluster as a persistent, replicated SQL database

Hey Denis, I think that we are making progress... I am now connecting to the database successfully, but when I submit a query, I get the following error: My config contains the following: /...

Re: How to configure a cluster as a persistent, replicated SQL database

Jose, You can use an XML file, that you use to start server nodes, as ignite-jdbc.xml in the connection string. The client node will be started automatically by the JDBC driver. Denis ср, 28 февр. 2018 г. в 19:32, joseheitor : > Thanks, Denis - this makes a lot of

Re: How to configure a cluster as a persistent, replicated SQL database

Thanks, Denis - this makes a lot of sense... Can you provide a sample ignite-jdbc.xml config file for reference? And any details about the config parameters for such a config file...? Also, must a 'Client' mode node be explicitly started prior to making a connection? Or does this happen in the

Re: How to configure a cluster as a persistent, replicated SQL database

Jose, >As usual, my JDBC connection points to the local node (where I am activating >the cluster on), but does not connect to the cluster port (11211) only to >the default 10800 port. 11211 is a connector port, which serves a different purpose. By default JDBC connections are accepted on port

Re: How to configure a cluster as a persistent, replicated SQL database

Hi Denis, I have now launched the 3 nodes on different boxes, and listed their addresses in each config. The nodes seem to be aware of each other, as I notice the topology updating when I bring additional nodes online/offline. As usual, my JDBC connection points to the local node (where I am

Re: How to configure a cluster as a persistent, replicated SQL database

Jose, Actually, there is no such node, that is responsible for all data, stored in the cluster. The data is distributed across all nodes instead, so each node is responsible for some particular piece. Cache data is split into partitions (1024 for a partitioned cache and 512 for replicated by

Re: How to configure a cluster as a persistent, replicated SQL database

Thanks, Denis. I read the docs and also followed this short video demo/tutorial: https://www.youtube.com/watch?v=FKS8A86h-VY It worked as described, so I then extended the exercise by adding and additional (3rd) node, using the persistent-store

Re: How to configure a cluster as a persistent, replicated SQL database

Hi Jose! Apache Ignite is indeed a scalable in-memory persistent SQL-enabled data store. Here is documentation, that can help you to start using it: *Data grid*: https://apacheignite.readme.io/docs/data-grid *Persistent storage*: https://apacheignite.readme.io/docs/distributed-persistent-store

How to configure a cluster as a persistent, replicated SQL database

How do I configure a cluster as a persistent, replicated SQL datastore?And can it perform as an active-active, high-availability solution that can be scaled horizontally? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/