It is my understanding that for Ignite transactions to be ACID, we need to have the caches configured as FULL_SYNC. [ Some of the code seems to imply only at least one of the caches in the transaction needs to be FULL_SYNC, but that is outside the scope of my question. ]
The initial load of our caches takes a long time, because our StreamReceiver needs to use transactions because it is transforming the data. This phase is idempotent, and could easily be run as FULL_ASYNC. However, once the data is loaded, we need the guarantees associated with FULL_SYNC. Is there any way to accomplish that, short of adding the ability to change this cache setting dynamically? Is there any way to force transactions on caches not configured as FULL_SYNC to be FULL_SYNC? Thanks, -DH Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
