[
https://issues.apache.org/jira/browse/HIVE-19302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615607#comment-16615607
]
Hive QA commented on HIVE-19302:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12939650/HIVE-19302.1.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 14940 tests
executed
*Failed tests:*
{noformat}
org.apache.hive.jdbc.TestSSL.testMetastoreConnectionWrongCertCN (batchId=250)
org.apache.hive.jdbc.TestSSL.testSSLConnectionWithProperty (batchId=250)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/13797/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/13797/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-13797/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12939650 - PreCommit-HIVE-Build
> Logging Too Verbose For TableNotFound
> -------------------------------------
>
> Key: HIVE-19302
> URL: https://issues.apache.org/jira/browse/HIVE-19302
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2
> Affects Versions: 2.2.0, 3.0.0
> Reporter: BELUGA BEHR
> Assignee: Alice Fan
> Priority: Minor
> Attachments: HIVE-19302.1.patch, table_not_found_cdh6.txt
>
>
> There is way too much logging when a user submits a query against a table
> which does not exist. In an ad-hoc setting, it is quite normal that a user
> fat-fingers a table name. Yet, from the perspective of the Hive
> administrator, there was perhaps a major issue based on the volume and
> severity of logging. Please change the logging to INFO level, and do not
> present a stack trace, for such a trivial error.
>
> See the attached file for a sample of what logging a single "table not found"
> query generates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
