Record filtering in the filter2 API could possibly short circuit

Record level filtering in the filter2 api still requires visiting every value of the record. We may be able to short circuit as soon as the filter predicate reaches a known state.

Another approach would be to figure out how to get essentially random access to the values referenced by the predicate and check them first. This could be tricky because it would require re-structuring the assembly algorithm.

**Reporter**: [Alex Levenson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alexlevenson) / @isnotinvain

_{**Note**: *This issue was originally created as [PARQUET-37](https://issues.apache.org/jira/browse/PARQUET-37). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*}

Empieza rastreando el filtrado a nivel de registro de la API filter2 y el algoritmo de ensamblado, ya que el issue no indica archivos ni tests. Determina si la evaluación del predicado puede detenerse una vez conocido su estado, o si es necesario acceder antes a los valores referenciados por el predicado; se considera completado cuando se conserva el comportamiento del filtrado y se evitan visitas innecesarias a valores.

Escrito por el modelo de indexación a partir del texto del issue.