Skip to content
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

Implement Async BigQueryTablePartitionExistenceSensor #173

Closed
phanikumv opened this issue Mar 30, 2022 · 3 comments
Closed

Implement Async BigQueryTablePartitionExistenceSensor #173

phanikumv opened this issue Mar 30, 2022 · 3 comments

Comments

@phanikumv
Copy link
Collaborator

phanikumv commented Mar 30, 2022

Follow up of #68

Since the glcoud aio library doesnt retrieve partition information, we are awaiting the gcloud-aio API to get updated so that this story can be implemented.

Acceptance Criteria:

Unit Tests coverage in the PR (80% Code Coverage -- We will need to add CodeCov separately to measure code cov) with all of them passing
Example DAG using the async Operator that can be used to run Integration tests that are parametrized via Environment variables. Example - https://github.com/apache/airflow/blob/8a03a505e1df0f9de276038c5509135ac569a667/airflow/providers/google/cloud/example_dags/example_bigquery_to_gcs.py#L33-L35
Add proper docstrings for each of the methods and functions including Example DAG on how it should be used (populate
Exception Handling in case of errors
Improve the OSS Docs to make sure it covers the following:
Has an example DAG for the sync version
How to add a connection via Environment Variable & explain each of the fields. Example - https://airflow.apache.org/docs/apache-airflow-providers-postgres/stable/connections/postgres.html
How to use Guide for the Operator - example: https://airflow.apache.org/docs/apache-airflow-providers-postgres/stable/operators/postgres_operator_howto_guide.html

@pankajastro
Copy link
Contributor

Copy link
Contributor

github-actions bot commented Feb 2, 2024

This issue has been automatically marked as stale because it has been open for 30 days with no response from the author. It will be closed in next 15 days if no further activity occurs from the issue author.

@github-actions github-actions bot added the stale label Feb 2, 2024
Copy link
Contributor

This issue has been closed because it has not received response from the issue author.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants