You should create multiple cores when each core is an independent search. If you have three separate search pages, you may want three separate cores.
wunder Search Guy, Chegg.com On Mar 7, 2012, at 8:48 PM, Abhishek tiwari wrote: > please suggest me when one should create multiple core..? > > On Thu, Mar 8, 2012 at 12:12 AM, Walter Underwood > <wun...@wunderwood.org>wrote: > >> Solr is not relational, so you will probably need to take a fresh look at >> your data. >> >> Here is one method. >> >> 1. Sketch your search results page. >> 2. Each result is a document in Solr. >> 3. Each displayed item is a stored field in Solr. >> 4. Each searched item is an indexed field in Solr. >> >> It may help to think of this as a big flat materialized view in your DBMS. >> >> wunder >> Search Guy, Chegg.com >> >> On Mar 6, 2012, at 10:56 PM, Abhishek tiwari wrote: >> >>> thanks for replying .. >>> >>> In our RDBMS schema we have Establishment/Event/Movie master relations. >>> Establishment has title ,description , ratings, tags, cuisines >>> (multivalued), services (multivalued) and features (multivalued) like >>> fields..similarly in Event title, description, category(multivalued) and >>> venue(multivalued) ..fields..and in movies name,start date and end date >>> ,genre, theater ,rating , review like fields .. >>> >>> we are having nearly 1 M data in each entity and movie and event expire >>> frequently ....and we have to update on expire .... >>> we are having the data additional to index data ( stored data) to reduce >>> RDBMS query.. >>> >>> please suggest me how to proceed for schema design.. single core or >>> multiple core for each entity? >>> >>> >>> On Tue, Mar 6, 2012 at 7:40 PM, Gora Mohanty <g...@mimirtech.com> wrote: >>> >>>> On 6 March 2012 18:01, Abhishek tiwari <abhishek.tiwari....@gmail.com> >>>> wrote: >>>>> i am new in solr want help in shema design . i have multiple entities >>>>> like Event , Establishments and Movies ..each have different types of >>>>> relations.. should i make diffrent core for each entities ? >>>> >>>> It depends on your use case, i.e., what would your typical searches >>>> be on. Normally, using a separate core for each entity would be >>>> unusual, and instead one would flatten out typical RDBMS data for >>>> Solr. >>>> >>>> Please describe what you want to achieve, and people might be >>>> better able to help you. >>>> >>>> Regards, >>>> Gora >>>>
