[jira] [Commented] (HIVE-10119) Allow Log verbosity to be set in hiveserver2 session

2015-06-02 Thread Lefty Leverenz (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570071#comment-14570071
 ] 

Lefty Leverenz commented on HIVE-10119:
---

Doc note:  [~hsubramaniyan] documented *hive.server2.logging.operation.level* 
in Configuration Properties, and I added small sections to Getting Started, 
Setting Up HiveServer2, and HiveServer2 Clients.

* [Getting Started -- HiveServer2 Logs | 
https://cwiki.apache.org/confluence/display/Hive/GettingStarted#GettingStarted-HiveServer2Logs]
* [Setting Up HiveServer2 -- Logging Configuration | 
https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2#SettingUpHiveServer2-LoggingConfiguration]
* [HiveServer2 Clients -- HiveServer2 Logging | 
https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-HiveServer2Logging]

Please review and correct or improve as needed.  (The release note could also 
be updated.)  Optimistically removing the TODOC1.2 label.

> Allow Log verbosity to be set in hiveserver2 session
> 
>
> Key: HIVE-10119
> URL: https://issues.apache.org/jira/browse/HIVE-10119
> Project: Hive
>  Issue Type: Improvement
>  Components: HiveServer2
>Reporter: Hari Sankar Sivarama Subramaniyan
>Assignee: Hari Sankar Sivarama Subramaniyan
> Fix For: 1.2.0
>
> Attachments: HIVE-10119.1.patch, HIVE-10119.2.patch, 
> HIVE-10119.3.patch, HIVE-10119.4.patch
>
>
> We need to be able to set logging per HS2 session.
> The client often uses the map-reduce completion matrix (Execution) that shows 
> up in Beeline to debug performance. User might not want the verbose log view 
> all the time since it obfuscates the Execution information. Hence the client 
> should be able to change the verbosity level.
> Also, there are 2 levels of verbosity at HS2 logging and not 3. The users 
> might want Execution + Performance counters only - so that level needs to be 
> added.
> So for logs,  the user should be able to set 3 levels of verbosity in the 
> session, that will override the default verbosity specified in the 
> hive-site.xml file.
> 0. None - IGNORE
> 1. Execution - Just shows the map-reduce tasks completing 
> 2. Performance - Execution + Performance counters dumped at the end
> 3. Verbose - All logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-10119) Allow Log verbosity to be set in hiveserver2 session

2015-04-08 Thread Hari Sankar Sivarama Subramaniyan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485587#comment-14485587
 ] 

Hari Sankar Sivarama Subramaniyan commented on HIVE-10119:
--

The test failures look unrelated to my change.
Thanks
Hari

> Allow Log verbosity to be set in hiveserver2 session
> 
>
> Key: HIVE-10119
> URL: https://issues.apache.org/jira/browse/HIVE-10119
> Project: Hive
>  Issue Type: Improvement
>  Components: HiveServer2
>Reporter: Hari Sankar Sivarama Subramaniyan
>Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-10119.1.patch, HIVE-10119.2.patch, 
> HIVE-10119.3.patch, HIVE-10119.4.patch
>
>
> We need to be able to set logging per HS2 session.
> The client often uses the map-reduce completion matrix (Execution) that shows 
> up in Beeline to debug performance. User might not want the verbose log view 
> all the time since it obfuscates the Execution information. Hence the client 
> should be able to change the verbosity level.
> Also, there are 2 levels of verbosity at HS2 logging and not 3. The users 
> might want Execution + Performance counters only - so that level needs to be 
> added.
> So for logs,  the user should be able to set 3 levels of verbosity in the 
> session, that will override the default verbosity specified in the 
> hive-site.xml file.
> 0. None - IGNORE
> 1. Execution - Just shows the map-reduce tasks completing 
> 2. Performance - Execution + Performance counters dumped at the end
> 3. Verbose - All logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-10119) Allow Log verbosity to be set in hiveserver2 session

2015-04-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484972#comment-14484972
 ] 

Hive QA commented on HIVE-10119:




