You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both gcloud-aio and aiogoogle has a aiohttp layer for all API calls to googleAPIs.
gcloud-aio has support to cloud storage,, BigQuery, pubsubs are there so we could use one library and also the library is very similar to the one used in airflow sync version which is google-cloud-storage.
So choosing gcloud-aio for having to ease of changes because similarity between sync library to async library
gcloud-aio
Pros
Cons
similar to sync library google cloud stroage
rewrite method support isnt there for huge files above 5 TB doesnt have
supports other bigquery and pubusbs services
aiogoogle
Pros
Cons
has more apis for google services
Certain methods implemenatations are not present (blob chunk size while copying not present)
Async version of https://github.com/apache/airflow/blob/1008d8bf8acf459dbc692691a589c27fa4567123/airflow/providers/google/cloud/sensors/gcs.py#L30 using one of the following libraries:
Official Python client does not support it yet: googleapis/google-cloud-python#3103
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: