-
Notifications
You must be signed in to change notification settings - Fork 29k
[SQL] logWarning should be logInfo in getResultSetSchema #1939
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
Conversation
|
Can one of the admins verify this patch? |
|
ok to test |
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.
Or maybe even logDebug? This seems pretty noisy.
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.
i think logInfo is ok, it's acceptable of each sql print once
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.
Yeah either way. I just think I wrote this line initially and it was for debugging :)
|
QA tests have started for PR 1939. This patch merges cleanly. |
|
QA results for PR 1939: |
|
@marmbrus, the test error in pyspark again~ |
Author: wangfei <[email protected]> Closes #1939 from scwf/patch-5 and squashes the following commits: f952d10 [wangfei] [SQL] logWarning should be logInfo in getResultSetSchema (cherry picked from commit 507a1b5) Signed-off-by: Michael Armbrust <[email protected]>
|
Thanks, I've merged this into master and 1.1. |
Author: wangfei <[email protected]> Closes apache#1939 from scwf/patch-5 and squashes the following commits: f952d10 [wangfei] [SQL] logWarning should be logInfo in getResultSetSchema
No description provided.