vikramkoka opened a new pull request #11308:
URL: https://github.com/apache/airflow/pull/11308


   Created a new Airflow ETL tutorial to use functional DAGs. Also created a 
DAG to perform the same operations without using functional DAGs to be 
compatible with Airflow 1.10.x and to show the difference between the 
"functional" and the "classic" ways side by side to illustrate the differences. 
   
   I tried to make this simple and not rely on any operators. I will create the 
html documentation page to cover this as soon as I get confirmation from 
@casassg and @turbaszek that this is in the right general direction. Also 
tagging @ashb for general review. 
   
   closes: #9041 
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   


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

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


Reply via email to