Skip to content

fix multipart blob dimensionality for directory uploads#7621

Open
ApfelPresse wants to merge 1 commit into
flyteorg:masterfrom
ApfelPresse:fix/multipart-blob-directory-literal
Open

fix multipart blob dimensionality for directory uploads#7621
ApfelPresse wants to merge 1 commit into
flyteorg:masterfrom
ApfelPresse:fix/multipart-blob-directory-literal

Conversation

@ApfelPresse

@ApfelPresse ApfelPresse commented Jul 3, 2026

Copy link
Copy Markdown

Why are the changes needed?

Directory blob uploads currently return a blob literal with SINGLE dimensionality, even though uploading a directory represents a multipart blob.

What changes were proposed in this pull request?

This PR updates the directory upload path in handleBlobType to return a blob literal with MULTIPART dimensionality.

It also adds a regression test that verifies a directory-based blob upload produces output metadata with:

dimensionality: MULTIPART

How was this patch tested?

Added a unit test for multipart blob uploads.

Tested with:

go test ./flytecopilot/data

Result:

PASS
ok github.com/flyteorg/flyte/flytecopilot/data

In addition, we built a Flyte container image with this patch applied to our current Flyte version and tested it in our environment. The patched version correctly returns multipart blob outputs with MULTIPART dimensionality for directory uploads.

Labels

fixed

Check all the applicable boxes

  • All new and existing tests passed.
  • All commits are signed-off.

@github-actions github-actions Bot added the flyte label Jul 3, 2026
Signed-off-by: kev <apfelpresse@mailbox.org>
Signed-off-by: kev <12345678+ApfelPresse@users.noreply.github.com>
@ApfelPresse ApfelPresse force-pushed the fix/multipart-blob-directory-literal branch from 23387e6 to 48814b8 Compare July 3, 2026 08:24
@ApfelPresse ApfelPresse marked this pull request as ready for review July 3, 2026 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants