InternalParquetRecordReader Logging is Too Verbose

A low-level library like Parquet should be pretty quiet. It should just do its work and keep quiet. Most issues should be addressed by throwing Exceptions, and the occasional warning message otherwise it will clutter the logging for the top-level application. If debugging is required, administrator can enable it for the specific workload.

**Warning:** This is my opinion. No stats to back it up.

**Reporter**: [David Mollitor](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=belugabehr) / @belugabehr
**Assignee**: [David Mollitor](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=belugabehr) / @belugabehr
#### Related issues:
- [Lower Logging Level in ParquetOutputFormat](https://github.com/apache/parquet-java/issues/2436) (is related to)
#### PRs and other links:
- [GitHub Pull Request #742](https://github.com/apache/parquet-mr/pull/742)

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

Inizia leggendo i percorsi di logging di InternalParquetRecordReader e il Pull Request #742 collegato. Confronta i messaggi e i livelli attuali con l’aspettativa dell’issue che il lavoro di routine rimanga silenzioso, mentre le eccezioni e gli avvisi occasionali rimangano; il lavoro è completato quando il comportamento del logging corrisponde a tale ambito.

Scritto dal modello di indicizzazione a partire dal testo della issue.