Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.8.1
-
None
-
None
Description
The current Log class is intended to allow swapping out logger back-ends, but SLF4J already does this. It also doesn't expose as nice of an API as SLF4J, which can handle formatting to avoid the cost of building log messages that won't be used. I think we should deprecate the org.apache.parquet.Log class and move to using SLF4J directly, instead of wrapping SLF4J (PARQUET-305).
This will require deprecating the current Log class and replacing the current uses of it with SLF4J.
Attachments
Issue Links
- is blocked by
-
PARQUET-528 Fix flush() for RecordConsumer and implementations
- Resolved
-
PARQUET-529 Avoid evoking job.toString() in ParquetLoader
- Resolved
- is related to
-
PARQUET-369 Shading SLF4J prevents SLF4J locating org.slf4j.impl.StaticLoggerBinder
- Resolved
-
PARQUET-305 Logger instantiated for package org.apache.parquet may be GC-ed
- Resolved
- is required by
-
PARQUET-408 Shutdown hook in parquet-avro library corrupts data and disables logging
- Resolved