[enhancement] Logging Optimization
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 396
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.
### Motivation
Two main optimizations were implemented:
1) No log level check was performed when invoking LOG.warn(xx);
2) Log statements did not use placeholders;
### Solution
1) add DEBUG-level log checks before logging operations;
2) log statements use parameterized placeholder
### Anything else?
NONE
### Are you willing to submit a PR?
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named in the issue. Start by locating the affected LOG.warn and other logging calls, then review how DEBUG-level checks and parameterized placeholders should apply. Done means the relevant logging operations use level checks and placeholders without changing their messages or behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100