-
Notifications
You must be signed in to change notification settings - Fork 43
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
Document for append operator #619
Conversation
Co-authored-by: Pankaj Koti <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #619 +/- ##
=======================================
Coverage 93.30% 93.30%
=======================================
Files 41 41
Lines 1672 1672
Branches 211 211
=======================================
Hits 1560 1560
Misses 89 89
Partials 23 23 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
output_table=Table(conn_id="postgres_conn"), | ||
) | ||
load_append = aql.load_file( | ||
input_file=File(path=DATA_DIR + "/homes2.csv"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
input_file=File(path=DATA_DIR + "/homes2.csv"), | |
input_file=File(path=DATA_DIR + "homes2.csv"), |
We have an extra /
here
What is the current behavior? In the past, we had a tutorial which illustrated how to use each of our operators/decorators: https://github.com/astronomer/astro-sdk/blob/be6280df00ccff0d7a1c0dfb099b2065303dbe88/REFERENCE.md closes: #590 What is the new behavior? Have a reference page per operator/decorator similar to https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/operators/ecs.html#howto-operator-ecsoperator In which we reference parts of an (automated tested) example DAG which illustrates the usage of that operator/decorator. Many of these use cases already exist in our example DAGs - we should reference them. Does this introduce a breaking change? Nope
What is the current behavior? In the past, we had a tutorial which illustrated how to use each of our operators/decorators: https://github.com/astronomer/astro-sdk/blob/be6280df00ccff0d7a1c0dfb099b2065303dbe88/REFERENCE.md closes: #590 What is the new behavior? Have a reference page per operator/decorator similar to https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/operators/ecs.html#howto-operator-ecsoperator In which we reference parts of an (automated tested) example DAG which illustrates the usage of that operator/decorator. Many of these use cases already exist in our example DAGs - we should reference them. Does this introduce a breaking change? Nope
Description
What is the current behavior?
In the past, we had a tutorial which illustrated how to use each of our operators/decorators:
https://github.com/astronomer/astro-sdk/blob/be6280df00ccff0d7a1c0dfb099b2065303dbe88/REFERENCE.md
closes: #590
What is the new behavior?
Have a reference page per operator/decorator similar to
https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/operators/ecs.html#howto-operator-ecsoperator
In which we reference parts of an (automated tested) example DAG which illustrates the usage of that operator/decorator.
Many of these use cases already exist in our example DAGs - we should reference them.
Does this introduce a breaking change?
Nope
Checklist