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

Steve Loughran commented on HADOOP-18287:
-----------------------------------------

I have an initial implementation of this on github. building but without tests 
yet...still planning that. 


> Provide a shim library for modern FS APIs
> -----------------------------------------
>
>                 Key: HADOOP-18287
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18287
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: fs
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Priority: Major
>
> Add a shim library to give libraries and applications built against hadoop 
> 3.2 access to APIs and features in later versions, especially those 
> delivering higher performance in cloud deployments. This will give them the 
> ability to invoke those APIs when available, so gain from the work everyone 
> has done. Key APIs are:
> * openFile
> * ByteBufferPositionedReadable
> * Vectored IO
> The library will either downgrade gracefully to existing code (openFile) or 
> simply thrown UnsupportedException when invoked -but offer probes for every 
> operation before invocation.
> This module will compile against hadoop 3.2.0; it will be tested against that 
> and later releases.
> We can and should release this on a different schedule; though ideally we 
> should issue releases in sync with new hadoop releases adding new supported 
> API calls.
> For that reason I think we could consider having separate git repository for 
> it. Verifying that the shim works against hadoop PRs could actually become 
> one of our regression tests -indeed, it should become one.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to