Move getType to Aggregation interface #24822
Merged
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
Given that both InternalAggregation and ParsedAggregation have this method, it makes sense to move it to the interface they both implement.
javanna
force-pushed
the
enhancement/move_get_type
branch
from
50e5313 to
78a38fe
Compare
tlrx
approved these changes
May 22, 2017
javanna
added a commit
to javanna/elasticsearch
that referenced
this pull request
May 23, 2017
Given that both InternalAggregation and ParsedAggregation have this method, it makes sense to move it to the interface they both implement.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Given that both InternalAggregation and ParsedAggregation have this method, it makes sense to move it to the interface they both implement.