-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate elastic/opensearch forks #978
Comments
Hey @Jeffail Some people ( me too ) want to run their own Elastic equivalent. There is a golang equivalent that matches the Elastic API closely https://github.com/prabhatsharma/zinc Its getting alot of attention. I guess tons of people want an efficient alternative. It works well. It's based on bluge: https://github.com/blugelabs/bluge ( thankyou @mschoch ). |
@Jeffail I would be interested in seeing a dedicated output for OpenSearch built against the aforementioned opensearch-go. We could ask the coordinators of https://opensearch.org/events/ to allow you to present, showing off Benthos and its OpenSearch integration. |
@Jeffail I can contribute in creating a dedicated opensearch output sink. Let me know. |
Go ahead if you have cycles to spare. All new contributors are welcome! Happy to help you get it in shape for merging |
I'm on it. Thanks! |
The official Go Client Library for OpenSearch - https://github.com/opensearch-project/opensearch-go |
The We still need to migrate from |
is there any process for opensearch input componements? |
The dust is starting to settle now since the opensearch fork so it's probably worth spending some time understanding what's needed in order to continue to support both offerings. We're currently using https://github.com/olivere/elastic which has been fantastic (more info about future direction here: olivere/elastic#1533) but we could also consider moving to the official client libraries as we only use a small fraction of ES endpoints.
Official libraries:
Questions:
opensearch
component?The text was updated successfully, but these errors were encountered: