[
https://issues.apache.org/jira/browse/HADOOP-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653497#action_12653497
]
Arun C Murthy commented on HADOOP-3953:
---------------------------------------
bq. To keep Unix-like semantics, it seems reasonable to be able to set the
sticky bit on a file (compared to a directory), but that doing so will have no
effect on the file. Unless anyone has a good reason to deviate?
+1 with the caveat that we heavily document the meaning of sticky bit for files.
> Sticky bit for directories
> --------------------------
>
> Key: HADOOP-3953
> URL: https://issues.apache.org/jira/browse/HADOOP-3953
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Reporter: Koji Noguchi
> Assignee: Jakob Homan
>
> Our users (especially Pig) heavily use /tmp for temporary storage.
> Permission are set to 777.
> However, this means any users can rename and also remove (by moving to
> .Trash) other users directories and files.
> It would be nice if we can have a sticky bit like unix.
> Copy&Pasted from manpage.
> STICKY DIRECTORIES
> When the sticky bit is set on a directory, files in that directory
> may be unlinked or renamed only by
> root or their owner. Without the sticky bit, anyone able to write to
> the directory can delete or rename
> files. The sticky bit is commonly found on directories, such as /tmp,
> that are world-writable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
