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

BigQuery Connector #2532

Closed
wants to merge 26 commits into from
Closed

Conversation

davidrabinowitz
Copy link
Contributor

Implementing a connector for BigQuery.

Instructions on how to use it are specified in the documentation - https://github.com/davidrabinowitz/prestosql/blob/master/presto-docs/src/main/sphinx/connector/bigquery.rst

Copy link
Member

@ebyhr ebyhr left a comment

Choose a reason for hiding this comment

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

Thanks for creating this PR. Only left basic comments as the initial review.

@davidrabinowitz
Copy link
Contributor Author

davidrabinowitz commented Jan 30, 2020

After making the POM changes I have this warning I can't rid off:

[INFO] Found Resolved Dependency/DependencyManagement mismatches:
[INFO] 	Ignoring Direct Dependencies.
[INFO] com.fasterxml.jackson.core:jackson-core:jar was excluded in DepMgt, but version 2.10.0 has been found in the dependency tree.
[INFO] org.apache.httpcomponents:httpclient:jar was excluded in DepMgt, but version 4.5.10 has been found in the dependency tree.
[INFO] org.apache.httpcomponents:httpcore:jar was excluded in DepMgt, but version 4.4.12 has been found in the dependency tree.
[INFO] org.slf4j:slf4j-api:jar was excluded in DepMgt, but version 1.7.29 has been found in the dependency tree.
[INFO] joda-time:joda-time:jar was excluded in DepMgt, but version 2.10.5 has been found in the dependency tree.
[WARNING] Potential problems found in Dependency Management 

The jars exist in the connector's zip. Any idea?

@electrum
Copy link
Member

electrum commented Feb 4, 2020

Don't worry about those dependency management warnings. They're bogus and can be ignored. I have a PR to remove that checker.

presto-bigquery/pom.xml Outdated Show resolved Hide resolved
Copy link
Member

@electrum electrum left a comment

Choose a reason for hiding this comment

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

First pass, lots of comments, mostly minor

presto-bigquery/pom.xml Outdated Show resolved Hide resolved
presto-bigquery/pom.xml Outdated Show resolved Hide resolved
presto-bigquery/pom.xml Show resolved Hide resolved
presto-docs/src/main/sphinx/connector/bigquery.rst Outdated Show resolved Hide resolved
presto-docs/src/main/sphinx/connector/bigquery.rst Outdated Show resolved Hide resolved
presto-docs/src/main/sphinx/connector/bigquery.rst Outdated Show resolved Hide resolved
presto-main/etc/config.properties Outdated Show resolved Hide resolved
@davidrabinowitz
Copy link
Contributor Author

@electrum @findepi All the issues have been fixed

Copy link
Member

@electrum electrum left a comment

Choose a reason for hiding this comment

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

I'm going to fix up these few small issues and merge it, so we can get this in for the next release.

One issue I found in testing is that you have to set both project-id and parent-project-id, but the error comes from the Google library and just says "Project ID", so it's confusing. Also, I'm not sure why I would need to set the parent unless I want separate billing, but I'm completely new to GCP so maybe it makes sense.

Also, can I get access to, or can you tell me how to create, the TPCH tables needed for TestBigQueryIntegrationSmokeTest?

@electrum
Copy link
Member

Merged, thanks!

@electrum electrum closed this Feb 29, 2020
@findepi findepi added this to the 331 milestone Mar 4, 2020
@electrum electrum mentioned this pull request Mar 11, 2020
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants