You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2012/09/22 11:34:08 UTC

[jira] [Commented] (HADOOP-7310) Trash location needs to be revisited

    [ https://issues.apache.org/jira/browse/HADOOP-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461090#comment-13461090 ] 

Harsh J commented on HADOOP-7310:
---------------------------------

I'd like Solution B.

bq. Do folks see *real* compatibility problem here?

Not sure what a *real* compatibility means. But if you mean code/API wise, I don't see anything abnormal in doing this, nope.

Though, the point I think we're missing is that its not always the admin who uses trash. It is certainly the admin who uses quotas, but trash is hardly ever queried by the admin.

The problem is breakage of user-training. All users do fs-command X to check trash today. Tomorrow they'll have to do fs-command Y, and thats not easy to ask them to do. If their admin wants to change it for good, he may instruct the users after having made the change; but its no good to break it by default.

Hence, I'd vote for solution B, with same-old format, and with a proper doc added along.
                
> Trash location needs to be revisited
> ------------------------------------
>
>                 Key: HADOOP-7310
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7310
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.0.0-alpha
>            Reporter: Sanjay Radia
>            Assignee: Sanjay Radia
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira