Skip to content

Define the default snapshot scope for onCommit and onPause #339

Open

Description

Prior to the #295, full snapshot was the only option. With the #295 an option for "data" scope is introduced. The onCommit supposed to be a subset of onPause.

For backward compatibility the default (non provided) behavior is "Full". One of the comment Tim Hockin (@thockin) raised as part of the PR , is onCommit default supposed to be Data?

Decision needs to be made for it.

Activity

  1. EItanya commented on Jul 24, 2026

    @EItanya
    Collaborator

    Dmitry Berkovich (@dberkov) should we update this based on discussion from the onsite?

  2. SamPriyadarshi commented on Oct 18, 2026

    @SamPriyadarshi

    I think this has been resolved by the lifecycle-v2 steps: #2309 (v0.4.0) removed on_pause, so pause captures the commit scope, and #2364 (v0.5.0) renamed on_commit to preferred_fidelity, which defaults to MEMORY (the old FULL) in cmd/ateapi/internal/defaults/defaults.go. So the onCommit default stayed full rather than Data, and there's no separate onPause anymore. Any further change to the default seems to belong to #2102. Can this be closed as superseded?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/apiUser-facing API changeskind/featureAn enhancement / feature request or implementation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions