Hi Ivan,
Generally the denormalization strategies you might use to optimize a
relational database are antipatterns when dealing with Solr, so I
wouldn't hesitate to give this option a try. Solr's very good at
reducing the footprint of a field value duplicated across many
documents down to a simpl
Hi Michael,
As I can see there are two directions how to do that:
1) store all package data in product documents
2) have separate documents for packages
In reality there are lots of packages for every product.
So if I make document for every combination product+package I'll get lots of
documents
Hello Puska,
I might not have understood your requirements, but if for a given
user, there's only one package per product that should ever be
retrieved, I'd make the document represent one package/price
combination, and then use a filter query to ensure the user's searches
only retrieve package/pr