{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12723736/HIVE-10119.4.patch

{color:red}ERROR:{color} -1 due to 13 failed/errored test(s), 8667 tests 
executed
*Failed tests:*
{noformat}
TestMinimrCliDriver-bucketmapjoin6.q-constprog_partitioner.q-infer_bucket_sort_dyn_part.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-external_table_with_space_in_location_path.q-infer_bucket_sort_merge.q-auto_sortmerge_join_16.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-groupby2.q-import_exported_table.q-bucketizedhiveinputformat.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-index_bitmap3.q-stats_counter_partitioned.q-temp_table_external.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-infer_bucket_sort_map_operators.q-join1.q-bucketmapjoin7.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-infer_bucket_sort_num_buckets.q-disable_merge_for_bucketing.q-uber_reduce.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-infer_bucket_sort_reducers_power_two.q-scriptfile1.q-scriptfile1_win.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-leftsemijoin_mr.q-load_hdfs_file_with_space_in_the_name.q-root_dir_external_table.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-list_bucket_dml_10.q-bucket_num_reducers.q-bucket6.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-load_fs2.q-file_with_header_footer.q-ql_rewrite_gbtoidx_cbo_1.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-parallel_orderby.q-reduce_deduplicate.q-ql_rewrite_gbtoidx_cbo_2.q-and-1-more
 - did not produce a TEST-*.xml file
TestMinimrCliDriver-ql_rewrite_gbtoidx.q-smb_mapjoin_8.q - did not produce a 
TEST-*.xml file
TestMinimrCliDriver-schemeAuthority2.q-bucket4.q-input16_cc.q-and-1-more - did 
not produce a TEST-*.xml file
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3323/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3323/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-3323/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 13 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12723736 - PreCommit-HIVE-TRUNK-Build

> Allow Log verbosity to be set in hiveserver2 session
> 
>
> Key: HIVE-10119
> URL: https://issues.apache.org/jira/browse/HIVE-10119
> Project: Hive
>  Issue Type: Improvement
>  Components: HiveServer2
>Reporter: Hari Sankar Sivarama Subramaniyan
>Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-10119.1.patch, HIVE-10119.2.patch, 
> HIVE-10119.3.patch, HIVE-10119.4.patch
>
>
> We need to be able to set logging per HS2 session.
> The client often uses the map-reduce completion matrix (Execution) that shows 
> up in Beeline to debug performance. User might not want the verbose log view 
> all the time since it obfuscates the Execution information. Hence the client 
> should be able to change the verbosity level.
> Also, there are 2 levels of verbosity at HS2 logging and not 3. The users 
> might want Execution + Performance counters only - so that level needs to be 
> added.
> So for logs,  the user should be able to set 3 levels of verbosity in the 
> session, that will override the default verbosity specified in the 
> hive-site.xml file.
> 0. None - IGNORE
> 1. Execution - Just shows the map-reduce tasks completing 
> 2. Performance - Execution + Performance counters dumped at the end
> 3. Verbose - All logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-10119) Allow Log verbosity to be set in hiveserver2 session

2015-04-06 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482573#comment-14482573
 ] 

Hive QA commented on HIVE-10119:




