We are looking into using elasticsearch and one of the use cases is
customerlists, for example a wishlist. So i can create a list (X-mas
shopping list) with a description, tags and some other metainformation. I
can then add items (with an identifier) to that list and also a custom
description for each item.
We would like to be able to :
- search through description, tags, etc...,
- sort on creating/mutationdate, and
- navigate on tags or other metainformation.
Conceptually you have a ListObject and it can contain 0 or many
ItemObjects. In a database this would probably mean 2 or more tables but
elasticsearch likes it's data flattened.
How would you model this in elasticsearch? Is it better to use nested or
parent-child relations, or simply flatten the data. The data isn't often
mutated and lists are usually very small.
itemId 123, itemdescription: aaa
itemId 456, itemdescription: bbb
itemId 789, itemdescription: ccc
Hope someone can give me some pointers or an example.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/79bd1fc0-770a-4545-a02b-dccd6764daf5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.