You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/02/25 23:32:30 UTC

[GitHub] vanzin commented on issue #23827: [SPARK-26912][CORE][HISTORY] Allow setting permission for event_log

vanzin commented on issue #23827: [SPARK-26912][CORE][HISTORY] Allow setting permission for event_log
URL: https://github.com/apache/spark/pull/23827#issuecomment-467227991
 
 
   I'd like to understand more what scenario the current model does not cover.
   
   The objective here is to have all users share the event log directory, but only a privileged user (or the owner) read the logs.
   
   So the log directory should have permissions `1777` with owner:group set to a privileged owner or group. (On non-HDFS I think that actually should be 3777, but not sure how often people are not using HDFS here.) The SHS should be run using that owner:group, so that it can read and delete log files.
   
   With that configuration, all apps are able to write, but only the owner (and the privileged user) can read and delete the log files, assuming the default `770` permissions.
   
   So what is the use case that is not being covered? Arbitrary users being allowed to read other people's event logs? Without a concrete example I'm not sure that's desirable.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org