Skip to content

Conversation

@martijnvg
Copy link
Member

The check was an identity check between the default constant and
the set indices options. This check is incorrect because in many
cases when IndicesOptions is parsed or randomly generated in tests,
then this check incorrectly returns false when in fact an IndicesOptions
instance is equal to the default constant, but it is just a different
instance/object.

Closes #78035

The check was an identity check between the default constant and
the set indices options. This check is incorrect because in many
cases when `IndicesOptions` is parsed or randomly generated in tests,
then this check incorrectly returns false when in fact an `IndicesOptions`
instance is equal to the default constant, but it is just a different
instance/object.

Closes elastic#78035
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Copy link
Contributor

@danhermann danhermann left a comment

Choose a reason for hiding this comment

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

LGTM

@martijnvg martijnvg merged commit c5a3c3d into elastic:master Sep 22, 2021
martijnvg added a commit to martijnvg/elasticsearch that referenced this pull request Sep 22, 2021
Backporting elastic#78070 to 7.x branch.

The check was an identity check between the default constant and
the set indices options. This check is incorrect because in many
cases when `IndicesOptions` is parsed or randomly generated in tests,
then this check incorrectly returns false when in fact an `IndicesOptions`
instance is equal to the default constant, but it is just a different
instance/object.

Closes elastic#78035
elasticsearchmachine pushed a commit that referenced this pull request Sep 22, 2021
…78165)

Backporting #78070 to 7.x branch.

The check was an identity check between the default constant and
the set indices options. This check is incorrect because in many
cases when `IndicesOptions` is parsed or randomly generated in tests,
then this check incorrectly returns false when in fact an `IndicesOptions`
instance is equal to the default constant, but it is just a different
instance/object.

Closes #78035
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.

[CI] WatcherUtilsTests testSerializeSearchRequest failing

4 participants