Skip to content

Conversation

pquentin
Copy link
Member

@pquentin pquentin commented Mar 27, 2025

Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
async_search.submit 🟢 7/7 7/7
fleet.msearch Missing test Missing test
fleet.search Missing test Missing test
msearch 🟢 17/17 16/16
open_point_in_time 🟢 7/7 7/7
search 🔴 2304/2389 2372/2373

You can validate these APIs yourself by using the make validate target.

Comment on lines 110 to 111
max_concurrent_shard_requests?: long
max_concurrent_shard_requests?: integer
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines 105 to 106
max_concurrent_searches?: long
max_concurrent_searches?: integer
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

include_named_queries_score?: boolean
/**
* Maximum number of concurrent searches the multi search API can execute.
* Defaults to `max(1, (# of data nodes * min(search thread pool size, 10)))`.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't use @server_default as it expects a number

Copy link
Member

@flobernd flobernd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

While long -> int is technically a breaking change, nobody would notice in the end (if somebody is already passing values > MAXINT to that field, this means it probably never worked anyways).

@pquentin
Copy link
Member Author

pquentin commented Mar 28, 2025

After discussing this offline, I extracted the breaking changes to #4171. Please take another look.

(I did not intend to close this, sorry.)

@pquentin pquentin closed this Mar 28, 2025
@pquentin pquentin reopened this Mar 28, 2025
Copy link
Contributor

Following you can find the validation results for the API you have changed.

API Status Request Response
open_point_in_time 🟢 7/7 7/7

You can validate this API yourself by using the make validate target.

1 similar comment
Copy link
Contributor

Following you can find the validation results for the API you have changed.

API Status Request Response
open_point_in_time 🟢 7/7 7/7

You can validate this API yourself by using the make validate target.

@pquentin pquentin merged commit 6138673 into main Mar 28, 2025
20 checks passed
@pquentin pquentin deleted the pit-max-concurrent-shard-requests branch March 28, 2025 16:16
github-actions bot pushed a commit that referenced this pull request Mar 28, 2025
github-actions bot pushed a commit that referenced this pull request Mar 28, 2025
github-actions bot pushed a commit that referenced this pull request Mar 28, 2025
pquentin added a commit that referenced this pull request Mar 28, 2025
(cherry picked from commit 6138673)

Co-authored-by: Quentin Pradet <quentin.pradet@elastic.co>
pquentin added a commit that referenced this pull request Mar 28, 2025
(cherry picked from commit 6138673)

Co-authored-by: Quentin Pradet <quentin.pradet@elastic.co>
pquentin added a commit that referenced this pull request Mar 28, 2025
(cherry picked from commit 6138673)

Co-authored-by: Quentin Pradet <quentin.pradet@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants