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

Datasets won't be re-loaded if their loading logic or SQL transforms have changed but their source data hasn't #18

Open
toolness opened this issue Jan 24, 2019 · 1 comment

Comments

@toolness
Copy link
Contributor

As an example, even though I fixed #13, the derived tables for hpd_registrations still haven't been created because that dataset's data still hasn't changed, as it's only updated monthly.

Obviously this will be even worse for datasets that never change.

So it might be good if we provide some simple mechanism to force-reload a dataset.

@toolness
Copy link
Contributor Author

Okay, it's not particularly well-documented right now, but I've created a foundation for fixing this in faa39ea.

Running python dbtool.py lastmod:reset <dataset> can now be used to reset the last-modified metadata of one or more datasets, so that the next time their loader runs, it will load the whole thing.

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