-
Notifications
You must be signed in to change notification settings - Fork 111
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
[DATA-851] Data CLI: retry query requests, logging, file naming #1642
Conversation
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 to me! Just one nitty suggestion on the time stuff + a question about the connection reset thing
cli/data.go
Outdated
metadataDir = "metadata" | ||
maxRetryCount = 5 | ||
logEveryN = 100 | ||
timeFormat = "2006-01-02T150405.0000Z" |
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.
Nit: If this is a standard a standard time format (e.g. rfc3339) it would be helpful to include a comment indicating that or use a const exposed by aa time package to indicate that (e.g. time.RFC3339)
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 originally did this to get nanoseconds (but we have file IDs to enforce uniqueness) and not use colons (since the mac browser shows them as "/"), but better to use the same format we're using when capturing data. Updated to RFC3339.
When/why does this happen? This gives me the impression we might be leaving orphaned connections |
This happened after running for ~20 mins when attempting to export 20k images, and @edaniels mentioned that it's highly likely to hit this error after so many consecutive requests. Follow-up PR will be batching/parallelizing requests to make this faster. |
|
The above addresses errors and feedback received on CLI data export usage.
Tested locally for both binary and tabular export.