thanks Pravesh for your feedback. I have 10 million products and 165M rows of visits accumulated for 2 years. The data-aggregated needs to be shown in the search result page along with the product description.
I also felt option 2 was the most suitable but wanted to have a second view. The only hesitation here is the overhead in doing 2 queries (1 to products and 1 to visits) for every search that could impact in performance. Regards, Esteban On Fri, Oct 14, 2011 at 8:35 AM, pravesh <suyalprav...@yahoo.com> wrote: > Hi Esteban, > > A lot depends on a lot of things: 1) How much volume(total documents) 2) > size of index 3) How you represent the data-aggregated part in your UI. > > Your option-2 seems to be a suitable way to go. This way you tune each cores > separately. Also the use-cases for updating each document/product in both > indexes also seems different. One is updated when a product is > added/updated. Other is updated when a product in viewed/sold from search > results > > Option-1 can be used in case you are showing the data-aggregation stats on > the search results page only along with each item. If it is shown in the > item-detail page then option-1 seems better. > > Regds > Pravesh > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/text-search-and-data-aggregation-thoughts-tp3416330p3421361.html > Sent from the Solr - User mailing list archive at Nabble.com. >
