Using a pattern for providing $maxCount and $maxAge sounds great.
I’d personally like to be able to set these for **projection-emitted partitioned streams. **I guess my pattern to match projection output would need to include a (partial) test for the partitionId so that it didn’t apply to the other partition-related streams, including the non-partitioned result…
SHOULD NOT MATCH
Furthermore, this has an advantage over writing to the metadata stream (e.g $$$projections-materialise_cart-cart1234-result) in that it won’t be wiped out by a projection reset.
(Rightly or otherwise, I am using projections to materialise my aggregates’ current states and generally only need the latest of each, hence wanting to set $maxCount=1 and let the old versions be scavenged)
From what I’ve gleaned from previous group threads, this would make a number of people very happy.
@Greg - your “StreamOfStreamLinks” post sounds very interesting, but I am struggling to fit it to this context. Did you post it in the right topic??