Re: Help with design choice: join or multiValued field

2017-02-14 Thread Karl Kildén
Thanks for the reply! We did it this way and it's seems to turn out really well On 6 February 2017 at 22:57, Fuad Efendi wrote: > Correct: multivalued field with 1 shop IDs. Use case: shopping network > in U.S. for example for a big brand such as Walmart, when user implicitly > provides IP a

Re: Help with design choice: join or multiValued field

2017-02-06 Thread Fuad Efendi
Correct: multivalued field with 1 shop IDs. Use case: shopping network in U.S. for example for a big brand such as Walmart, when user implicitly provides IP address or explicitly Postal Code, so that we can find items in his/her neighbourhood. You basically provide “join” information via this