Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use job class instead of hardcoded Job in AbstractDBMetastore #390

Closed
ilongin opened this issue Sep 4, 2024 · 0 comments · Fixed by #391
Closed

Use job class instead of hardcoded Job in AbstractDBMetastore #390

ilongin opened this issue Sep 4, 2024 · 0 comments · Fixed by #391
Assignees
@ilongin
Labels
priority-p1

Comments

@ilongin
Copy link
Contributor

ilongin commented Sep 4, 2024

Currently we use Job directly in methods like _parse_job() which will cause issues in SaaS.
We need to use job_class instead.
@ilongin ilongin self-assigned this Sep 4, 2024
@ilongin ilongin linked a pull request Sep 4, 2024 that will close this issue
Using job class instead of hardcodced Job #391
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ilongin ilongin

Labels
priority-p1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Using job class instead of hardcodced Job iterative/datachain
1 participant
@ilongin