Hi The approach I take is to store enough data in the SOLR index to render the results page, and go to the database if the user want to view a document.
Cheers François On Oct 6, 2013, at 9:45 AM, user 01 <user...@gmail.com> wrote: > @Gora: > you understood the schema correctly, but I can't believe it's strange but i > think it is actually the recommended way.. you index your data but don't > store in a Search engine, you store your actual data in DB, which is the > right place for it. Data in SE should be just used for indexing. Isn't it ? > > @maephisto: ok, thanks! > > > On Sun, Oct 6, 2013 at 6:07 PM, Gora Mohanty <g...@mimirtech.com> wrote: > >> On 6 October 2013 16:36, Ertio Lew <ertio...@gmail.com> wrote: >>> I meant that solr should not be thinking that it has to retrieve any >> thing >>> further (as in any stored document data) after once it gets the doc id, >> so >>> that one further look up for doc data is prevented. >> [...] >> >> If I understood your setup correctly, the doc ID is the only field >> in the Solr schema, and the only data stored in the Solr index. >> So there is no question of recovering any other data. >> >> Having said that, this is a strange setup and seems to defeat the >> whole purpose of a search engine. Maybe you could explain further >> as to what you are trying to achieve: What does storing only doc >> IDs in Solr gain you? You could as well get these from a database >> lookup which it seems that you would be doing anyway. >> >> Regards, >> Gora >>
