the {adapter} adapter returned {n} of {total} matching rows when asked for the whole result, and residual work will run over that fraction. allowPartialResults is set, so the result is used as-is - it may be wrong. The adapter must follow the engine's own paging to be correct.

Warnings reference › source.pushdown.partial.residual.*

Identifier

source.pushdown.partial.residual.*

Raised by

The grid (core)

Since

1.18.0

What happened

The same shortfall, with filtering or sorting still to do in the browser - so the residual work runs over a fraction of the result and can return the wrong rows. Without allowPartialResults this case throws; with it, the permissive path is taken and the hazard is named once.

The fix

Fix the adapter's paging, hold the data in memory, or keep allowPartialResults knowingly.

Reference

Covered in full at the API reference.