List view

• M5 (as time allows): Convenience layer for auto-generated clients

  This is much lower priority than the previous four milestones, but if we have time it would be good to go over the auto-generated client functionality for our other four clients and see if there are any good quality of life improvements we can make for users.

  Due by September 14, 2016

  •1/1 issues closed
  100% complete0 open1 closed

• M2: Performant extension to the core client for single file upload and download

  - Multi-part upload/download support for single files, with flexibility for the user to determine how performant/parallel the upload/download is, with smart defaults that will take advantage of their available network capacity. - Unit tests and CI tests for this functionality

  Due by August 17, 2016

  •2/2 issues closed
  100% complete0 open2 closed

• M1: Core Data Lake Store Filesystem Client

  - 1:1 mapping of filesystem - REST endpoints to client methods - Unit tests and CI tests for the core client covering all the methods - Pythonic Filesystem layer, including file class interfacing for the REST calls. This allows native interaction with file objects the same way a user would interact with basic python files and folders.

  Due by August 3, 2016

  •3/3 issues closed
  100% complete0 open3 closed