-
Notifications
You must be signed in to change notification settings - Fork 118
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 :: java.lang.NoSuchMethodError: 'java.lang.String com.google.cloud.bigquery.BigQueryOptions.getResolvedApiaryHost(java.lang.String)' #3233
Comments
I've also run into this issue simply trying to run the following |
I also got same issue Any Resolution??? |
Until the code is updated to fix the exception you can resolve the issue by downgrading. I just downgraded to version 2.35.0 and don't have the issue anymore |
Hi @pramod-prabhakar-kapase-db , @RaymondKADuncan , @RYenike , I was not able to reproduce this issue. I created a new maven project and was able to create new BigQuery objects in v2.38.2 and v2.36.0 for both the provided example code and |
My project uses maven without the BOM. We're unable to use the BOM because we have our own parent project serving as a BOM and nesting one within another doesn't seem to be supported |
Sorry for the late update, The command: |
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":
If you are still having issues, please include as much information as possible:
Environment details
General, Core, and Other are also allowed as types
Steps to reproduce
Code example
HttpBigQueryRpc:
this.bigquery = (new Bigquery.Builder(transport, new GsonFactory(), initializer)).setRootUrl(options.getResolvedApiaryHost("bigquery")).setApplicationName(options.getApplicationName()).build();
The text was updated successfully, but these errors were encountered: