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

[BUG] Async-Search in OS 3.0 #607

Closed
Tokesh opened this issue Aug 25, 2024 · 1 comment · Fixed by #641
Closed

[BUG] Async-Search in OS 3.0 #607

Tokesh opened this issue Aug 25, 2024 · 1 comment · Fixed by #641
Labels
bug Something isn't working

Comments

@Tokesh
Copy link

Tokesh commented Aug 25, 2024

What is the bug?
Hello everyone!
I wrote specs for async-search in OpenSearch-api-specification repo
We test all our PRs in different versions of OpenSearch.
So, as i understand, async-search is already available in OS 3.0, but i cant find a tag that i can use.
I tried using the latest tag, but it doesnt work.
Do I understand correctly that async search should be in version 3.0?

How can one reproduce the bug?
use async-search APIs with latest tag of OS 3.0
mostly i got [INFO] <= 400 (application/json) | "no handler found for uri [/_plugins/_asynchronous_search] and method [POST]"

What is the expected behavior?
It should work in 3.0 the same as in 2.x, or its bug

What is your host/environment?
Docker CI configs

  • OS: Ubuntu
  • Version 22.04
  • Plugins

Do you have any additional context?
I'm newbie at this repo. I’m always happy to make new connections and meet friendly people here. You can ask me any questions, I will try to answer as quickly as possible and my colleagues from our repository.

@Tokesh Tokesh added bug Something isn't working untriaged labels Aug 25, 2024
@dblock dblock removed the untriaged label Sep 16, 2024
@dblock
Copy link
Member

dblock commented Sep 16, 2024

[Catch All Triage - 1, 2, 3, 4, 5]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants