That is correct. Storing values in solr make the values redundant. That's because solr and Riak are different systems with different storage strategies. Since we only return the solr results, the only way we can access the kv values would be to make a separate call, which is not much different from your client making that same call.
As for separating Riak Search from kv entirely, this is a possibility we've looked into, but it won't be ready for 2.0. I'm sorry to say that, for the time being, the only option for your request is to store values in both places. Eric On Mar 26, 2014 10:05 AM, "Elias Levy" <[email protected]> wrote: > On Wed, Mar 26, 2014 at 9:44 AM, Eric Redmond <[email protected]> wrote: > >> The newest Riak Search 2 (yokozuna) allows you to create custom solr >> schemas. One of the field options is to save the values you wish to index. >> Then when you perform a search request, you can retrieve any of the stored >> values with a field list (fl) property >> > Certainly, but that makes the KV storage redundant. If that is really the > suggested solution, then there may as well be a null storage KV backend. > > Of curse, a null KV backend is not sufficient, given that writes to > Yokozuna happen asynchronously and that AAE is used to ensure KV and > Yomozuna are in sync. You'd also need to make writes to Yokozuna > synchronous with the client request and disable AAE as there is nothing to > sync with. > > > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