{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12723492/HIVE-10119.3.patch

{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 8705 tests executed
*Failed tests:*
{noformat}
TestMinimrCliDriver-smb_mapjoin_8.q - did not produce a TEST-*.xml file
org.apache.hive.service.cli.operation.TestOperationLoggingAPI.testFetchResultsOfLogWithExecutionMode
org.apache.hive.service.cli.operation.TestOperationLoggingAPI.testFetchResultsOfLogWithNoneMode
org.apache.hive.service.cli.operation.TestOperationLoggingAPI.testFetchResultsOfLogWithPerformanceMode
org.apache.hive.service.cli.operation.TestOperationLoggingAPI.testFetchResultsOfLogWithVerboseMode
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3302/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3302/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-3302/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 5 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12723492 - PreCommit-HIVE-TRUNK-Build

> Allow Log verbosity to be set in hiveserver2 session
> 
>
> Key: HIVE-10119
> URL: https://issues.apache.org/jira/browse/HIVE-10119
> Project: Hive
>  Issue Type: Improvement
>  Components: HiveServer2
>Reporter: Hari Sankar Sivarama Subramaniyan
>Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-10119.1.patch, HIVE-10119.2.patch, 
> HIVE-10119.3.patch
>
>
> We need to be able to set logging per HS2 session.
> The client often uses the map-reduce completion matrix (Execution) that shows 
> up in Beeline to debug performance. User might not want the verbose log view 
> all the time since it obfuscates the Execution information. Hence the client 
> should be able to change the verbosity level.
> Also, there are 2 levels of verbosity at HS2 logging and not 3. The users 
> might want Execution + Performance counters only - so that level needs to be 
> added.
> So for logs,  the user should be able to set 3 levels of verbosity in the 
> session, that will override the default verbosity specified in the 
> hive-site.xml file.
> 0. None - IGNORE
> 1. Execution - Just shows the map-reduce tasks completing 
> 2. Performance - Execution + Performance counters dumped at the end
> 3. Verbose - All logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-10119) Allow Log verbosity to be set in hiveserver2 session

2015-04-06 Thread Thejas M Nair (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482239#comment-14482239
 ] 

Thejas M Nair commented on HIVE-10119:
--

The patch looks great. Can you also make one more change ? Change the enum 
loggingLevel to LoggingLevel ? (start with capital letter). +1 pending that 
change and test run.


> Allow Log verbosity to be set in hiveserver2 session
> 
>
> Key: HIVE-10119
> URL: https://issues.apache.org/jira/browse/HIVE-10119
> Project: Hive
>  Issue Type: Bug
>  Components: HiveServer2
>Reporter: Hari Sankar Sivarama Subramaniyan
>Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-10119.1.patch, HIVE-10119.2.patch, 
> HIVE-10119.3.patch
>
>
> We need to be able to set logging per HS2 session.
> The client often uses the map-reduce completion matrix (Execution) that shows 
> up in Beeline to debug performance. User might not want the verbose log view 
> all the time since it obfuscates the Execution information. Hence the client 
> should be able to change the verbosity level.
> Also, there are 2 levels of verbosity at HS2 logging and not 3. The users 
> might want Execution + Performance counters only - so that level needs to be 
> added.
> So for logs,  the user should be able to set 3 levels of verbosity in the 
> session, that will override the default verbosity specified in the 
> hive-site.xml file.
> 0. None - IGNORE
> 1. Execution - Just shows the map-reduce tasks completing 
> 2. Performance - Execution + Performance counters dumped at the end
> 3. Verbose - All logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-10119) Allow Log verbosity to be set in hiveserver2 session

2015-04-04 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395972#comment-14395972
 ] 

Hive QA commented on HIVE-10119:




{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12709410/HIVE-10119.1.patch

{color:red}ERROR:{color} -1 due to 6 failed/errored test(s), 8700 tests executed
*Failed tests:*
{noformat}
TestMinimrCliDriver-smb_mapjoin_8.q - did not produce a TEST-*.xml file
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_index_bitmap_auto_partitioned
org.apache.hive.hcatalog.hbase.TestPigHBaseStorageHandler.org.apache.hive.hcatalog.hbase.TestPigHBaseStorageHandler
org.apache.hive.jdbc.TestSSL.testSSLFetchHttp
org.apache.hive.service.cli.operation.TestOperationLoggingAPI.testFetchResultsOfLogWithExecutionMode
org.apache.hive.service.cli.operation.TestOperationLoggingAPI.testFetchResultsOfLogWithNoneMode
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3287/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3287/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-3287/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 6 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12709410 - PreCommit-HIVE-TRUNK-Build

> Allow Log verbosity to be set in hiveserver2 session
> 
>
> Key: HIVE-10119
> URL: https://issues.apache.org/jira/browse/HIVE-10119
> Project: Hive
>  Issue Type: Bug
>  Components: HiveServer2
>Reporter: Hari Sankar Sivarama Subramaniyan
>Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-10119.1.patch
>
>
> We need to be able to set logging per HS2 session.
> The client often uses the map-reduce completion matrix (Execution) that shows 
> up in Beeline to debug performance. User might not want the verbose log view 
> all the time since it obfuscates the Execution information. Hence the client 
> should be able to change the verbosity level.
> Also, there are 2 levels of verbosity at HS2 logging and not 3. The users 
> might want Execution + Performance counters only - so that level needs to be 
> added.
> So for logs,  the user should be able to set 3 levels of verbosity in the 
> session, that will override the default verbosity specified in the 
> hive-site.xml file.
> 0. None - IGNORE
> 1. Execution - Just shows the map-reduce tasks completing 
> 2. Performance - Execution + Performance counters dumped at the end
> 3. Verbose - All logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)