Hi,
So for your use case are you wanting to search for a consultant then
look at all of his or her request or pull both at the same time? In
both cases one index should suffice. In you define a primary key field
and use it for both doc types it shouldn't be an issue. Unless your
dataset in very large it would reduce the overhead of running a
multicore solution especially in indexing etc
David Stuart
On 28 May 2010, at 18:12, Moazzam Khan <moazz...@gmail.com> wrote:
Thanks for all your answers guys. Requests and consultants have a many
to many relationship so I can't store request info in a document with
advisorID as the primary key.
Bill's solution and multicore solutions might be what I am looking
for. Bill, will I be able to have 2 primary keys (so I can update and
delete documents)? If yes, can you please give me a link or someting
where I can get more info on this?
Thanks,
Moazzam
On Fri, May 28, 2010 at 11:50 AM, Bill Au <bill.w...@gmail.com> wrote:
You can keep different type of documents in the same index. If each
document has a type field. You can restrict your searches to
specific
type(s) of document by using a filter query, which is very fast and
efficient.
Bill
On Fri, May 28, 2010 at 12:28 PM, Nagelberg, Kallin <
knagelb...@globeandmail.com> wrote:
Multi-core is an option, but keep in mind if you go that route you
will
need to do two searches to correlate data between the two.
-Kallin Nagelberg
-----Original Message-----
From: Robert Zotter [mailto:robertzot...@gmail.com]
Sent: Friday, May 28, 2010 12:26 PM
To: solr-user@lucene.apache.org
Subject: Re: Storing different entities in Solr
Sounds like you'll want to use a multiple core setup. One core
fore each
type
of "document"
http://wiki.apache.org/solr/CoreAdmin
--
View this message in context:
http://lucene.472066.n3.nabble.com/Storing-different-entities-in-Solr-tp852299p852346.html
Sent from the Solr - User mailing list archive at Nabble.com.
