That's a great use case cause it's not ad hoc (worst case). Your pre compute/cache solution will work whichever approach you take. Then the question just becomes space vs compute.
On Wednesday, May 11, 2016, Alex De la rosa <alex.rosa....@gmail.com> wrote: > My use case for searching is mainly for internal purposes, rankings and > statistics (all that data is pre-compiled and stored into final objects for > the app to display)... so I think is best to not store anything in SOLR and > just fetch keys to compile the data when required. > > Thanks, > Alex > > On Wed, May 11, 2016 at 10:40 PM, Alexander Sicular <sicul...@basho.com > <javascript:_e(%7B%7D,'cvml','sicul...@basho.com');>> wrote: > >> Those are exactly the two options and opinions vary generally based on >> use case. Storing the data not only take up more space but also more io >> which makes things slower not only on read time , but more crucially , at >> write time. >> >> Often people will take a hybrid approach and store certain elements like >> , say , for blog posts , the author , publish date and title fields. Yet >> they will leave the body out of the solr index. That way you could quickly >> generate lists of posts by title and only fetch the body when the post is >> clicked through. >> >> What is your use case? >> >> Best, >> Alexander >> >> On Wednesday, May 11, 2016, Alex De la rosa <alex.rosa....@gmail.com >> <javascript:_e(%7B%7D,'cvml','alex.rosa....@gmail.com');>> wrote: >> >>> Hi all, >>> >>> When creating a SOLR schema for Riak Search, we can chose to store or >>> not the data we are indexing, for example: >>> >>> <field name="firstname" type="string" indexed="true" *stored="false"* /> >>> >>> I know that the point to have the value stored is to be able to get it >>> returned automatically when doing a search query... that implies using more >>> disc to store data that maybe never would be searched and making the return >>> slower as more bytes are required to get the data. >>> >>> Would it be better to just index data but not store the values, >>> returning only Riak IDs (_yz_id) and then doing a multi-get in the >>> client/API to fetch the objects for the final response? >>> >>> Or would it be better to store the values in SOLR so they will be >>> already fetched when searching? >>> >>> What would give better performance or more sense in terms of disc space >>> on an application that normally you won't be using much searching (all data >>> is more or less discoverable without searching using GETs) >>> >>> Thanks and Best Regards, >>> Alex >>> >> >> >> -- >> >> >> Alexander Sicular >> Solutions Architect >> Basho Technologies >> 9175130679 >> @siculars >> >> > -- Alexander Sicular Solutions Architect Basho Technologies 9175130679 @siculars
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
