Improve documentation for 'send-partial-result-on-expiry' [INT-2012]

[spring-operator]

Oleg Zhurakousky opened INT-2012 and commented

I know we have plenty of cases where certain attributes are mutually-exclusive, but we always make an attempt to either throw an exception or warn the user. In the case of the aggregator, not only we have mutually exclusive attributes but we currently have mutually exclusive combinations which involve several attributes and beans configured outside.
For example:

send-partial-result-on-expiry="true" - is meaningless unless MessageGroupStoreReaper bean is configured on MessageGroupStore. This means that both 'send-partial-result-on-expiry' and 'message-store' must be explicitly configured on the aggregator. It also means that 'send-partial-result-on-expiry' must be 'true' otherwise MessageGroupStoreReaper is meaningless since it has no affect on the behavior of the aggregator.

---

Affects: 2.0.5

[spring-operator]

Oleg Zhurakousky commented

Actually looking further send-partial-result-on-expiry is not all that meaningless without the reaper since MessageGroups could be expired via ControlBus call (e.g., messageGroupStore.expireMessageGroups(..) )

So i think this is really an issue of WARNING/INFORMING users that we could not find a reaper if this attribute is set to true and letting them know that unless they execute the manual call this attribute has no value/behavior

olegz@748db57