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

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

                Author: ASF GitHub Bot
            Created on: 04/Feb/23 01:40
            Start Date: 04/Feb/23 01:40
    Worklog Time Spent: 10m 
      Work Description: yigress commented on PR #4013:
URL: https://github.com/apache/hive/pull/4013#issuecomment-1416595363

   @amanraj2520 I see you are fixing tests in branch-3, will really appreciate 
your help here. I run the unit test in hive-4 master locally and it passes, but 
in branch-3, it just hangs. the command i use is 
   
   MAVEN_OPTS="-Xmx6144m" mvn clean test -pl ql -Dos.arch=x86_64 
-Dmaven.javadoc.skip=true  -Drat.numUnapprovedLicenses=500 
-Dtest="org.apache.hadoop.hive.ql.exec.tez.TestTezOutputCommitter"
   
   it seems locally it times out to start a cluster. I tried some other unit 
test in the ql/tez, some can run locally, some seem to have same problem of 
hanging.
   
   it is hard to troubleshoot unit test failing if I can't run it locally.  How 
would you run it? Thank you in advance if you can help out!




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

    Worklog Id:     (was: 843603)
    Time Spent: 0.5h  (was: 20m)

> Invoke optional output committer in TezProcessor
> ------------------------------------------------
>
>                 Key: HIVE-27016
>                 URL: https://issues.apache.org/jira/browse/HIVE-27016
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor, StorageHandler
>    Affects Versions: 3.1.3
>            Reporter: Yi Zhang
>            Assignee: Yi Zhang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This is backport HIVE-24629 and HIVE-24867, so StorageHandler with their own 
> OutputCommitter run in tez.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to