You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the time being, if a query runs into a non-responding datanode (404 or read timeout) or metadata issue (size or checksum) the files will remain stuck in a loop of errors for as long as you retry downloading the query.
It is easy to bypass this with 5 lines of esgpull python client. But it would be much cleaner/convenient to wrap this into a subcommand and call it from command line.
Something like:
esgpull flush-query <######>
Expected behaviour: flushes the db, optionally asks if query is to be deleted
The text was updated successfully, but these errors were encountered:
For the time being, if a query runs into a non-responding datanode (404 or read timeout) or metadata issue (size or checksum) the files will remain stuck in a loop of errors for as long as you retry downloading the query.
It is easy to bypass this with 5 lines of esgpull python client. But it would be much cleaner/convenient to wrap this into a subcommand and call it from command line.
Something like:
Expected behaviour: flushes the db, optionally asks if query is to be deleted
The text was updated successfully, but these errors were encountered: