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

feat: PagoPA-2427 migration service type adjustment 1️⃣ ㏈ #272

Merged
merged 8 commits into from
Jan 20, 2025

Conversation

alessio-acitelli
Copy link
Collaborator

List of Changes

  • created script to adjust values ​​in the serviceType field of ACA and WISP type debt positions

Motivation and Context

  • correctly value the previous ACA and WISP type debt positions

How Has This Been Tested?

  • manual test

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Copy link
Contributor

@cap-ang cap-ang left a comment

Choose a reason for hiding this comment

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

Just a doubt: does the execution of this transaction block other transactions? What kind of lock does it acquire?

it is important to understand this and test the migration duration, downtime should be avoided

Copy link
Contributor

@pasqualespica pasqualespica left a comment

Choose a reason for hiding this comment

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

test it into UAT env , according to @cap-ang comment too

@alessio-acitelli
Copy link
Collaborator Author

alessio-acitelli commented Dec 2, 2024

Just a doubt: does the execution of this transaction block other transactions? What kind of lock does it acquire?

it is important to understand this and understand the duration of the migration, downtime should be avoided

Yes, DML operation of type UPDATE locks the affected rows during the transaction.
The database locks the affected rows to prevent concurrent changes from other transactions.
This means that no other transaction can read or write the same rows until the lock is released (COMMIT or ROLLBACK).

To limit the problem, the transactional block could be removed, but the risk is that, in the event of errors, an inconsistent situation could be created.

Execution detail in UAT via dbeaver:

Execute time (ms) 13913
Fetch time (ms) 0
Total time (ms) 13913
Start time 2024-12-02 09:42:18.628
Finish time 2024-12-02 09:42:32.547

@cap-ang
Copy link
Contributor

cap-ang commented Jan 9, 2025

Changes are included in this PR

@pasqualespica pasqualespica changed the title feat: [PagoPA-2427] - migration service type adjustment feat: PagoPA-2427 migration service type adjustment Jan 14, 2025
@pasqualespica pasqualespica changed the title feat: PagoPA-2427 migration service type adjustment feat: PagoPA-2427 migration service type adjustment 1️⃣ Jan 14, 2025
@pasqualespica pasqualespica changed the title feat: PagoPA-2427 migration service type adjustment 1️⃣ feat: PagoPA-2427 migration service type adjustment 1️⃣ ㏈ Jan 14, 2025
Copy link
Contributor

This pull request does not contain a valid label. Please add one of the following labels: [major, minor, patch, patch, skip]

@pasqualespica pasqualespica merged commit 006ceaa into main Jan 20, 2025
34 of 41 checks passed
@pasqualespica pasqualespica deleted the PAGOPA-2427-serviceType-adjustment branch January 20, 2025 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev documentation Improvements or additions to documentation prod size/small uat
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants