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

docs: event tag migration guide #781

Merged
merged 7 commits into from
Oct 27, 2023
Merged

Conversation

Roiocam
Copy link
Contributor

@Roiocam Roiocam commented Oct 26, 2023

References #731

Copy link
Member

@octonato octonato left a comment

Choose a reason for hiding this comment

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

I left some rewording suggestions.

I know realise that the way we are creating the migration script wouldn't allow for proper rolling upgrades.

To have it properly done, a user must first run a script that only creates the new columns.

Then they need to redeploy their application in legacy-mode. The application will start to write on all three columns. But the join will be done using the event_id.

After that, they should run the second part of the script that will migrate the rows and adapt the constraints. Once this is done, they can redeploy their application by disabling the legacy-mode.

docs/src/main/paradox/migration.md Outdated Show resolved Hide resolved
docs/src/main/paradox/migration.md Outdated Show resolved Hide resolved
docs/src/main/paradox/migration.md Outdated Show resolved Hide resolved
@Roiocam
Copy link
Contributor Author

Roiocam commented Oct 27, 2023

@octonato I have update the guide, Explicitly point the mutiple-phase rollout/deploy, and the two configuration style.

The script has update this too: 8587ba0

Can you take a look? Thanks.

Copy link
Member

@octonato octonato left a comment

Choose a reason for hiding this comment

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

Thanks @Roiocam

Looking good. Left a few minor change requests.
I think we can merge it after that.

docs/src/main/paradox/migration.md Outdated Show resolved Hide resolved
docs/src/main/paradox/migration.md Outdated Show resolved Hide resolved
Roiocam and others added 2 commits October 27, 2023 18:17
@Roiocam
Copy link
Contributor Author

Roiocam commented Oct 27, 2023

Thanks @Roiocam

Looking good. Left a few minor change requests. I think we can merge it after that.

Thanks for the feedback.

@octonato octonato merged commit 0197caa into akka:master Oct 27, 2023
13 checks passed
Bugsource pushed a commit to Bugsource/akka-persistence-jdbc that referenced this pull request Jan 8, 2024
* docs: event tag migration guide

* Update docs/src/main/paradox/migration.md

Co-authored-by: Renato Cavalcanti <[email protected]>

* Update docs/src/main/paradox/migration.md

Co-authored-by: Renato Cavalcanti <[email protected]>

* Update docs/src/main/paradox/migration.md

Co-authored-by: Renato Cavalcanti <[email protected]>

* fix: guide for multi-phase rollout

* Update docs/src/main/paradox/migration.md

Co-authored-by: Renato Cavalcanti <[email protected]>

* Update docs/src/main/paradox/migration.md

Co-authored-by: Renato Cavalcanti <[email protected]>

---------

Co-authored-by: Renato Cavalcanti <[email protected]>
@Roiocam Roiocam deleted the tag-migration-guide branch February 20, 2024 01:38
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.

2 participants