Paul, I'm not quite sure I understand what you're asking.
If you do a fetch and have siblings each one is converted to your domain object using the Converter and then passed as a Collection to the ConflictResolver. Each sibling is going to include its links and/or indexes as long as the Converter is injecting them into the domain object and you can resolve them in the ConflictResolver. The default JSONConverter, for example, injects them into your domain object via annotations from the com.basho.riak.client.convert[1] package. Thanks, Brian Roach http://basho.github.io/riak-java-client/1.4.0/com/basho/riak/client/convert/package-summary.html On Tue, Jul 30, 2013 at 11:41 AM, Paul Ingalls <[email protected]> wrote: > Newbie with Riak, and looking at the java client. > > Specifically, I've been digging into the domain mapping apis. Looking into > the code, it appears to me that, if I'm using links a bunch or even > secondary indexes, that I could lose some data during the conflict > resolution phase. I see where links and other relevant user data gets > cached during the conversion phase from the fetch and then patched back in > during the conversion phase for the store. However, it doesn't look like > you have the opportunity during the resolution phase to merge metadata. > Should I focus on using the raw client, or am I missing something? > > Thanks! > > Paul > > > > > Paul Ingalls > Founder & CEO Fanzo > [email protected] > @paulingalls > http://www.linkedin.com/in/paulingalls > > > > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
