Skip to content
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.

YACHT-1009: copy job now handles insert job duplicates #54

Merged

Conversation

marcin-kolda
Copy link
Contributor

No description provided.

@coveralls
Copy link

coveralls commented Sep 11, 2018

Pull Request Test Coverage Report for Build 579

  • 11 of 11 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.09%) to 79.076%

Totals Coverage Status
Change from base Build 557: 0.09%
Covered Lines: 2226
Relevant Lines: 2815

💛 - Coveralls

@@ -38,9 +41,14 @@ def run_copy_job_request(copy_job_request):

@staticmethod
@retry(Exception, tries=6, delay=2, backoff=2)
def __schedule(source_big_query_table, target_big_query_table):
def __schedule(source_big_query_table, target_big_query_table, job_id):
logging.info("Scheduling job ID: " + job_id)
job_data = {
"projectId": source_big_query_table.get_project_id(),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this line decides about from which project copy job quota is used? why source then?

how it is connected with jobReference.projectId field where target project id is used?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm... projectId doesn't exist in REST API. I remember we planned to remove it :), so I'll remove it.

@jarekdrabek jarekdrabek merged commit 64f3f22 into master Sep 12, 2018
@jarekdrabek jarekdrabek deleted the YACHT-1009_copy_job_should_handle_duplicated_job_id branch September 12, 2018 14:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants