Project

General

Profile

Idea #12706

Updated by Peter Amstutz over 6 years ago

> As a first step, the R SDK should allow me to allow to find collections and files in Keep using filtering on metadata, load the files into R, process them and then write the results back to a collection. 

 For this, we will provide a high level API.    The low-level Arvados API access can be provided either by googleAuthR (as described in #11876) or by hand.    If not using googleAuthR, the low-level API should not be accessible by the user, so that we can replace it with an auto-generated API later. 

 High level requirements: 

 * User can get a specific collection by UUID or portable_data_hash (PDH). 
 * User can get a list of collections, with standard Arvados filters. 
 * User can create a new, empty collection in a specific project (project is owner_uuid) 
 * Collection object supports these operations (using WebDAV unless otherwise noted) 
 ** Update collection name (via Arvados API) 
 ** Open a file or directory that already exists and get a File or Directory object  
 ** Read the listing of a Directory 
 ** Get size of a file 
 ** Read the contents of a File.    API should support reading a portion of the file at a certain offset and length 
 ** Put some text or bytes to file (replaces entire file) 
 ** Create a new File object under a certain path 
 ** Delete a File under a certain path 
 ** Move/rename a file or directory from one path to another within the same collection 

 If such a thing exists, implement R equivalent of "file-like objects" so that open Collection File objects can be used as input to R functions. 

 Writable WebDAV support is in progress and should be available soon.    Start by working on Arvados API access and reading from WebDAV.

Back