Hi, It’s unlikely but, anyway, please confirm you haven’t faced this issues: https://issues.apache.org/jira/browse/IGNITE-6285 <https://issues.apache.org/jira/browse/IGNITE-6285>
What type of JDBC driver are you on? If it’s Ignite Client Driver [1] and you set “streaming” parameter to “true” double check the connection is properly closed [2] (otherwise the data might not be flushed). If nothing helps share a reproducer with us to facilitate the debugging. If the bug is confirmed you’ll be able to get a fix in the nearest weeks. The community is preparing 2.3 release. [1] https://apacheignite.readme.io/docs/jdbc-driver#section-jdbc-client-node-driver [2] https://apacheignite.readme.io/docs/jdbc-driver#section-streaming-mode <https://apacheignite.readme.io/docs/jdbc-driver#section-streaming-mode> — Denis > On Oct 6, 2017, at 1:58 PM, blackfield <[email protected]> wrote: > > Hi, > > I configure my Ignite 2.2 nodes to enable persistence to disk. > > > <property name="persistentStoreConfiguration"> > <bean > class="org.apache.ignite.configuration.PersistentStoreConfiguration"/> > </property> > > After cluster restart, I notice that data that is inserted via JDBC is gone. > > Note: if I programmatically create the cache/table and insert entries to the > cache, these data persist properly after cluster restart. > > How to reproduce? > 1. Enable persistence > 2. Create simple table via SQL > 3. Insert data via SQL > 4. restart Ignite cluster and perform query against the table > > Am I missing some other configuration or is this a bug in 2.2? > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
