[Improvement]: Filter out the CodecPool log in the optimizer log
klion26 opened this issue · comments
Search before asking
- I have searched in the issues and found no similar issues.
What would you like to be improved?
Currently, there will be a lot of logs for compressor/decompressor such as below.
How should we improve?
We can filter out these logs by modifying the log4j property
Seems currently only the log4j property of local optimizer was managed by Amoro, so we only need to change the log4j property for local optimizer, and let the flink/spark to user(maybe we can add some docs)
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Subtasks
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
@zhoujinsong @baiyangtx what do you think about this feature, if this is valid I can contribute it later.
+1