-
Notifications
You must be signed in to change notification settings - Fork 1
feat: [PAGOPA-2696] Generating search indexes on payments
table
#131
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
Conversation
This pull request does not contain a valid label. Please add one of the following labels: |
The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually. |
The default action is to increase the |
payments
table
src/main/resources/db/migration/liquibase/changelog/1.0.2/db.changelog-202504220000.sql
Outdated
Show resolved
Hide resolved
src/main/resources/db/migration/liquibase/changelog/1.0.2/db.changelog-202504220000.sql
Outdated
Show resolved
Hide resolved
src/main/resources/db/migration/liquibase/changelog/db.changelog-master-1.0.2.xml
Outdated
Show resolved
Hide resolved
|
This PR contains the definition of new indexes on
payment
table. In order to execute some deep searches of flows by payments, it is needed to add new indexes on IUV and IUR fields. This avoid the search to be so much long when Technical Support's application invoke the search APIs on this application.Note:
Applying this change via Liquibase apply can lead to a lock on entire
fdr3.payment
table. During applies on UAT environment, the changes required about 10 minutes in order to be applied on tables of 25GB size.List of Changes
Motivation and Context
This change is required in order to resolve long timed operation during search operation in
payment
tableHow Has This Been Tested?
Screenshots (if appropriate):
Types of changes
expected)
Checklist: