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

BigQueryType.fromStorage to ingest default project_ids #2928

Closed
patrick-wu opened this issue Apr 29, 2020 · 0 comments · Fixed by #2995
Closed

BigQueryType.fromStorage to ingest default project_ids #2928

patrick-wu opened this issue Apr 29, 2020 · 0 comments · Fixed by #2995
Labels
enhancement New feature or request

Comments

@patrick-wu
Copy link

Context

At my organization, we have separate GCP projects for sandbox, QA and prod, and they all contain identical schemas of datasets & tables on BigQuery. This means that if we were to take advantage of BigQueryType.fromStorage's cost-effectiveness, ideally we should pass in table specs without projectIds and have it inferred via a compile time argument.

When i try to compile with projec-id-less table specs, the macro expansion fails in the following manner:

/...Schemas.scala:29:6: exception during macro expansion: io.grpc.StatusRuntimeException: 

INVALID_ARGUMENT: 'x-goog-request-params' header value 'table_reference.project_id=&table_reference.dataset_id=my_dataset' is invalid.
[error]     @BigQueryType.fromStorage(

which seems like an empty project ID is used to build the dry run request.

Suggested feature

Is it possible to use a compiled argument, like -Dbigquery.project, somewhere within the StorageImpl section of the type provider to fill in as a default project id?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants