Currently, I have an index that collects the logs of a series of control centers, and obtain from them the technical data of their electrical consumption, on and off status, and other kinds of data that allow me to know the status of the said control center.
The mapping was created manually, to optimize storage and work costs to the maximum, and at the time of creation, a typical master-detail relationship was not created with the control center data, leaving this to the program that works with elasticSearch, since we were only interested in the issue of logs.
+------------------------+
| |
| |
| CommandCenter |
| |
| |
+---+------------+-----------+
| |
| |
+----v-----+ +----v-----+
| | | |
| | | |
| Log | | Log |
| | | |
| | | |
+----------+ +----------+ ...
Whenever I read about the subject, I see that all the documentation and help revolve around avoiding treating Elasticsearch as a relational DB, but my doubt comes from the need to show in the search results, observability, and others, a minimum of box information, such as your name, your location, etc.
Is it possible to have that master-detail relationship? Is it really as expensive as some tutorials or forums say?
A lot of thanks