-
Notifications
You must be signed in to change notification settings - Fork 108
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
Remove controller parameter from queries #2575
Remove controller parameter from queries #2575
Conversation
This comment has been minimized.
This comment has been minimized.
3e84a42
to
08bf357
Compare
680db64
to
e1c65fa
Compare
e1c65fa
to
6c9a5fd
Compare
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.
Looks very good. I just have the usual pile of nits, small things, and suggestions.
0212ba6
to
80397ba
Compare
80397ba
to
1cc9dfe
Compare
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.
Looks good...but, of course, I can't help but comment on stuff.
So, if you find none of my comments worth acting on, let me know and I'll close them.
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.
Looks good.
Would just like to make sure we don't execute unnecessary code in debug statements, and make sure the TODO
s are properly captured in issues, and removed from the code.
"controller" is becoming just a dataset metadata; perhaps useful to filter based on origin, but not essential. The new /datasets/list API is based on a SQL query of the Datasets table, supporting filtering by name (substring, e.g., "fio"), controller, start and end time range (which can be used together or independently for a "before" or "after"). The Dataset record now has both `created` and `uploaded` timestamps, where the latter is the old `created` (defaults to current time of `Dataset` commit) and the new `created` is read from the tarball `metadata.log` file. Dataset SQL uniqueness is defined now only by the dataset name.
Try to work around an inexplicable test tarball unpacking problem on Jenkins by re-packing my modified test-5.2.tar.xz inside a local container.
Mostly factoring out some comments that have become issues.
1cc9dfe
to
d9bb283
Compare
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.
Ship it!
"controller" is becoming just a dataset metadata; perhaps useful to filter based on origin, but not essential. The new
/datasets/list
API is based on a SQL query of theDatasets
table, supporting filtering by name (substring, e.g., "fio"), controller, start and end time range (which can be used together or independently for a "before" or "after").The
Dataset
record now has bothcreated
anduploaded
timestamps, where the latter is the oldcreated
(defaults to current time ofDataset
commit) and the newcreated
is read from the tarballmetadata.log
file.Dataset SQL uniqueness is defined now only by the dataset name.