wdumper icon indicating copy to clipboard operation
wdumper copied to clipboard

Preview on results page

Open bennofs opened this issue 5 years ago • 2 comments

On the results page, there should be a way to already see a preview of the dump, to make the decision which dump to choose easier.

bennofs avatar Mar 06 '20 12:03 bennofs

Not sure whether this is the right place to ask, but the wdumper "about" page (https://tools.wmflabs.org/wdumps/about) doesn't appear to have any way to do this, and "Preview results" sounded reasonable, so...

I accidentally started 3 identical dumps at https://tools.wmflabs.org/wdumps/dumps?page=1. The only criterion I put on the dumps was "language='ru'". I didn't see much in the way of output, and it was only later that I realized this was because my jobs were queued.

I'd like to kill two of my dumps in the queue, but I can't see any way to do this. Can it be done?

And apropos of the name of this Issue ("Preview on results page"), it would be nice if the system could provide some estimate (preview) of how big a dump is likely to be. It's quite possible that my request to dump the Russian wikidata is an unreasonable one, i.e. a request that will generate huge amounts of data and/or consume too much computer resources for too long. If that's the case, I'd be happy to put more constraints on my request for results (if I could figure out how).

mcswell avatar May 28 '20 18:05 mcswell

Thanks for your feedback! I've opened a new issue for estimating dump size before generating a dump (https://github.com/bennofs/wdumper/issues/12).

I'd like to kill two of my dumps in the queue, but I can't see any way to do this. Can it be done?

Unfortunately, this is not possible right now. It requires some kind of authentication, which we don't have at the moment (otherwise, anyone could kill your dumps, which would not be good). A simple fix right now would be to prevent putting the exact same dump into the queue twice (this should be easy to implement, I've created https://github.com/bennofs/wdumper/issues/13 for this). In the future, we might implement some kind of session identification so that the creator of a dump can modify some of its properties (like retention time or killing it).

bennofs avatar Jun 03 '20 10:06 bennofs