Re: 1 main collection or multiple smaller collections?

Derek You could have one document per supplier which has no product info. It would have a flag to indicate this. Then your supplier search is simple. But grouping would be better, so the supplier search can show product counts and categories and ... +1 Walter on designing back from the

Re: 1 main collection or multiple smaller collections?

Richard Iam considering the sameoption asyour suggestion to put them in 1 single collection of products documents. A product doccontaining the supplier info. In this option, a supplier info will get repeated in eachof the supplier's product doc.I may be influenced by DB concepts. Guess it's a

Re: 1 main collection or multiple smaller collections?

Hi Shawn 1 set of data is suppliers info and 1 set isthe suppliers products info. Usercan eitherdo a product search or a supplier search. 1 optionI am thinking of is to put them in 1 single collectionwith each product as a document. Each productdocument will have the supplier info in it.

Re: 1 main collection or multiple smaller collections?

Design backwards from the search result pages (SRP). Make flat schema(s) with the fields you will search and display. One example is the schema I used at Netflix. I used one collection to hold movies, people (actors), and genres. There were collisions between the integer IDs, movies IDs were

Re: 1 main collection or multiple smaller collections?

Does it make sense to use nested documents here? Products could be nested in a supplier document perhaps. Alternately, consider de-normalizing "til it hurts". A product doc might be able to contain supplier info. On April 27, 2017 8:50:59 AM EDT, Shawn Heisey wrote: >On

Re: 1 main collection or multiple smaller collections?

On 4/26/2017 11:57 PM, Derek Poh wrote: > There are some common fields between them. > At the source data end (database), the supplier info and product info > are updated separately. In this regard, I should separate them? > If it's In 1 single collection, when there are updatesto only the >

Re: 1 main collection or multiple smaller collections?

There are some common fields between them. At the source data end (database), the supplier info and product info are updated separately. In this regard, I should separate them? If it's In 1 single collection, when there are updatesto only the supplier info,the product info will be index again

Re: 1 main collection or multiple smaller collections?

Also, 300,000 documents is fairly small for Solr. We handle a million queries per day with a few servers on a collection that size. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Apr 26, 2017, at 10:33 PM, Walter Underwood

Re: 1 main collection or multiple smaller collections?

Do they have the same fields or different fields? Are they updated separately or together? If they have the same fields and are updated together, I’d put them in the same collection. Otherwise, probably separate. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/

1 main collection or multiple smaller collections?

Hi I amplanning for a migration of a legacy searchengine to Solr. Basically thedata can be categorisedinto suppliersinfo, suppliers products info and products category info. These sets of data are related to each other. suppliers products data, which is the largest, have around 300,000 records