Skip to content
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

Resume on crash ability / keep track of progress #31

Open
ramotswa opened this issue Mar 18, 2015 · 0 comments
Open

Resume on crash ability / keep track of progress #31

ramotswa opened this issue Mar 18, 2015 · 0 comments

Comments

@ramotswa
Copy link

This is probably more a feature request than anything else;

It would be great to be able to pick up from where the loader left off in the case of a server disconnect / crash etc. I guess if the .sql files don't get deleted you could do an if exists on those, or keep track of what is being processed in a txt file...
Biggest issue I can see is that the subprocesses that are being called can't really raise an error if they fail, so we can't know if the ogr2ogr (for instance) completed successfully or not.

Happy to have a chat how this might be done and potentially contribute.

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant