Skip to content

[DOCS][8.x]:Update depreciation notice for index mapping updates privileges #130916

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

Open
wants to merge 1 commit into
base: 8.19
Choose a base branch
from

Conversation

charlotte-hoblik
Copy link
Contributor

This PR updates the depreciation notice for 4 write-related operations on indices: (8.x asciidoc version)

  • create
  • create_doc
  • index
  • write

Based on: elastic/docs-content#1668
9.x Version: #130894

@charlotte-hoblik charlotte-hoblik requested a review from 3kt July 9, 2025 12:33
@charlotte-hoblik charlotte-hoblik self-assigned this Jul 9, 2025
@charlotte-hoblik charlotte-hoblik added >docs General docs changes Team:Docs Meta label for docs team auto-backport Automatically create backport pull requests when merged documentation v8.17.0 v8.18.0 v8.19.0 labels Jul 9, 2025
Copy link
Contributor

github-actions bot commented Jul 9, 2025

Documentation preview:

@charlotte-hoblik charlotte-hoblik changed the title [DOCS]:Update depreciation notice for index mapping updates privileges [DOCS][8.x]:Update depreciation notice for index mapping updates privileges Jul 9, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-docs (Team:Docs)

the {ref}/indices-put-mapping.html[updating mapping API] or by relying on
{ref}/dynamic-mapping.html[dynamic field mapping]. In a future major release,
this privilege will not grant any mapping update permissions.
deprecated:[8.0] Starting from 8.0, this privilege no longer grants the permission
Copy link
Contributor

@3kt 3kt Jul 10, 2025

Choose a reason for hiding this comment

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

Could we call this a change rather than a deprecation? Or maybe a notice? Or something like a partial deprecation? Do we have a clear nomenclature for what such a thing should be called?
My point is that the "deprecated" term tends to push people away from the feature, rather than bringing attention to what exactly changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged >docs General docs changes documentation Team:Docs Meta label for docs team v8.17.0 v8.18.0 v8.19.0 v8.19.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants