okayhooni opened a new pull request, #24564:
URL: https://github.com/apache/superset/pull/24564

   ### SUMMARY
   
   - Currently, Google BigQuery python sdk is not compatible with `gevent`, due 
to some dynamic monkeypatching on python core library by `gevent`.
     - https://github.com/googleapis/python-bigquery/issues/697
     - https://github.com/gevent/gevent/issues/1797
     - https://github.com/grpc/grpc/issues/4629
   - Even though enabling `GLOBAL_ASYNC_QUERIES` feature flag, some superset 
UI&API remain to be called on webserver, instead of celery worker. (ex: 
`force_refresh` UI on `v2.1.0`)
   - So, it helps superset users, to notice `gunicorn` with `gevent` worker 
type is not compatible with `bigquery` data source.
   - Related community links
     - https://github.com/apache/superset/issues/23979
     - https://apache-superset.slack.com/archives/C015WAZL0KH/p1686908792979199
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   - just docs update
   
   ### TESTING INSTRUCTIONS
   - just docs update
   
   ### ADDITIONAL INFORMATION
   - [x] Has associated issue: https://github.com/apache/superset/issues/23979
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
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