implicitly defining DEBUG mode in MessageColumnIO causes 80% performance overhead

**parquet-column** jar leverages slf4j and log4j as default logger, neglecting to define a log4j configuration, defaults to **DEBUG** log level.

 
```java

public class MessageColumnIO extends GroupColumnIO {
private static final Logger LOG = LoggerFactory.getLogger(MessageColumnIO.class);

private static final boolean DEBUG = LOG.isDebugEnabled(); // <------
}
```
 

this "magic behavior" defaults parquet library to be in DEBUG mode, without any notification or warnings. Unfortunately, the **RecordConsumerLoggingWrapper** implementation generates 5x performance overhead in comparison to the **MessageColumnIORecordConsumer** implementation, causing a massive hit in performance and wasteful server utilization.

IMHO there are two things that could prevent such issue:
- printing a message to STDOUT notifying about DEBUG mode being set to active.
- defaulting to **MessageColumnIORecordConsumer** implementation, and waiting for explicit configuration to define DEBUG mode, and use **RecordConsumerLoggingWrapper**.

 

In the past 2 years, this issue probably cost my company 50,000$ in excessive cloud costs!

**Reporter**: [Elad Yosifon](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elad_yosifon)

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

Beginne mit MessageColumnIO und untersuche, wie LOG.isDebugEnabled() zwischen MessageColumnIORecordConsumer und RecordConsumerLoggingWrapper auswählt. Verfolge die Logger-Konfiguration sowie vorhandene Performancetests oder Benchmarks. Als abgeschlossen gilt die Aufgabe, wenn DEBUG nicht implizit aktiviert ist und der normale Consumer den gemeldeten Overhead vermeidet, sofern dies nicht ausdrücklich konfiguriert wurde.

Vom Indexierungsmodell aus dem Issue-Text verfasst.