Skip to content

API: Multipart Upload with Presigned URL Parts - Moving Out of Experimental Phase #9193

@nopcoder

Description

@nopcoder

To enable upload of large files without requiring data going through LakeFS, a multipart presigned URL API was introduced in an experimental state.
This functionality provides a more efficient upload mechanism for clients needing to handle large file sizes.

To improve usability and ensure client support, we propose transitioning this API out of the experimental phase.
This transition will involve a phased approach to minimize disruption to existing clients and specify the current limitation in using it. (Current support is only on S3)

The proposed steps are:

  1. Promotion to Non-Experimental: The multipart presigned URL API will be promoted from the experimental designation to a stable, non-experimental status.
  2. Deprecation of Experimental Endpoint: The original experimental endpoint will be deprecated, providing a clear timeline for client migration to the stable endpoint.
  3. Operation ID Refinement (Opportunity): During this transition, we will also evaluate and potentially update the Operation ID for single presigned URL generation (currently uploadPart) to a more descriptive and consistent name. We may also explore the addition of for retrieving a list of presigned part links.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/APIImprovements or additions to the API

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions