We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
No description provided.
The text was updated successfully, but these errors were encountered:
Would adding a job_queue column fix this instead of creating new table per job queue?
Also, if it's fine with you. Is it ok if we move the swift-jobs tables under a swift_jobs schema?
Queries would be as follow:
SELECT job_id FROM swift_jobs.queue
Sorry, something went wrong.
No problem changing the table names. A job queue column is worth thinking about.
Implementations in are in the following PRS #20 hummingbird-project/swift-jobs#67 hummingbird-project/swift-jobs-redis#23
I suppose this issue can be closed now?
thoven87
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: