Hi, 1. SQL will support transactions after next ticket will be resolved [1]. You can track it's state via "start watching this issue" link on issue page.
2. JDBC pooling, failover and load banacling is not supported for JDBC. More over JDBC connection is not thread safe. Feel free to create a ticket for features you need. Most likely, c3pi0 can be used for connection polling once transaction support will be added [2]. [1] https://issues.apache.org/jira/browse/IGNITE-4191 [2] https://stackoverflow.com/questions/40498191/apache-ignite-jdbc-driver-jdbc-connection-pool-options On Wed, Jan 10, 2018 at 6:05 AM, rizal123 <khaerul.ri...@btpn.com> wrote: > Hi, > > I have a project/poc, about migrating database oracle into in memory apache > ignite. > > First of all, this is my topology. > <http://apache-ignite-users.70518.x6.nabble.com/file/ > t1530/Topology_Draft_1.png> > > in case image not showing: https://ibb.co/cbi5cR > > I have done this thing: > 1. Create node server cluster. And import schema oracle into it. > 2. Load data from Oracle into server cluster using LoadCache. > 3. From my application, change datasource into ignite cluster. (just only > one IP address). Currently i am using Jdbc Thin. > 4. Start my application, and its Up. It`s running well. > > I have the following problems: > 1. JDBC Thin, does not support Transactional SQL. I really need this ticket > to be fixed. > 2. Multi connection IP Address for JDBC Thin, or Load Balancer for JDBC > Thin. > 3. Automatic fail over. I have tested 1 machine, with 3 node cluster > server. > If the first node (That was first turn on) down, the connection will down > too. Though there are still 2 clusters that live. > > Please let me know if there any solution... > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Andrey V. Mashenkov
