Hi Yakav, Our requirement is to just be able to read partial content of large cache items without any concurreny overhead. read committed guarantees are good enough.
Are you saying the suggestion from afedotov (use entry processor within an optimistic, read committed transaction) will still serialize the entry processor invokes? We already built a good bit of our API based on that premise. If yes :( , how can you access your ignite cache from within IgniteCompute.affinityCall() ? thanks, Rajeev -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/EntryProcessor-and-Locks-tp16150p16379.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
