skysiders commented on PR #3894:
URL: https://github.com/apache/hive/pull/3894#issuecomment-1374681627

   Hi @cnauroth , thanks for your review. I'm glad to see your reply. In the 
MAPREDUCE-7375 you mentioned, I saw your approval of this fix, as well as the 
extremely special situation that you mentioned earlier that the umask would not 
be set to 777, and I very much agree with these. The repairs I submitted in 
other projects are also based on the way of thinking I mentioned above, that 
is, after we create a file, should we check and judge the permissions of this 
file and grant permissions to it. I think this matter is necessary, because as 
an upper-level application, it is difficult to determine the umask setting of 
the underlying file system (for example, the umask under Linux is set by the 
system administrator root, and the umask of the distributed filesystem is set 
by the underlying hdfs The user decides when starting dfs, while hive or other 
systems are run by program administrators, and these two users may not be the 
same user) This is my most fundamental point of view, and it is
  also the reason why I insist on this repair.
   
   I would like to discuss this issue with you further. Do you think that this 
repair method should be applied to those permissions of 770 instead of 
permissions like 700 (because 770 may be defaulted by the file system umask=022 
affect)?
   
   Finally, I am very happy to have such an in-depth discussion with you on the 
issue of file permissions. Thank you for your views on my point of view.
   
   Hi @abstractdog @ayushtkn , could you please have a look at this?


-- 
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.

To unsubscribe, e-mail: [email protected]

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to