provide an option to skip entire row group in case corrupted bytes occur

In case of hardware failure (disk, memory, etc), there might be corrupted bytes. That will result in ArrayIndexOutOfBoundException or/and data garbled.

Currently, jobs reading those Parquet files will fail unless the corrupted files are deleted/moved.

It would be better if Parquet provide an option to skip entire row group (and report how many rows being affected) in case of corrupted bytes.

related issue: PARQUET-147

**Reporter**: [Tongjie Chen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tongjie) / @tongjiechen

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

No se nombran archivos, pruebas ni puntos de entrada. Empieza rastreando la lectura de grupos de filas de Parquet Java y cómo gestiona los bytes corruptos; el trabajo estará terminado cuando un comportamiento opt-in pueda omitir un grupo de filas afectado e informar de cuántas filas se vieron afectadas.

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