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.

Sign up for GitHub

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

Jump to bottom

fix(clustering): session renamed fields #10352

Merged
merged 2 commits into from Feb 23, 2023
Merged

fix(clustering): session renamed fields #10352

merged 2 commits into from Feb 23, 2023

Conversation

samugi
Copy link
Contributor

@samugi samugi commented Feb 22, 2023 •
edited

Summary

for older DPs, session "renamed" fields were just copied, this fixes it by removing the old field from the configuration

Checklist

Full changelog

  • [Implement ...]

Issue reference

Fix #[issue number]

KAG-738

@bungle bungle added this to the 3.2.1 milestone Feb 22, 2023
@samugi
fix(clustering): session rename fields
7ee2588 
for older DPs, session "renamed" fields were just copied, this fixes it
by removing the old field from the configuration
@dndx dndx merged commit 90c707b into master Feb 23, 2023
@dndx dndx deleted the fix/session-cluster-compat branch February 23, 2023 03:04
@mashapedeployment mashapedeployment mentioned this pull request Feb 23, 2023
Merged
mashapedeployment pushed a commit that referenced this pull request Feb 23, 2023
@samugi @github-actions
fix(clustering/compat): session plugin renamed fields compatibility (…
41993c9 
…#10352)

For older version DPs, session "renamed" fields were just copied, this fixes it
by removing the old field from the configuration

KAG-738

(cherry picked from commit 90c707b)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bungle bungle bungle approved these changes

Assignees
No one assigned
Labels
changelog core/clustering size/M
Projects
None yet
Milestone
3.2.1
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@samugi @bungle @dndx