Adding ability to give default QueryJobConfig to Client - #6088

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

CLAs look good, thanks!

@blainehansen

Making a PR from your master branch makes things hard for you over the long term: it creates barriers to synchronizing with this repository's master over time.

WRT the test failures, there is missing line / branch coverage for:

google/cloud/bigquery/client.py               374      1    160      1    99%   1244, 1236->1244

which is the case where no job_config is passed.

@tseaver Sorry about not creating a feature branch ha, I don't expect to maintain a fork for a long period, I was just hoping to include this feature, but I shouldn't have cut corners.

👍 yeah making that private is definitely a better choice 😄

🎊 🎊 🎊

Thanks everyone!