Skip to content

Document the visibility cost of data attributes in Temporal memo - #610

Closed
ahmadmaha02 wants to merge 1 commit into
indeedeng:mainfrom
ahmadmaha02:fix/visibility-memo-page-size
Closed

ahmadmaha02 wants to merge 1 commit into
indeedeng:mainfrom
ahmadmaha02:fix/visibility-memo-page-size

Conversation

@ahmadmaha02

@ahmadmaha02 ahmadmaha02 commented Oct 26, 2026 •

Copy link
Copy Markdown

Description

Document that useMemoForDataAttributes copies data attributes into Temporal visibility rows, and that external storage can keep large values out of those memos. This is an opt-in feature; disabling it for new workflows does not remove existing memos.

No search behavior changes. Temporal UI does not call the iWF search endpoint, and the Cloud SQL alert in #609 has not been tied to a particular query.

Checklist

  • Code compiles correctly (no code changes)
  • Tests for the changes have been added (documentation only)
  • All tests passing (go test ./service/api -count=1; integration tests not run)
  • This PR change is backwards-compatible
  • This PR CONTAINS a (planned) breaking change (it is not backwards compatible)

Related Issue

Refs #609

@ahmadmaha02
ahmadmaha02 force-pushed the fix/visibility-memo-page-size branch from fdb2064 to bd2031c Compare October 26, 2026 03:24
@ahmadmaha02 ahmadmaha02 changed the title Reduce default workflow search page size and document memo cost Document the visibility cost of data attributes in Temporal memo Oct 26, 2026
@ahmadmaha02
ahmadmaha02 deleted the fix/visibility-memo-page-size branch October 26, 2026 03: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