This Math.min calculation seems over-general. At most it seems that what is needed is an assert that either the min/max column is among the equality filtered columns OR there are strictly more indexedColIdx entries than filters. It would be trivial to assert (in all cases) that there are never more filters than indexedColIdx entries.
The presence of the min/max column in the filters could be detected and cached in a boolean during the initial filter iteraton above.
If it wasn't found, indexedColIdx.get(filterSize+1) should match the min/max col to allow this index.