Skip to content

Use data payloads supplied by Server to download and upload blobs on Executor #1356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 14, 2025

Conversation

eabatalov
Copy link
Contributor

@eabatalov eabatalov commented Apr 11, 2025

In this PR we process data payloads sent by Server on HTTP (SSE task stream) path.
gRPC path is already doing that.

For both gRPC and HTTP paths we also upload task outputs to blob store if task output blob store URI prefix is supplied by Server.

Both gRPC and SSE task stream modes support direct blob store downloads and uploads now.

Tested these changes with and without Server supplied data payloads in S3 and local FS blob store modes. They changes are fully backward compatible.

…Executor

Tested these changes with and without Server supplied data payloads
in S3 and local FS blob store modes. They fully backward compatible.

Both gRPC and SSE task stream modes support direct blob store
downloads and uploads now.
@eabatalov eabatalov force-pushed the eugene-task-input-s3-download-http branch from fc48989 to 1ffdbc3 Compare April 11, 2025 16:13
@eabatalov eabatalov marked this pull request as ready for review April 11, 2025 16:13
@eabatalov eabatalov requested a review from diptanu April 11, 2025 16:14
@eabatalov eabatalov merged commit 7216adb into main Apr 14, 2025
9 checks passed
@eabatalov eabatalov deleted the eugene-task-input-s3-download-http branch April 14, 2025 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant