Re: Write behind and eventual consistency

2017-05-04 Thread vkulichenko
-users.70518.x6.nabble.com/Write-behind-and-eventual-consistency-tp12242p12438.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Write behind and eventual consistency

2017-05-03 Thread Gaurav Bajaj
of write behind I cannot maintain >> referential integrity (since the insert/update are done in a random order) >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Write-behind-and-eventual-consistency-tp12242p12287.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >

Re: Write behind and eventual consistency

2017-04-27 Thread Gaurav Bajaj
grity (since the insert/update are done in a random order) > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Write-behind-and-eventual- > consistency-tp12242p12287.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >

RE: Write behind and eventual consistency

2017-04-27 Thread steve.hostettler
ignite-users.70518.x6.nabble.com/Write-behind-and-eventual-consistency-tp12242p12287.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

RE: Write behind and eventual consistency

2017-04-27 Thread vkulichenko
Hi Steve, What is the business use case behind this? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Write-behind-and-eventual-consistency-tp12242p12285.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

RE: Write behind and eventual consistency

2017-04-26 Thread Steve Hostettler
Hello Val, Thanks for your help. Don't you think that this would be an interesting functionality? Steve -Original Message- From: vkulichenko [mailto:valentin.kuliche...@gmail.com] Sent: Wednesday, April 26, 2017 9:57 AM To: user@ignite.apache.org Subject: Re: Write behind and eventual

Re: Write behind and eventual consistency

2017-04-26 Thread vkulichenko
There is no way to do this. However, you can take a look at GridCacheWriteBehindStore which implements this functionality and try tweaking it so that the queue size is exposed somehow. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Write-behind

Re: Write behind and eventual consistency

2017-04-25 Thread steve.hostett...@gmail.com
e-users.70518.x6.nabble.com/Write-behind-and-eventual-consistency-tp12242p12247.htmlSent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Write behind and eventual consistency

2017-04-25 Thread vkulichenko
ight after or concurrently with this check? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Write-behind-and-eventual-consistency-tp12242p12247.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Write behind and eventual consistency

2017-04-25 Thread steve.hostettler
anything like that. What would you advise to do? Many thanks in advance Best Regards -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Write-behind-and-eventual-consistency-tp12242.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.