Skip to content

Workaround to use with elasticsearch gem 7.14 or later #77

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

Conversation

Fumipo-Theta
Copy link

Because of the change of the elasticsearch gem (elastic/elasticsearch-ruby#1360), AWS OpenSearch has not been supported.
Maybe relates to

I think we need some workaround.

My suggestion is based on this comment.
This method will allow any versions and any distributions of elasticsearch.
I confirmed that I could transfer messages to AWS OpenSearch Service.

I'm a beginner and I can't think of a better way...
If there is a better way, I would love to hear advices.

@Fumipo-Theta
Copy link
Author

The new fluent plugin will be made for OpenSearch (mentioned in uken/fluent-plugin-elasticsearch#915 (comment)).
If it is released, would it be better to fork a new project with using OpenSearch compatible plugin?

cosmo0920 added a commit to fluent/fluent-plugin-opensearch that referenced this pull request Jan 12, 2022
cosmo0920 added a commit to fluent/fluent-plugin-opensearch that referenced this pull request Jan 12, 2022
@cosmo0920
Copy link
Collaborator

We're planning AWS OpenSearch Service AWS SignV4 request support on fluent-plugin-opensearch plugin itself:
fluent/fluent-plugin-opensearch#2

Thanks for the incompatibility notification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants