-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Adding UDF Resources to Queries #2015
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. 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, please reply here (e.g.
|
I signed it! |
See #2007 for an alternative. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
All commits were authored by me. I had a different email set as primary when the initial commit was made. |
I'm not entirely sure how that not works but you might have to rebase and On Friday, July 22, 2016, Daniel McClary [email protected] wrote:
Tom Schultz |
CLAs look good, thanks! |
OK rebased to reflect the proper author email. |
if not self._udf_resources: | ||
return [] | ||
if not all(isinstance(u, UDFResource) for u in self._udf_resources): | ||
raise ValueError("udf items must be UDFResource") |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
@dwmclary Thanks for the patch! |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
@dwmclary It appears that Github / the CLA bot do not think 1ff3252 was authored by you, but by another blind poet of the same name. |
Testing deploy with 1:1 class:json. Add overview.html Deploy script working now in testing. Fix code blocks. Add href support. Add snippets to base service module. closes #1951 Fix types generation. Fix linking. Fix external github links. Update gcloud-commit site files. Swtich to live site generation. clean up manifest for starters. Remove old example detection code. Update TOC.
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
Authored by me, and now painfully rebased to reflect it. |
OK, should be all fixed as soon as CLAbot looks at the authorship again. |
@googlebot can you check the CLA again? |
I need to get better at whitespace.
@tseaver @daspecster Any idea why the CLA isn't flipping? At this point all commits and author emails should point to me. There doesn't appear to be any rebase magic I can perform beyond this. Worst-case, I can re-fork and resubmit if we can't make @googlebot behave. |
Re-opened here |
The BigQuery client doesn't currently support adding UDF resources. This pull request adds a UDFResources object, and properties to set these resources on queries and QueryJobs.