tustvold opened a new issue #1495: URL: https://github.com/apache/arrow-rs/issues/1495
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** Currently `arrow` and `parquet` do not have any log instrumentation, and I have frequently found myself adding logging to track down a problem, only to then have to remove this logging for the final PR. **Describe the solution you'd like** This [log](https://docs.rs/log/latest/log/) crate is well-supported within the Rust ecosystem and allows filtering out callsites at both runtime and compile time. It is also used upstream by [DataFusion](https://github.com/apache/arrow-datafusion/blob/master/datafusion/Cargo.toml#L70). This would allow adding instrumentation to the code that can be enabled for debugging a problem, and then disabled when no longer desired. **Describe alternatives you've considered** There is also the [tracing](https://docs.rs/tracing/latest/tracing/) ecosystem, but this is likely significant overkill given neither crate makes significant use of tokio. Fortunately [tracing-log](https://docs.rs/tracing-log/latest/tracing_log/) provides an adapter should a downstream wish to use tokio-tracing, whilst allowing `arrow`, etc... to use the significantly simpler `log` ecosystem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
