ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Tupitsyn <ptupit...@apache.org>
Subject Re: cache update from .NET client to Java cluster
Date Fri, 17 Mar 2017 05:26:51 GMT
> new entry get created in the map

Updating an entry in Ignite cache is not just updating some map;
it is a distributed operation that may update multiple memory/disk
locations on multiple machines,
depending on cache mode, number of backups, swap storage, etc.

Anyway, these are implementation details, and I'm not very familiar with
this part of code.
You can write to dev@ignite.apache.org and ask for technical details there.

Or is there something from the user point of view that affects you?
Because from public API pov, I don't think this matters.

On Fri, Mar 17, 2017 at 4:19 AM, kfeerick <
kevin.feerick@ninemilefinancial.com> wrote:

> /When you update the entry and call cache.Put, it gets serialized and then
> sent to the server node./
> Thanks Pavel,
> Perhaps I'm missing something here but I would expect the existing entry to
> get updated do to key equivalence rather than a new entry get created in
> the
> map?
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/cache-update-from-NET-client-to-
> Java-cluster-tp11217p11261.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message