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

Timeout Not Triggering as Expected in search Method #654

Open
MILEWID opened this issue Oct 5, 2023 · 1 comment
Open

Timeout Not Triggering as Expected in search Method #654

MILEWID opened this issue Oct 5, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@MILEWID
Copy link

MILEWID commented Oct 5, 2023

What is the bug?

The timeout feature in the search method is not working as expected.

How can one reproduce the bug?

When attempting to create a timeout in my method using values like "10m" or "10ms," I do not receive a timeout error. Here's the code snippet:

SearchRequest searchRequest = new SearchRequest.Builder()
                .timeout("10m")
                .index(index)
                .query(q -> q.bool(b -> b
                        .must(byTyp)
                        .must(byCis)
                        .must(bySta)))
                .build();
return openSearchClient.search(searchRequest, AccountBean.class);

What is the expected behavior?

The expected behavior is to receive a timeout exception when the specified timeout duration is reached.

@MILEWID MILEWID added bug Something isn't working untriaged labels Oct 5, 2023
@MILEWID MILEWID changed the title timeout in method search , don't working Timeout Not Triggering as Expected in search Method Oct 5, 2023
@dblock
Copy link
Member

dblock commented Oct 6, 2023

Does your search request complete? What do you receive? Does changing it to t->t.time("10m") change anything?

@dblock dblock removed the untriaged label Dec 4, 2023
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

No branches or pull requests

2 participants