@Gora: >One wants to index "just >enough" data in the search engine. Plus, if one wants to do relevant >searches in large text blobs, documents, etc., those should be in the >search engine: Databases are bad at such searches.
Perhaps you took me wrong.. :) may be I couldn't make that clear. I am indexing all the data required to be searched in Solr. All of my fields have directly or indirectly(via copyfields) *indexed=true *but * stored=false.* But as Francois pointed out that I should be opting with *stored=false *for some of the fields to show search results. I was planning that out of the indexed data when solr gives me a list of document ids in the response I would then use the DB to get the full data of the relevant items. > It is unlikely that they are going to bee searching by IDs. Of course, not & I dont index my id field, so it is not even an option. They search using keywords, category filters etc using the indexed(but unstored) fields in solr. On Sun, Oct 6, 2013 at 9:57 PM, Gora Mohanty <g...@mimirtech.com> wrote: > On Oct 6, 2013 9:50 PM, "Gora Mohanty" <g...@mimirtech.com> > > In particular, I would say that using just the ID in the search engine > makes little sense. > > To elaborate further, you should be approaching the issue from the > perspective of the searches that your end users are likely to be doing. It > is unlikely that they are going to bee searching by IDs. > > Regards, > Gora >
