Hi - We are designing a system for reporting and are planning to use
Elastic search as a backend. We want to expose reporting in such a way that
users can build custom reports on top of their data without us coming in
their way. One way to do this is to expose elastic search query APIs
through our public endpoints. The other option is to use an abstraction
language which get translated to elastic search queries in the middle tier.
The latter option allows us to control what runs on ES but can become
restrictive in terms of how much we expose the rich query mechanism of ES
using the abstraction layer. I would like to know if there is a known
design pattern to solve this. How have users of elastic search addressed
flexibility vs. control?
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 email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7b09e135-578d-420a-9dc6-da503e4b3163%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.