Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Walter Underwood <wunder@wunderwood.org>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-10-687757573
Subject: Re: schema design help
Date: Wed, 7 Mar 2012 20:51:15 -0800
In-Reply-To: 
 <CA+CUyFM+Hy404LT1J+G8LE7GQ_W5WHvWJyDNFj6rEZdGCCdeEw@mail.gmail.com>
To: solr-user@lucene.apache.org
References: 
 <CA+CUyFOhFvpsVS2PoxuUgpwnrqNJd8XD=-Hg=Bocrp0GS2_YyQ@mail.gmail.com>
 <CACiMRGJK4v8F3nPKFpqB66fr=wjOgK3jB8S_RNiBNkhrVu+QeQ@mail.gmail.com>
 <CA+CUyFPZTd=6at0z0CtgiEUphYVKCBGdNCScMRdexTMuk-zV6w@mail.gmail.com>
 <0AE2C1C7-6B2E-42D2-8016-A5736A013219@wunderwood.org>
 <CA+CUyFM+Hy404LT1J+G8LE7GQ_W5WHvWJyDNFj6rEZdGCCdeEw@mail.gmail.com>
Message-Id: <EEF87B0D-CB36-4401-90CF-4836F0B8E6F8@wunderwood.org>

--Apple-Mail-10-687757573
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

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..?
>=20
> On Thu, Mar 8, 2012 at 12:12 AM, Walter Underwood =
<wunder@wunderwood.org>wrote:
>=20
>> Solr is not relational, so you will probably need to take a fresh =
look at
>> your data.
>>=20
>> Here is one method.
>>=20
>> 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.
>>=20
>> It may help to think of this as a big flat materialized view in your =
DBMS.
>>=20
>> wunder
>> Search Guy, Chegg.com
>>=20
>> On Mar 6, 2012, at 10:56 PM, Abhishek tiwari wrote:
>>=20
>>> thanks for replying ..
>>>=20
>>> 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 ..
>>>=20
>>> 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..
>>>=20
>>> please suggest me how to proceed for schema design.. single core or
>>> multiple core for each entity?
>>>=20
>>>=20
>>> On Tue, Mar 6, 2012 at 7:40 PM, Gora Mohanty <gora@mimirtech.com> =
wrote:
>>>=20
>>>> On 6 March 2012 18:01, Abhishek tiwari =
<abhishek.tiwari.tek@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 ?
>>>>=20
>>>> 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.
>>>>=20
>>>> Please describe what you want to achieve, and people might be
>>>> better able to help you.
>>>>=20
>>>> Regards,
>>>> Gora
>>>>=20


--Apple-Mail-10-687757573--