[ 
https://issues.apache.org/jira/browse/HIVE-25158?focusedWorklogId=602103&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-602103
 ]

ASF GitHub Bot logged work on HIVE-25158:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/May/21 05:12
            Start Date: 26/May/21 05:12
    Worklog Time Spent: 10m 
      Work Description: ujc714 opened a new pull request #2319:
URL: https://github.com/apache/hive/pull/2319


   ### What changes were proposed in this pull request?
   Changed one line in 
service/src/java/org/apache/hive/service/cli/session/HiveSessionImpl.java. The 
session log directory should be <operationLogRootDir>/<session_id>/ instead of 
<operationLogRootDir>/<sessionHandle_id>/.
   
   
   ### Why are the changes needed?
   If we run beeline/hive command with parameter "--hiveconf 
hive.session.id=xxx", we can't see the query operation logs. And the operation 
logs can't be cleaned up by HS2.
   
   ### Does this PR introduce _any_ user-facing change?
   No.
   
   
   ### How was this patch tested?
   Added testSessionId1() and testSessionId2() in TestHiveCli.java.
   Run "mvn test -Dtest=org.apache.hive.beeline.cli.TestHiveCli"
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 602103)
    Remaining Estimate: 0h
            Time Spent: 10m

> Beeline/hive command can't get operation logs when hive.session.id is set
> -------------------------------------------------------------------------
>
>                 Key: HIVE-25158
>                 URL: https://issues.apache.org/jira/browse/HIVE-25158
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Robbie Zhang
>            Assignee: Robbie Zhang
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Usually, we can see the operation logs when we run a query from beeline/hive. 
> For example, the query ID, the time taken in compiling/executing, the 
> application information, etc. But if we use "–hiveconf hive.session.id=xxxx" 
> to set the session ID, we can't see the operation logs any more. Here are 
> examples:
>  * Without hive.session.id
> {code:java}
> $ hive -e "select 1"
> SLF4J: Class path contains multiple SLF4J bindings.
> ...
> Connected to: Apache Hive (version 3.1.3000.7.1.6.0-297)
> Driver: Hive JDBC (version 3.1.3000.7.1.6.0-297)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> INFO  : Compiling 
> command(queryId=hive_20210524105207_9d0774b2-8108-4800-a5e4-3b950ae03198): 
> select 1
> INFO  : Semantic Analysis Completed (retrial = false)
> INFO  : Created Hive schema: Schema(fieldSchemas:[FieldSchema(name:_c0, 
> type:int, comment:null)], properties:null)
> INFO  : Completed compiling 
> command(queryId=hive_20210524105207_9d0774b2-8108-4800-a5e4-3b950ae03198); 
> Time taken: 0.122 seconds
> INFO  : Executing 
> command(queryId=hive_20210524105207_9d0774b2-8108-4800-a5e4-3b950ae03198): 
> select 1
> INFO  : Completed executing 
> command(queryId=hive_20210524105207_9d0774b2-8108-4800-a5e4-3b950ae03198); 
> Time taken: 0.016 seconds
> INFO  : OK
> +------+
> | _c0  |
> +------+
> | 1    |
> +------+
> 1 row selected (0.318 seconds)
> Beeline version 3.1.3000.7.1.6.0-297 by Apache Hive
> {code}
>  * With hive.session.id
> {code:java}
> $ hive --hiveconf hive.session.id=abcd -e "select 1"
> SLF4J: Class path contains multiple SLF4J bindings.
> ...
> Connected to: Apache Hive (version 3.1.3000.7.1.6.0-297)
> Driver: Hive JDBC (version 3.1.3000.7.1.6.0-297)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> +------+
> | _c0  |
> +------+
> | 1    |
> +------+
> 1 row selected (5.862 seconds)
> Beeline version 3.1.3000.7.1.6.0-297 by Apache Hive
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to