Shards are "special" cores, usually hosted on separate machines that comprise one single large (logical) index. Shards need to have the same schema, config, etc usually.
So unless you have a corpus that's too large to fit on a single piece of your hardware, you'll always be using "cores". And since your cores have different types of data (and presumably use different schemas), you're talking cores. Best Erick On Tue, Aug 6, 2013 at 10:49 PM, manju16832003 <manju16832...@gmail.com>wrote: > Hi, > I have a confusion over choosing Cores or Shards for the project scenario. > My scenario is as follows > I have three entities > 1. Customers > 2. Product Info > 3. Listings [Contains all the listings posted by customer based on > product] > > I'm planning to design Solr structure for the above scenario like this > 1. Customers Core > 2. Product Info Core > 3. Listings Core > 4. Searchable Listing Core [Indexing searchable parameters selected from > Listings, Product Info and Customer entities]. > > Having in mind that there wouldn't be much updates to Customers, Product > Info. There will be regular updates to Listings that in turn I need to > update Searchable listings that I could manage it. > > My Confusion is it feasible to choose many cores or use shards. I do not > have much experience on how shards works and why they are used for. I would > like to know the suggestions :-) for the design like this. > What are the implications if I were to choose to use many cores and handle > stuff at application level calling different cores. > > Thanks > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-design-Choose-Cores-or-Shards-tp4082930.html > Sent from the Solr - User mailing list archive at Nabble.com. >
