Skip to content

Conversation

@jakelandis
Copy link
Contributor

This commit adds support to check for a value of 'fix' for the index setting
index.shard.check_on_startup for the deprecation info API. This is no longer
a valid value for this setting.

relates #36024
relates #33194

This commit adds support to check for a value of 'fix' for the index setting
`index.shard.check_on_startup` for the deprecation info API. This is no longer
a valid value for this setting.

relates elastic#36024
relates elastic#33194
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

Copy link
Contributor

@gwbrown gwbrown left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks!

@jakelandis
Copy link
Contributor Author

@gwbrown thanks for the review.

jenkins test this please

@jakelandis
Copy link
Contributor Author

@gwbrown - could i get you take one more look ? I updated the details message to be more consistent with #36454

The final output is:

  "index_settings" : {
    "test" : [
      {
        "level" : "warning",
        "message" : "The value [fix] for setting [index.shard.check_on_startup] is no longer valid",
        "url" : "https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-7.0.html#_literal_fix_literal_value_for_literal_index_shard_check_on_startup_literal_is_removed",
        "details" : "The index [test] has the setting [index.shard.check_on_startup] set to value [fix], but [fix] is no longer a valid value. Valid values are true, false, and checksum"
      }
    ]
  }

@jakelandis jakelandis merged commit e171bd9 into elastic:6.x Dec 13, 2018
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