You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/05 10:06:00 UTC

[jira] [Work logged] (HIVE-26201) QueryResultsCache may have wrong permission if umask is too strict

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

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

                Author: ASF GitHub Bot
            Created on: 05/May/22 10:05
            Start Date: 05/May/22 10:05
    Worklog Time Spent: 10m 
      Work Description: skysiders opened a new pull request, #3267:
URL: https://github.com/apache/hive/pull/3267

   HIVE-26201 QueryResultsCache should add permission check after mkdir with special permission
   ### What changes were proposed in this pull request?
   TezSessionState, QueryResultsCache and Context use mkdirs(path, permission) to create directory with special permission. But If the umask is too restrictive, permissions may not work as expected. So we need to check if permission is set as expected.
   
   
   ### Does this PR introduce _any_ user-facing change?
   no
   
   




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

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

> QueryResultsCache may have wrong permission if umask is too strict
> ------------------------------------------------------------------
>
>                 Key: HIVE-26201
>                 URL: https://issues.apache.org/jira/browse/HIVE-26201
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor, Tez
>    Affects Versions: 3.1.3
>            Reporter: Zhang Dongsheng
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> TezSessionState, QueryResultsCache and Context use mkdirs(path, permission) to create directory with special permission. ButĀ If the umask is too restrictive, permissions may not work as expected. So we need to check if permission is set as expected.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)