Skip to content

Update PostAggregator to be backwards compat#12138

Merged
clintropolis merged 1 commit intoapache:masterfrom
imply-cheddar:post-agg-compact-22-1
Jan 11, 2022
Merged

Update PostAggregator to be backwards compat#12138
clintropolis merged 1 commit intoapache:masterfrom
imply-cheddar:post-agg-compact-22-1

Conversation

@imply-cheddar
Copy link
Copy Markdown
Contributor

@imply-cheddar imply-cheddar commented Jan 11, 2022

This change mimics what was done in PR #11917 to
fix the incompatibilities produced by #11713. #11917
fixed it with AggregatorFactory by creating default
methods to allow for extensions built against old
jars to still work. This does the same for PostAggregator

This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

This change mimics what was done in PR 11917 to
fix the incompatibilities produced by 11713. 11917
fixed it with AggregatorFactory by creating default
methods to allow for extensions built against old
jars to still work.  This does the same for PostAggregator
@clintropolis
Copy link
Copy Markdown
Member

ignoring coverage check since it is a backwards compat thing

@clintropolis clintropolis merged commit eb0bae4 into apache:master Jan 11, 2022
@abhishekagarwal87 abhishekagarwal87 added this to the 0.23.0 milestone May 11, 2022
sachinsagare pushed a commit to pinterest/druid that referenced this pull request Oct 28, 2022
This change mimics what was done in PR apache#11917 to
fix the incompatibilities produced by apache#11713. apache#11917
fixed it with AggregatorFactory by creating default
methods to allow for extensions built against old
jars to still work.  This does the same for PostAggregator

(cherry picked from commit eb0bae4)
sachinsagare pushed a commit to sachinsagare/druid that referenced this pull request Nov 2, 2022
This change mimics what was done in PR apache#11917 to
fix the incompatibilities produced by apache#11713. apache#11917
fixed it with AggregatorFactory by creating default
methods to allow for extensions built against old
jars to still work.  This does the same for PostAggregator

(cherry picked from commit eb0bae4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants