rathishkumar opened a new issue, #23979:
URL: https://github.com/apache/superset/issues/23979

   Unable to query BigQuery data. I could see the executed queries at the 
BigQuery project history. Even simple SQL statements are not returning results 
at Superset.
   
   #### How to reproduce the bug
   
   1. Installed latest version of Apache Superset (2.1) & tried with older 
previous version of Superset and Python (3.8)
   3. Installed SQLAlchemy BigQuery connector
   4. Created database connection successfully and able to see the datasets and 
tables
   5. Creating Dataset / creating charts / running simple SQL statements at SQL 
lab produce Gateway TimeOut error.
   
   ### Expected results
   
   Result set at sql lab / data returning at the superset for creating charts.
   
   ### Actual results
   
   Gateway Timeout Error - queries running forever and then timeout after the 
timeout threshold.
   
   #### Screenshots
   
   
![image](https://user-images.githubusercontent.com/3918929/237002815-a3e616e6-b27d-4b00-bc7c-6c17a155cfbb.png)
   
![image](https://user-images.githubusercontent.com/3918929/237004551-15b0c959-e969-4eb4-bf26-21b54adc7e90.png)
   
![image](https://user-images.githubusercontent.com/3918929/237003060-a39593a2-5186-4e15-aaa4-b344a8d6954a.png)
   
   
   ### Environment
   
   - Browser: Tested with Google Chrome, Edge, Safari
   - superset version: Superset 2.1.0 / Tested with Superset 2.0
   - python version: Python 3.10 / Tested with Python 3.8
   - bigquery connector: sqlalchemy-bigquery  1.6.1 / Tested with Pybigquery
   - OS version: Ubuntu 22.04.2 LTS
   - Hosted on: GCP VM
   
   
   ### Checklist
   
   - [ x ] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [ x ] I have reproduced the issue with at least the latest released 
version of superset.
   - [ x ] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   The VM hosted on GCP Compute Engine and verified the access to BigQuery - 
APIs access is already enabled and able to query data using the same connector 
(sqlalchemy-bigquery).
   
   ```
   from sqlalchemy.engine import create_engine
   from pprint import pprint
   
   bigquery_uri = f'bigquery://{project}/{table}'
   
   engine = create_engine(
       bigquery_uri,
   )
   
   query = f'SELECT * FROM table WHERE DATE(partition) = "2023-05-05" LIMIT 10;'
   rows = engine.execute(query).fetchall()
   
   rows = [dict(row) for row in rows]
   
   pprint(rows)
   ```
   
   Does not look like connectivity issue as I could see the datasets and tables 
listed for the database and once queries are executed, I could see the same 
successfully executed queries at the BigQuery.
   
   
![image](https://user-images.githubusercontent.com/3918929/237005148-66cd63d5-2e99-475c-9cc0-37bcfffcbea6.png)
   
   Please let me know if you require any additional information. Your 
assistance would be greatly appreciated. Thank you.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to