I have a question about a data modeling in ElasticSearch to fulfill our use case.
We have 2 instances of data - traffic and sale which can be matched by clickout_id field. The relationship is one to many (one traffic clickout can cause multiple sales under same clickout_id) as in this schematic example.
Sometimes, traffic won't contain this "clickout_id" field, sometimes it will and it's a unique value.
I was revising different approaches, described here, namely:
- Nesting objects
- Storing data in different _types by providing different mappings within one index
- Children-parent relationship
Storing data in different _types, trying to emulate DBMS behaviour won't work, I asked this question earlier. If the field in mappings have the same name, Lucene will not handle it.
My issue is that applying nesting objects approach works fine in Elastic, but will not be working correctly in Kibana, as it does not recognize an array. Thus, I cannot build any visualizations.
The questions are:
- Perhaps I did a mistake when uploaded nested documents and/or mappings for specific index (I can describe the process).
- Maybe child-parent relationship will suit better, but I cannot see how can I apply this in Kibana
- The aim is to query documents in Kibana and Timelion freely
I would appreciate any hints,