Did quick validation on my side. Could successfully preload data using JDBC thin driver and query it after the cluster restart. Used this script [1] and sqline tool mentioned in that GitHub project.
Please share: - configurations for cluster nodes. - log files from all the nodes and applications using JDBC driver (the logs are need before and after the restart). - source code you use. [1] https://github.com/dmagda/ignite_world_demo/blob/master/ignite_world.sql <https://github.com/dmagda/ignite_world_demo/blob/master/ignite_world.sql> — Denis > On Oct 6, 2017, at 3:19 PM, blackfield <[email protected]> wrote: > > I think it is unlikely I have problem described in IGNITE-6285. > It is consistent that the data on the table that is inserted via > IgniteDataStreamer (table created via Ignite getOrCreateCache) persist after > cluster restart. > > > I am using JDBC thin client, I both use it programmatically. I also > configured DBeaver to use DBeaver, same result. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
