Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
Date: Fri, 7 Jul 2017 11:42:25 -0700 (MST)
From: vkulichenko <valentin.kulichenko@gmail.com>
To: user@ignite.apache.org
Message-ID: <1499452945325-14501.post@n6.nabble.com>
In-Reply-To: <CAKV011r+ON-_rO2hPNBaSKDNNtqpYvS+TC3gwABGo2y9BqXO_g@mail.gmail.com>
References: <CAKV011r+ON-_rO2hPNBaSKDNNtqpYvS+TC3gwABGo2y9BqXO_g@mail.gmail.com>
Subject: Re: Ignite Info
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Fri, 07 Jul 2017 18:42:29 -0000

Hi,


Riccardo Iacomini wrote
>    - Will a local file system persistence strategy be available in future
>    releases of Ignite?

The new disk storage will be available in 2.1.


Riccardo Iacomini wrote
>    - Using the write-behind mode, will operations on the cache still be
>    mapped 1 on 1 on the underlying persistence system, in my specific
> case,
>    Cassandra?
> 
> Expanding on this, multiple operations on the same cache key will be all
> executed (in batch) when the write is triggered, or only the last version
> will be written?

Nothing changes if you use Cassandra or any other arbitrary store, this
functionality stays the same. New disk storage is not related to this.
Answering you particular question: it's controlled by
CacheConfiguration#writeBehindCoalescing property which is available in both
1.x and 2.x.

-Val


--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Info-tp14473p14501.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.