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 "Eli Collins (Created) (JIRA)" <ji...@apache.org> on 2012/03/21 02:08:38 UTC
[jira] [Created] (HADOOP-8195) Backport FileContext to branch-1
Backport FileContext to branch-1
--------------------------------
Key: HADOOP-8195
URL: https://issues.apache.org/jira/browse/HADOOP-8195
Project: Hadoop Common
Issue Type: New Feature
Components: fs
Reporter: Eli Collins
It's hard to get users to migrate to FileContext because they (rightly!) want their software to work against Hadoop 1.x which only has FileSystem. Backporting FileContext to branch-1 would allow people to migrate to FileContext and still work against both Hadoop 1.x and 2.x (or whatever we call it). It probably isn't that much work since FileContext is mostly net new code with lots of tests. It's a pain to support the same code in two places, but we already have to do that with FileSystem, and that's the cost of introducing a new API instead of improving FileSystem in place.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8195) Backport FileContext to branch-1
Posted by "Kihwal Lee (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234428#comment-13234428 ]
Kihwal Lee commented on HADOOP-8195:
------------------------------------
Does this mean the sym link support will be backported as well?
> Backport FileContext to branch-1
> --------------------------------
>
> Key: HADOOP-8195
> URL: https://issues.apache.org/jira/browse/HADOOP-8195
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs
> Reporter: Eli Collins
>
> It's hard to get users to migrate to FileContext because they (rightly!) want their software to work against Hadoop 1.x which only has FileSystem. Backporting FileContext to branch-1 would allow people to migrate to FileContext and still work against both Hadoop 1.x and 2.x (or whatever we call it). It probably isn't that much work since FileContext is mostly net new code with lots of tests. It's a pain to support the same code in two places, but we already have to do that with FileSystem, and that's the cost of introducing a new API instead of improving FileSystem in place.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8195) Backport FileContext to branch-1
Posted by "Eli Collins (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234836#comment-13234836 ]
Eli Collins commented on HADOOP-8195:
-------------------------------------
This would get the client side but not the server side, which would need to be backported as well. I'm not planning to do this jira at the moment btw which is why I left it unassigned.
> Backport FileContext to branch-1
> --------------------------------
>
> Key: HADOOP-8195
> URL: https://issues.apache.org/jira/browse/HADOOP-8195
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs
> Reporter: Eli Collins
>
> It's hard to get users to migrate to FileContext because they (rightly!) want their software to work against Hadoop 1.x which only has FileSystem. Backporting FileContext to branch-1 would allow people to migrate to FileContext and still work against both Hadoop 1.x and 2.x (or whatever we call it). It probably isn't that much work since FileContext is mostly net new code with lots of tests. It's a pain to support the same code in two places, but we already have to do that with FileSystem, and that's the cost of introducing a new API instead of improving FileSystem in place.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira