gcdev373

I think a feature like this would be very handy, as it would allow Stroom to be usefully deployed in an XML free mode. JSON in, JSON transformation language, JSON...

See [stroom-data-generator](https://github.com/gchq/stroom-data-generator). Contains elements of above, including templates for generating data. There are scripts that automatically create and send data into Stroom where they are processed by a pipeline designed...

Making an aggregate of values feels like a very different operation to making an aggregate of distinct values.

@burnalting that sounds good to me.

Update: Some background about the requirement is [here](https://github.com/gchq/stroom-docs/blob/master/HOWTOs/General/RawSourceTracking.md) Testing with Stroom `v7.0-beta.105` suggest this functionality is now working for streams derived from text using a pipeline with a data splitter...

Possible overlap with [this issue](https://github.com/gchq/stroom/issues/4338)

Possible overlap with [this issue](https://github.com/gchq/stroom/issues/4109)

There might be a bit of a hole when a feed status changes to a `REJECT` or `DROP` status from `RECEIVE`. Ideally, any events already received at Proxy could still...