What steps will reproduce the problem?
1. install kettle spoon GA 5.3.0.0-213
2. install bqjdbc standalone 1.4 driver and dependencies according to install
instruction
3. create bigquery client ID (installed application option)
4. open kettle and define a new database connection (generic DB, JDBC)
5. define URL:
https://accounts.google.com/o/oauth2/auth?scope=email%20profile&redirect_uri=urn
:ietf:wg:oauth:2.0:oob&response_type=code&client_id=455782345370-oaoen19skajp3v6
sgr7eggvp0r575gob.apps.googleusercontent.com
6. define driver class name: net.starschema.clouddb.jdbc.BQDriver
7. define username:
455782345370-oaoen19skajp3v6sgr7eggvp0r575gob.apps.googleusercontent.com
8. define passwort (set to value shown for that API under client secret)
What is the expected output? What do you see instead?
I expect a successful connection message but get a pop up with the following
error message (for the complete message see attached file):
Error connecting to database [BQ] :
org.pentaho.di.core.exception.KettleDatabaseException:
Error occurred while trying to connect to the database
Error connecting to database: (using class net.starschema.clouddb.jdbc.BQDriver)
No suitable driver found for
https://accounts.google.com/o/oauth2/auth?scope=email
%20profile&redirect_uri=urn:ietf:wg:oauth:2.0:oob&response_type=code&client_id=4
55782345370-
oaoen19skajp3v6sgr7eggvp0r575gob.apps.googleusercontent.com
org.pentaho.di.core.exception.KettleDatabaseException:
Error occurred while trying to connect to the database
Error connecting to database: (using class net.starschema.clouddb.jdbc.BQDriver)
No suitable driver found for
https://accounts.google.com/o/oauth2/auth?scope=email
%20profile&redirect_uri=urn:ietf:wg:oauth:2.0:oob&response_type=code&client_id=4
55782345370-
oaoen19skajp3v6sgr7eggvp0r575gob.apps.googleusercontent.com
What version of the product are you using? On what operating system?
see above for product (kettle) version; running on windows7 enterprise, SP1,
64bit
Please provide any additional information below.
Original issue reported on code.google.com by frank.d....@gmail.com on 2 Apr 2015 at 6:24
Original issue reported on code.google.com by
frank.d....@gmail.comon 2 Apr 2015 at 6:24Attachments: