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

Konstantin Shvachko commented on HADOOP-6909:
---------------------------------------------

- Getting rid of common, as Dough proposed, is a good idea, imo.
- I think it makes sense to move fs APIs like FileSystem and FileContext into 
HDFS. The same way as mapreduce APIs like Mapper and Reducer are in mapreduce 
project.
- I looked at [commons.vfs|http://commons.apache.org/vfs/apidocs/index.html] 
packages. There are clearly some similarities with fs.FileSystem, but the 
differences are substantial. I believe one can implement {{commons.vfs.HDFS}} 
using {{hadoop.fs.FileSystem}}. But using commons.vfs as a new API for HDFS 
would be a big, incompatible, hard to justify change, which also lacks 
intrinsic for HDFS apis like getBlockLocations().
So at this point I don't understand what the proposal of moving fs packages 
into Jakarta Commons means.

> Umbrella ticket for reducing the number of libraries in Common
> --------------------------------------------------------------
>
>                 Key: HADOOP-6909
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6909
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Jeff Hammerbacher
>
> There seems to be some consensus that moving libraries out of Common, with 
> the eventual goal of getting rid of the Common package all together, is a 
> good idea: http://hadoop.markmail.org/thread/jhiactdekhywznac. Hopefully we 
> can collect the incremental tasks needed to achieve that goal here.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to