Is Payload size based filtering also a requirement?

Even if its not for consistency, how about include both?

I didn't hear any asks for payload size but yes let's add both

Hi Kiran - I discussed it with Justine on Teams, the requirement here is mainly around monitoring for queries with high RU charges, but I suppose that anything that closes the gap w.r.t. Java SDK helps. (https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/CosmosDiagnosticsThresholds.java)

For a moment my heart skipped a beat thinking that #1763 was being addressed (I'd still love to be able to define a size or RU budget for queries in general, and ChangeFeedl requests in particular).
Having to pick between ultra conservative 100 docs or setting a huge limit and getting lumpy RU costs when the documents are not of uniform size is very unfortunate in terms of delivering consistent throughput without random large requests causing rate limiting when that's absolutely not the intent of the system.