Skip to content

Dry up AcknowledgedResponse Handling (#63335) #64130

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

Merged
merged 1 commit into from
Oct 26, 2020

Conversation

original-brownbear
Copy link
Member

  1. AcknowledgedResponse should really be two singletons to make things clearer and save some objects and code size.
  2. We were duplicating reading this type over and over in a bunch of transport master node actions so I dried that up

backport of #63335

1. `AcknowledgedResponse` should really be two singletons to make things clearer and save some objects and code size.
2. We were duplicating reading this type over and over  in a bunch of transport master node actions so I dried that up
@original-brownbear original-brownbear added :Core/Infra/Core Core issues without another label backport labels Oct 26, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Core)

@elasticmachine elasticmachine added the Team:Core/Infra Meta label for core/infra team label Oct 26, 2020
@original-brownbear original-brownbear merged commit fdc1500 into elastic:7.x Oct 26, 2020
@original-brownbear original-brownbear deleted the 63335-7.x branch October 26, 2020 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Core/Infra/Core Core issues without another label Team:Core/Infra Meta label for core/infra team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants