We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
opensearch
In #3198 we added ability to auto-detect OpenSearch storage. Would it make sense to add opensearch as a valid backend choice for SPAN_STORAGE_TYPE?
SPAN_STORAGE_TYPE
cc @pavolloffay @jkowall @albertteoh @Ashmita152
The text was updated successfully, but these errors were encountered:
I don't see much value by adding opensearch as a valid storage option right now. It will make more sense once opensearch implementation diverges.
That said I don't have a strong opinion to add it right now and use the same implementation for both elasticsearch and opensearch.
Sorry, something went wrong.
Yes, I meant using the same implementation for now. Having explicit opensearch option would server to goals:
@pavolloffay #3255
Successfully merging a pull request may close this issue.
In #3198 we added ability to auto-detect OpenSearch storage. Would it make sense to add
opensearch
as a valid backend choice forSPAN_STORAGE_TYPE
?cc @pavolloffay @jkowall @albertteoh @Ashmita152
The text was updated successfully, but these errors were encountered: