Similar in spirit to #36015, but with the goal of removing unecessary metric/bucket agg IT. Unlike the pipeline aggs, it should be very straightforward to replace, and I think we can probably remove most of the existing ESIntegTestCase tests
Some of these aggs do already have an AggregatorTestCase, so we should evaluate if the IT has something the unit test does not, migrate if possible and decide if the IT is useful otherwise.
A quick skim shows a lot of the IT deal with scripts, unmapped fields, formatting, etc. It's not clear to me right now if we can test some of these (notably scripts) outside of an IT. So that might be a reason to keep the IT around.
Metrics
Bucket
Similar in spirit to #36015, but with the goal of removing unecessary metric/bucket agg IT. Unlike the pipeline aggs, it should be very straightforward to replace, and I think we can probably remove most of the existing
ESIntegTestCasetestsSome of these aggs do already have an
AggregatorTestCase, so we should evaluate if the IT has something the unit test does not, migrate if possible and decide if the IT is useful otherwise.A quick skim shows a lot of the IT deal with scripts, unmapped fields, formatting, etc. It's not clear to me right now if we can test some of these (notably scripts) outside of an IT. So that might be a reason to keep the IT around.
Metrics
Bucket