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

Old data is (usually) better than no data for sources #75

Open
bhtucker opened this issue Dec 20, 2017 · 0 comments
Open

Old data is (usually) better than no data for sources #75

bhtucker opened this issue Dec 20, 2017 · 0 comments

Comments

@bhtucker
Copy link
Contributor

In a concurrent load, extracts may be observed to fail or may stall for long enough that the load process 'times out' waiting for them.

When this happens, the last-loaded version of the data source may be available elsewhere in the warehouse (ie, if loading in staging, a copy is sitting in the non-prefixed 'standard' position). Rather than fail the relation, we should try to load our new table using the data from that existing table.

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

No branches or pull requests

1 participant