Skip to content

Remove unused fields in ActionTransportException #80692

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

Conversation

DaveCTurner
Copy link
Contributor

The fields in ActionTransportException are reflected in the message
generated at construction time, and apart from that they are only used
in tests. This commit removes them, and hence another spot where we were
creating a per-message TransportAddress object.

Relates #80690

The fields in `ActionTransportException` are reflected in the message
generated at construction time, and apart from that they are only used
in tests. This commit removes them, and hence another spot where we were
creating a per-message `TransportAddress` object.

Relates elastic#80690
@DaveCTurner DaveCTurner added :Distributed Coordination/Network Http and internode communication implementations >refactoring v8.1.0 labels Nov 14, 2021
@elasticmachine elasticmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Nov 14, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

Copy link
Member

@tlrx tlrx left a comment

Choose a reason for hiding this comment

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

LGTM

@DaveCTurner DaveCTurner merged commit 37f7adc into elastic:master Nov 15, 2021
@DaveCTurner DaveCTurner deleted the 2021-11-14-unused-fields-in-ActionTransportException branch November 15, 2021 08:34
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Nov 23, 2021
Today we use `writeBoolean(false);` to write to a `StreamOutput` an
optional value that is always missing. It's something of an
implementation detail that a missing value is indicated by a `false`
(i.e. a zero byte) so this commit wraps these calls in methods that
better indicate the intent.

Relates elastic#80944
Relates elastic#80692
DaveCTurner added a commit that referenced this pull request Nov 23, 2021
Today we use `writeBoolean(false);` to write to a `StreamOutput` an
optional value that is always missing. It's something of an
implementation detail that a missing value is indicated by a `false`
(i.e. a zero byte) so this commit wraps these calls in methods that
better indicate the intent.

Relates #80944
Relates #80692
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Network Http and internode communication implementations >refactoring Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. v8.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants