Skip to content
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

Add parent workflow info to visibility schema #5054

Merged
merged 1 commit into from
Nov 3, 2023

Conversation

rodrigozhou
Copy link
Contributor

What changed?
Add parent workflow info to visibibility schema

Why?

How did you test it?
Unit tests

Potential risks
No.

Is hotfix candidate?
No.

@rodrigozhou rodrigozhou requested a review from a team as a code owner October 31, 2023 17:24
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Naive question: why wouldn't we create a new version v1.5? If v1.4 is rolled out already, wouldn't people not get this update?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We only release schema changes with minor release. v1.4 was added after v1.22 was released.

@rodrigozhou rodrigozhou merged commit 595b9ce into temporalio:main Nov 3, 2023
10 checks passed
@rodrigozhou rodrigozhou deleted the vis-parent-wf-schema branch November 3, 2023 22:10
nichtverstehen pushed a commit to nscloud-demo/temporal that referenced this pull request Nov 23, 2023
<!-- Describe what has changed in this PR -->
**What changed?**
Add parent execution search attributes to ES mappings

<!-- Tell your future self why have you made these changes -->
**Why?**
PR temporalio#5054 modified the SQL
schemas to add parent execution to visibility. This one does for ES.

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**
Unit Tests.

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
No.

<!-- Is this PR a hotfix candidate or require that a notification be
sent to the broader community? (Yes/No) -->
**Is hotfix candidate?**
No.
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.

None yet

2 participants