-
Notifications
You must be signed in to change notification settings - Fork 0
CROSSLINK-119 Implement archive function #232
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
32cfd8a to
395e456
Compare
d2c6ba5 to
87dccf1
Compare
| located_suppliers JSONB NOT NULL | ||
| ); | ||
|
|
||
| CREATE OR REPLACE FUNCTION archive_ill_transaction_by_date_and_status( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JanisSaldabols are there any provisions here to prevent starting two archive functions at the same time?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point
Added DB lock
3fb9f44 to
11d51c6
Compare
|
@adamdickmeiss I'm wondering if API endpoint is the best interface for this given that HTTP is just not great for modelling async stuff. Initially, I discussed with Janis making a separate binary for this so we can launch it as a Kubernetes CronJob. The really nice thing about this approach is that devops have 100% visibility into it. Thoughts? |
No description provided.