[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188967#comment-15188967 ]
Steve Loughran commented on HADOOP-12910: ----------------------------------------- # I'm going to be ruthless and say "I'd like to see a specification of this alongside the existing one". Because that one has succeeded in being a reference point for everyone; we need to continue that for a key binding. It should be straightforward here. # Is it the future that raises an IOE, or the operation? I can see both needing to # assuming this is targed @ Hadoop 3, it'd be nice to make sure this works really well with the Java 8 language features; maybe this could be the first use in the codebase. > Add new FileSystem API to support asynchronous method calls > ----------------------------------------------------------- > > Key: HADOOP-12910 > URL: https://issues.apache.org/jira/browse/HADOOP-12910 > Project: Hadoop Common > Issue Type: New Feature > Components: fs > Reporter: Tsz Wo Nicholas Sze > Assignee: Xiaobing Zhou > > Add a new API, namely FutureFileSystem (or AsynchronousFileSystem, if it is a > better name). All the APIs in FutureFileSystem are the same as FileSystem > except that the return type is wrapped by Future, e.g. > {code} > //FileSystem > public boolean rename(Path src, Path dst) throws IOException; > //FutureFileSystem > public Future<Boolean> rename(Path src, Path dst) throws IOException; > {code} > Note that FutureFileSystem does not extend FileSystem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)