Switch BigQuery queries from using old vacancies table to vacancy table #1324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira ticket URL:
https://dfedigital.atlassian.net/browse/TEVA-458
Changes in this PR:
The production dataset in BigQuery used to contain a vacancies table which was written to via the BigQuery API. Now we export all tables, including 'vacancy', into Google Cloud Storage as CSVs and then import them into BigQuery that way. This PR moves SQL queries in BigQuery across from using the old vacancies table to using the new vacancy table in BigQuery to allow the code writing to the vacancies table to be removed in future.