-
Notifications
You must be signed in to change notification settings - Fork 46
Issue741 movedatabasecode #815
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
base: master
Are you sure you want to change the base?
Conversation
|
TODO; move also the unit tests once settled on rearangement |
|
I'd try to do this exercise in atomic commits/PRs:
that will avoid long-running PR review cycles that block other progress e.g. I just started #824 to only move |
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.
some quick notes
| "duration": _ColumnProperties(dtype="str"), | ||
| "costs": _ColumnProperties(dtype="float64"), | ||
| } | ||
|
|
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.
The three comments above should be moved along with _COLUMN_REQUIREMENTS
| # Expected columns in the job DB dataframes. | ||
| # TODO: make this part of public API when settled? | ||
| # TODO: move non official statuses to seperate column (not_started, queued_for_start) | ||
| COLUMN_REQUIREMENTS = { |
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.
I don't think COLUMN_REQUIREMENTS belongs under the _job_database module.
The requirements describe what the job manager expects as columns, so this should stay close to the job manager module (__init__.py at the moment)
first proposal to seperate the job database/dataframe logic and the processbasedjobstart