lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Kildén <>
Subject Help with design choice: join or multiValued field
Date Mon, 06 Feb 2017 10:57:34 GMT

I have Items and I have Shops. This is a e-commerce system with items from
thousands of shops all though the inventory is often similar between shops.
Some users can shop from any shop and some only from their default one.

One item can exist in about 10000 shops.

   - When a user logs in they may have a shop pre selected so when they
   search for items we need to get all matching documents but if it's' found
   in their pre selected shop we should mark it out in the UI.
   - They need to be able to filter out only items in their current shop
   - Items found in their shop should always be boosted heavily


Either we just have a multiValued field on the item document with all
shops. This would be a multivalued field with 10000 rows


Could we have a new document ShopItem that has the shopId and the itemId
(think join table). Then we join this document instead... But we still need
to get the Item document back, and we need bq boosting on item?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message