Closed maximepln closed 1 year ago
Hi @lvaylet, @bkamin29
What are your thought on this ?
I had to disable py-lint code duplication to have the CI to pass.
Hi @maximepln, thanks a lot for this submission. I will take a look at it shortly. Regarding your choice of going with two different backends (with some duplicate code), I ended up doing the exact same thing to support MQL in Cloud Monitoring on top of the existing MQF backend.
Thanks for the feedback @lvaylet,
I updated to code to use OpenSearch
instead of Opensearch
Don't hesitate if you have any other comments
Hi @lvaylet,
Sorry for the delay to respond, I was away on holiday.
Hope everything is fine now
hello @lvaylet, any updates ?
I will take a look tomorrow afternoon.
Everything is in the title but I will add a bit of details
The goal of that PR is to implement a new backend provider
Opensearch
For instance, I opened an issue about this there: Issue 346, in which I explained why the
Elasticsearch
wasn't usable withOpensearch
As you will see, some code could have been mutualised between the two backend. But as we don't know the direction that will take the 2 backends in the future, and due to the fact that they could become quite different, I chose to avoid adding too much complexity.
Furthermore, most of the people will work on either
Opensearch
orElasticsearch
so having a common codebase could become complicated when wanting to add new features.Everything is documented in the right directories and unit tests & mocks were implemented.