Skip to content

Fix rest validation of search request using a PIT #71688

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

Merged
merged 4 commits into from
Apr 20, 2021

Conversation

jimczi
Copy link
Contributor

@jimczi jimczi commented Apr 14, 2021

The rest validation of the search request ensures that the indices options
are set to the default value. However, the comparison is too strict and should
use equals since we create a new IndicesOption object when parsing from http or transport.

Closes #69974

The rest validation of the search request ensures that the indices options
are set to the default value. However, the comparison is too strict and should
use equals since we create a new IndicesOption object when parsing from http or transport.

Closes elastic#69974
@jimczi jimczi added >bug :Search/Search Search-related issues that do not fall into other categories v7.13.0 v7.12.1 labels Apr 14, 2021
@elasticmachine elasticmachine added the Team:Search Meta label for search team label Apr 14, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (Team:Search)

Copy link
Member

@dnhatn dnhatn left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you for fixing this quickly.

@gwbrown gwbrown added v7.12.2 and removed v7.12.1 labels Apr 14, 2021
@jimczi jimczi merged commit a039ef2 into elastic:master Apr 20, 2021
@jimczi jimczi deleted the indices_option_equals branch April 20, 2021 07:04
jimczi added a commit that referenced this pull request Apr 20, 2021
The rest validation of the search request ensures that the indices options
are set to the default value. However, the comparison is too strict and should
use equals since we create a new IndicesOption object when parsing from http or transport.

Closes #69974
jimczi added a commit that referenced this pull request Apr 20, 2021
The rest validation of the search request ensures that the indices options
are set to the default value. However, the comparison is too strict and should
use equals since we create a new IndicesOption object when parsing from http or transport.

Closes #69974
jimczi added a commit to jimczi/elasticsearch that referenced this pull request Apr 21, 2021
Adjust this random test now that default indices options are not
exposed in rest.

Relates elastic#71688
Closes elastic#71916
jimczi added a commit that referenced this pull request Apr 22, 2021
Adjust this random test now that default indices options are not
exposed in rest.

Relates #71688
Closes #71916
jimczi added a commit that referenced this pull request Apr 22, 2021
Adjust this random test now that default indices options are not
exposed in rest.

Relates #71688
Closes #71916
jimczi added a commit that referenced this pull request Apr 28, 2021
Adjust this random test now that default indices options are not
exposed in rest.

Relates #71688
Closes #71916
jimczi added a commit that referenced this pull request Apr 28, 2021
Adjust this random test now that default indices options are not
exposed in rest.

Relates #71688
Closes #71916
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Search/Search Search-related issues that do not fall into other categories Team:Search Meta label for search team v7.12.2 v7.13.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RestHighLevelClient: indicesOptions cannot be used with point in time, but is not nullable in SearchRequest
4 participants