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

Using Jobs.insert instead of Jobs.query for queries #2323

Merged
merged 2 commits into from
Aug 10, 2017
Merged

Conversation

garrettjonesgoogle
Copy link
Member

Fixes #1588 .

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Aug 9, 2017
Copy link
Contributor

@tswast tswast left a comment

Choose a reason for hiding this comment

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

I see two changes in here:

  1. add query params to the query job config. Those changes look fine to me.
  2. Add job ID argument to query function. I think we might want to go a step further and remove the QueryResponse / QueryRequest classes.

@@ -987,6 +987,19 @@ public static QueryResultsOption maxWaitTime(long maxWaitTime) {
QueryResponse query(QueryRequest request);

This comment was marked as spam.

This comment was marked as spam.

@garrettjonesgoogle
Copy link
Member Author

How about I just make the new function @BetaApi, since we'll go and break it later?

Copy link
Contributor

@tswast tswast left a comment

Choose a reason for hiding this comment

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

Thanks. Makes sense to limit the scope and mark as @BetaAPI to indicate it's likely to break.

These changes as-is are a big improvement. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants