Closed vishnuchalla closed 1 year ago
@rook and @rsevilla87 - Both elasticsearch
and opensearch
APIs share exactly same code (See elastic.go
and opensearch.go
). We can have any one of them for indexing functionality or else both in case we want to have some backward compatability. My idea is to fully migrate to opensearch
.
Related blogs:
Please feel free to share your thoughts here. Thanks!
@rook and @rsevilla87 - Both
elasticsearch
andopensearch
APIs share exactly same code (Seeelastic.go
andopensearch.go
). We can have any one of them for indexing functionality or else both in case we want to have some backward compatability. My idea is to fully migrate toopensearch
. Related blogs:* https://dattell.com/data-architecture-blog/opensearch-vs-elasticsearch/ * https://logit.io/blog/post/aws-elasticsearch-vs-opensearch/
Please feel free to share your thoughts here. Thanks!
thanks for the research!, I don't have a strong opinion on this, but I think we can keep both for backwards compatibility in case any user is using a recent version of elasticsearch (OpenSearch is compatible up to the 7.10 version). I'll add some notes to the kube-burner docs about this.
@rook and @rsevilla87 - Both
elasticsearch
andopensearch
APIs share exactly same code (Seeelastic.go
andopensearch.go
). We can have any one of them for indexing functionality or else both in case we want to have some backward compatability. My idea is to fully migrate toopensearch
. Related blogs:
- https://dattell.com/data-architecture-blog/opensearch-vs-elasticsearch/
- https://logit.io/blog/post/aws-elasticsearch-vs-opensearch/
Please feel free to share your thoughts here. Thanks!
Yeah - opensearch works fine for me... k8s-netperf started with opensearch, so I would defer to @rsevilla87 on eventually moving to opensearch from es.
Hey @vishnuchalla, I just sent a PR to your fork's branch containing the logger interface abstraction we discussed about in yesterday's meeting. https://github.com/vishnuchalla/go-commons/pull/1
Hey @vishnuchalla, I just sent a PR to your fork's branch containing the logger interface abstraction we discussed about in yesterday's meeting. vishnuchalla#1
@rsevilla87 - Thanks for the quick help. IMHO, I don't think we should be passing logger as an argument to functions in go-commons
(because we do not do it for any of the go imports in our code). Instead, either
Open for other thoughts too. Please let me know your thoughts here. Thank you!
cc: @jtaleric
Description
Adding indexers to go commons.
Testing
Tested integrating with kube-burner for elastic indexer.
Tested integrating with kube-buner for opensearch indexer as well.