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.
Adds event aggregation as specified in the Preliminary Design Details document.
Adds aggregation for the following events:
Configuration
Each event that can be aggregated has a configuration setting to enable or disable aggregation, for eample
bsm.message.count.progression.aggregateEvents
. Aggregation is enabled by default. When aggregation is enabled, only aggregated events are written to Kafka topics.Key config settings:
aggregation.interval
: The aggregation interval, default 60aggregation.intervalUnits
: Default SECONDSImplementation Details
The key classes that implement the aggregation algorithm are:
All the aggregation topologies inherit from
BaseAggregationTopology
The aggregated events all inherit from the EventAggregation class.
Each event that produced notifications also has a corresponding NotificationAggregation added.
See also the related PR for ode-utils that adds new topics for the aggregated events and notifications:
usdot-jpo-ode/jpo-utils#15
Testing
Adds unit tests for each of the new aggregation topologies.
Ran the following integration tests scripts: