Scenario 1: If you know the object doesn't exist or you want to overwrite it (because allow_multi is not enabled), you want to call withoutFetch() - there's no reason to fetch something from Riak if it's not there (not found) or you don't care what the value is currently (and again, are not creating siblings)
Scenario 2: If you want to ... but since you're not fetching in the first place the result should be exactly what is in your Mutation. - Roach On Thu, Jan 31, 2013 at 6:14 AM, Guido Medina <guido.med...@temetra.com> wrote: > Hi, > > I have doubts about withoutFetch() and returnBody(boolean), I will put some > scenarios: > > Store object (or overwrite) existing Riak object where I'm 100% I don't need > to fetch from Riak (Last write wins and goes to memory cache) > Apply a mutation to an object but this time return the mutated instance from > the Riak operation without fetching it from Riak cluster (via apply()?) so > that the mutated result gets updated in memory cache. > > I want to use accurately both methods but I'm a bit lost with their use > case, so, is it safe to assume the following? > > Scenario 1: execute() without calling withoutFetch() and returnBody(false) > because both by default are false? > Scenario 2: execute() with returnBody(true) so I get the result of > Mutation.apply()? > > All described scenarios have no siblings enabled and use default converter > (Domain POJO annotated with Jackson) > > Thanks in advance for the response(s), > > Guido. > > > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
