Remove types exists action #43344
Merged
Remove types exists action #43344
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
client, as RestGetMappingAction has its own logic that ties into the unified HEAD requests handling. Now that tranport client is removed, we can remove also TransportTypesExistsAction as well as its corresponding request, request builder, response, and action.
javanna
added
>enhancement
:Core/Infra/Core
Collaborator
|
Pinging @elastic/es-core-infra |
Member
Author
|
run elasticsearch-ci/default-distro |
Member
Author
|
run elasticsearch-ci/docbldesx |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The types exists action was kept around only to not break transport
client, as RestGetMappingAction has its own logic that ties into the
unified HEAD requests handling.
Now that transport client is removed, we can remove also
TransportTypesExistsAction as well as its corresponding request,
request builder, response, and action.