-
Notifications
You must be signed in to change notification settings - Fork 54
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
Use PostgreSQL instead of Redis for taskmanager's persistence #1626
Comments
5 tasks
bamthomas
added a commit
that referenced
this issue
Jan 15, 2025
bamthomas
added a commit
that referenced
this issue
Jan 15, 2025
bamthomas
added a commit
that referenced
this issue
Jan 15, 2025
bamthomas
added a commit
that referenced
this issue
Jan 15, 2025
bamthomas
added a commit
that referenced
this issue
Jan 15, 2025
bamthomas
added a commit
that referenced
this issue
Jan 17, 2025
bamthomas
added a commit
that referenced
this issue
Jan 17, 2025
bamthomas
added a commit
that referenced
this issue
Jan 17, 2025
bamthomas
added a commit
that referenced
this issue
Jan 17, 2025
bamthomas
added a commit
that referenced
this issue
Jan 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
For now the task manager uses a Redis Hashmap for storing tasks.
It can be cumbersome as, each time we change the structure it breaks the display of the tasks.
So tasks must be migrated.
Describe the solution you'd like
For persistence data in datashare (other that session data) we store it in the PostgreSQL database.
The schemas are migrated with liquibase.
The text was updated successfully, but these errors were encountered: