Unclear The finding does not say what CCR is or what effect changing the flush policy has in practice.
What
When the CCR client receives a response to its heartbeat, it now checks for an event_flush_policy field in the response data and, if present, calls a new takeUpFlushPolicy method to adopt it. This happens alongside the existing handling for refreshed authentication in heartbeat responses.
Why
This lets the server adjust how the client flushes events at runtime by pushing a policy through the regular heartbeat, rather than that behavior being fixed on the client side.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what CCR is or what effect changing the flush policy has in practice.