You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/12/02 09:31:04 UTC

[GitHub] [airflow] potiuk edited a comment on issue #12744: Difference of extras Airflow 2.0 vs. Airflow 1.10

potiuk edited a comment on issue #12744:
URL: https://github.com/apache/airflow/issues/12744#issuecomment-737106323


   > @potiuk doesn't that mean that we keep them in core and make them available to all users, but they still have to refactor their DAGs (due to import changes)? Should we limit the number of changes required in users' DAGs?
   
   I think moving them to core now is NOT a good idea, and I think most of the "core" operators were moved inside the core anyway - at least changed module names to conform to AIP-21. I do not think there is a big difference whether they moved inside the core, or whether they are moved to providers. 
   
   ```
   http_operator -> http
   contrib.ftp_operator -> ftp 
   ```
   
   
   etc
   


----------------------------------------------------------------
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:
users@infra.apache.org