Skip to content

Finish the Life Cycle of Large Binaries #4123

Description

@kunwp1

clearExecutionResources unconditionally calls LargeBinaryManager.deleteAllObjects(), which deletes all large-binary objects in the shared texera-large-binaries bucket even though the method is intended to clean up resources for a single execution eid. This means any user action that triggers cleanup for one workflow execution can erase all other users’ large-binary data, violating tenant isolation and causing global data loss. Instead of a bucket-wide wipe, track the specific LargeBinary URIs associated with the given eid and delete only those objects; reserve any global deleteAllObjects call for tightly controlled, admin-only maintenance flows, if needed at all.

Impact / Priority

(P2)Medium – useful enhancement

Affected Area

Storage / Metadata

Activity

  1. added theissue type on Dec 8, 2025
  2. self-assigned this
    on Dec 8, 2025
  3. added a commit that references this issue on Jun 8, 2026
    48e800e
  4. added a commit that references this issue on Jun 10, 2026
    01eea9d
  5. added a commit that references this issue on Jun 16, 2026
    0f11ae7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions