-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: do not print error log on PlanQuery error #4322
Conversation
WalkthroughThe recent adjustments to the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- src/common/error/src/status_code.rs (2 hunks)
Additional comments not posted (2)
src/common/error/src/status_code.rs (2)
173-173
: Verify ifPlanQuery
errors should not be logged.The
StatusCode::PlanQuery
variant has been moved to a match arm that returnsfalse
in theshould_log_error
method. Ensure that allPlanQuery
errors are user input errors and do not need error logging to avoid missing critical issues.
173-173
: Verify ifPlanQuery
errors should be retryable.The
StatusCode::PlanQuery
variant has been moved to a match arm that returnstrue
in theis_retryable
method. Ensure thatPlanQuery
errors are indeed retryable and this change aligns with the intended error handling strategy.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4322 +/- ##
==========================================
- Coverage 85.15% 84.88% -0.28%
==========================================
Files 1061 1061
Lines 188255 188247 -8
==========================================
- Hits 160313 159796 -517
- Misses 27942 28451 +509 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@waynexia PTAL |
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
We get a lot of error logs for "table not found" query on the production. Here I moved PlanQuery code to non error log section to avoid this. I also want to confirm if
PlanQuery
is all caused by user input errors, which is safe to do so.Checklist
Summary by CodeRabbit
StatusCode::PlanQuery
to improve error management.