Re: Write behind with data streamer

2015-10-13 Thread Andrew
Thanks for your replies. I made my code simpler, then it works well. It would be my mistake. Anyway, thanks again. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Write-behind-with-data-streamer-tp1598p1607.html Sent from the Apache Ignite Users mailing list a

Re: Write behind with data streamer

2015-10-13 Thread Raul Kripalani
Correct. In unit tests we normally use IgniteDataStreamer.autoFlushFrequency(10) to decrease the flush period to 10ms. Maybe try to do the same to discard a flushing problem – like Valentin suggested. *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messa

Re: Write behind with data streamer

2015-10-13 Thread vkulichenko
BTW, do you call IgniteDataStreamer.close() when there is more data to add? You should do this to make sure all the data is flushed from the streamer's buffers into the cache. If there are only several entries in your test, it can be the reason why they don't end up in the persistence store. -Val

Re: Write behind with data streamer

2015-10-13 Thread Raul Kripalani
Did you try setting the Streamer's allowOverwrite option? It would be interesting to see your code for further help. Regards, Raúl. On 13 Oct 2015 09:02, "Andrew" wrote: > Hi, all. > > I'm new to Ignite, and testing write behind with data streamer. > I made a cache using write-behind and then p

Re: Write behind with data streamer

2015-10-13 Thread vkulichenko
Hi Andrew, Write-behind persistence should work with the data streamer without any additional configuration changes. Note that in this case both data streamer and store are asynchronous, so there will be a delay between IgniteDataStreamer.addData() call and writing to the store. If this still doe

Re: Encountered incompatible class loaders for cache Error in Queries

2015-10-13 Thread Ivan Veselovsky
Is there a simple way to reproduce the problem on an independent environment? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Encountered-incompatible-class-loaders-for-cache-Error-in-Queries-tp1590p1602.html Sent from the Apache Ignite Users mailing list archive

Re: Encountered incompatible class loaders for cache Error in Queries

2015-10-13 Thread roar109
Both predicates are different class names and packages. Also are in different WAR's, are not duplicates in each. I tried a work around generating a single jar and deployed as a jboss module to be accesible by both wars and works fine (only in jboss #2 the client modes, jboss 1 stay without the jbo

Re: Ignite architecture

2015-10-13 Thread andy@bdp
Hi Dmitriy Thank you, for your reply. I didn't realize you had called into our office, but then I have been on-site for a long time. I initiated the conversation with Jim Leonard some time ago and would have liked to have met. I have looked through all the examples and am struggling to understan

Re: Using Json object to replace POJO

2015-10-13 Thread Dmitriy Setrakyan
On Mon, Oct 12, 2015 at 8:41 PM, xeseo wrote: > Thanks for reply. > well, for better understanding, I'll take an example. > Let's say I have a table in database, table A(C1,C2). > What I'm trying to do is reading content from database with the below SQL: > select C1 as empName, C2 as empScore fro

Write behind with data streamer

2015-10-13 Thread Andrew
Hi, all. I'm new to Ignite, and testing write behind with data streamer. I made a cache using write-behind and then put lots of data into cache with data streamer. I expected write-behind functionality had been executed but nothing happened. I guess the data store which I implemented has no p