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

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

                Author: ASF GitHub Bot
            Created on: 17/Feb/23 17:59
            Start Date: 17/Feb/23 17:59
    Worklog Time Spent: 10m 
      Work Description: yigress commented on PR #4068:
URL: https://github.com/apache/hive/pull/4068#issuecomment-1435041562

   @zabetak @amanraj2520 I wonder if we should continue with this fix, rather 
than revert HIVE-27016? The reason is that I see in branch-4 the permissions 
were changed as proposed here in HIVE-22589, but it is not apparent to me that 
HIVE-22589 itself causes the permission changes, so it looks like the 
orc_merge* tests permissions should have been updated. 
   
   I agree that stabilizing the tests is the first priority in branch-3 right 
now. Our users looking forward to the next branch-3 release as branch-4 seems a 
bit too far, this feature is very important for users who are staying on 
branch-3 with storagehandlers.  We will watch branch-3 progress and not making 
addons until tests are stabilized.




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

    Worklog Id:     (was: 846230)
    Time Spent: 1h  (was: 50m)

> Fix orc_merge*.q test failures
> ------------------------------
>
>                 Key: HIVE-27089
>                 URL: https://issues.apache.org/jira/browse/HIVE-27089
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Aman Raj
>            Assignee: Aman Raj
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The orc_merge1,2,3,4,10 .q tests fails with the following errors : 
> < -rw-rw-rw- 3 ### USER ### ### GROUP ### 349 ### HDFS DATE ### hdfs://### 
> HDFS PATH ###
> ---
> > -rw-r--r-- 3 ### USER ### ### GROUP ### 349 ### HDFS DATE ### hdfs://### 
> > HDFS PATH ###



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

Reply via email to