Skip to content
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

[FEATURE] Support Opensearch API #798

Open
3 tasks done
autata opened this issue Mar 12, 2024 · 0 comments
Open
3 tasks done

[FEATURE] Support Opensearch API #798

autata opened this issue Mar 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@autata
Copy link
Contributor

autata commented Mar 12, 2024

Description

Opening this issue to track support for the Opensearch API. This is to replace the draft PR: #780

I'm new to this project, so I can't outline each of the places support is missing, but it would be valuable to support the spec. In particular, (_msearch and range query) in their entirety.

For example if either lte or gte are missing, astra return a 500 (Internal Server Error) response due to null pointer exception. In Opensearch these are not required. Also a 500 is not ideal. Perhaps 400 (Bad Request) and a helpful error string would be better if not implementing the API.

For now, I've closed the draft PR that shows this issue. Because it looks like Opensearch will be implemented in a few months, it probably doesn't make sense to do one-off changes to the return codes.

Requirements (place an x in each of the [ ])

  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant