We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Job controller is keeping an "in-memory" copy of the Job table of the database.
First of all, we should investigate why this is needed, maybe for performance reason?
If it's not needed, should we drop the in-memory database and only use PostgreSQL?
If the in-memory database needs to be kept around, then:
Job
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Job controller is keeping an "in-memory" copy of the Job table of the database.
First of all, we should investigate why this is needed, maybe for performance reason?
If it's not needed, should we drop the in-memory database and only use PostgreSQL?
If the in-memory database needs to be kept around, then:
Job
object a proper class and not a dictThe text was updated successfully, but these errors were encountered: