-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[Deprecation API] Adjust details in the SourceFieldMapper deprecation warning #122041
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
[Deprecation API] Adjust details in the SourceFieldMapper deprecation warning #122041
Conversation
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
|
Pinging @elastic/es-data-management (Team:Data Management) |
| public static final String DEPRECATION_WARNING = "Configuring source mode in mappings is deprecated and will be removed " | ||
| public static final String DEPRECATION_WARNING = "Configuring source mode in mappings is deprecated."; | ||
|
|
||
| public static final String DEPRECATION_DETAILS = "Configuring source mode in mappings is deprecated and will be removed " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is used in many places, let's keep this as is and add DEPRECATION_WARNING_TITLE above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! I adjusted it. I did not notice that this is also added a header warning.
| return new DeprecationIssue( | ||
| DeprecationIssue.Level.CRITICAL, | ||
| SourceFieldMapper.DEPRECATION_WARNING_TITLE, | ||
| "https://ela.st/migrate-source-mode", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This for now points at #117172 but now we can update it when we have the guide, without having as much time pressure. Let me know if you do not agree with this approach.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Mary! We need to regenerate changelogs, because the change now shows up as deprecation instead of a breaking change: https://www.elastic.co/guide/en/elasticsearch/reference/master/migrating-9.0.html#deprecations_90_mapping
kkrik-es
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Mary! @martijnvg fyi, no pressure on getting the migration guide in.
martijnvg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💚 Backport successful
You can use sqren/backport to manually backport by running |
… warning (elastic#122041) In this PR we improve the deprecation warning about configuring source in the mapping. - We reduce the size of the warning message so it looks better in kibana. - We keep the original message in the details. - We use an alias help url, so we can associate it with the guide when it's created.
…cation warning (#122041) (#122068) * [Deprecation API] Adjust details in the SourceFieldMapper deprecation warning (#122041) In this PR we improve the deprecation warning about configuring source in the mapping. - We reduce the size of the warning message so it looks better in kibana. - We keep the original message in the details. - We use an alias help url, so we can associate it with the guide when it's created. * Remove bwc code
In this PR we improve the deprecation warning about configuring source in the mapping.