turbaszek commented on issue #8765:
URL: https://github.com/apache/airflow/issues/8765#issuecomment-656712140
I screened the UPDATING.md for "breaking" changes that can be check /
communicated. I selected those explicitly saying "breaking" or sounding like
that. In general, we can split them into three categories:
- python code changes (related to DAGs etc)
- config changes
- cli changes (related to scripts etc)
I ended up with a list of 59 of changes:
```
'BaseOperator uses metaclass',
'Not-nullable conn_type column in connection table',
'Change signature of BigQueryGetDatasetTablesOperator',
'Unify `hostname_callable` option in `core` section',
'Changes in BigQueryHook',
'Use project_id argument consistently across GCP hooks and operators',
'GCSUploadSessionCompleteSensor signature change',
'Remove SQL support in base_hook',
'Changes to SalesforceHook',
'Rename parameter name in PinotAdminHook.create_segment',
'Rename parameter name in HiveMetastoreHook.get_partitions',
'Remove unnecessary parameter in FTPHook.list_directory',
'Remove unnecessary parameter in PostgresHook function copy_expert',
'Change parameter name in OpsgenieAlertOperator',
'Assigning task to a DAG using bitwise shift (bit-shift) operators are no
longer supported',
'Custom executors is loaded using full import path',
'Removed sub-package imports from `airflow/__init__.py`',
'Drop plugin support for stat_name_handler',
'Standardize handling http exception in BigQuery',
'Remove airflow.utils.file.TemporaryDirectory',
'Chain and cross_downstream moved from helpers to BaseOperator',
'Change python3 as Dataflow Hooks/Operators default interpreter',
'Logging configuration has been moved to new section',
'Simplification of CLI commands',
'Remove gcp_service_account_keys option in airflow.cfg file',
'Removal of airflow.AirflowMacroPlugin class',
' Change default aws_conn_id in EMR operators',
'Removal of redirect_stdout, redirect_stderr',
'Changes to SQLSensor',
'Idempotency in BigQuery operators',
'AWS Batch Operator',
'Additional arguments passed to BaseOperator cause an exception',
'Simplification of the TriggerDagRunOperator',
'Changes in Google Cloud Platform related hooks',
'Fernet is enabled by default',
'Changes to Google PubSub Operators, Hook and Sensor',
'Removed Hipchat integration',
'The gcp_conn_id parameter in GKEPodOperator is required',
'Changes to propagating Kubernetes worker annotations',
'Remove provide_context',
'Variables removed from the task instance context',
'Moved provide_gcp_credential_file decorator to GoogleBaseHook',
'Changes to S3Hook',
'Changes to Google Transfer Operator',
'Changes in Google Cloud Transfer Hook',
'CLI reorganization',
'Removal of Mesos Executor',
'Changes to SalesforceHook',
'HTTPHook verify default value changed from False to True.',
'Changes to GoogleCloudStorageHook',
'Changes to CloudantHook',
'Unify default conn_id for Google Cloud Platform',
'Changes to sensor imports',
'Deprecate legacy UI in favor of FAB RBAC UI',
'CLI Changes',
'Unification of `do_xcom_push` flag',
'Changes to Dataproc related Operators',
'Changes to skipping behaviour of LatestOnlyOperator',
'Change default snowflake_conn_id for Snowflake hook and operators'
```
I like the idea proposed by @mik-laj in #9467 with defining `Rules` and
that's something we should follow I think.
Questions that should be addressed before we move on:
- do we plan to only "warn" or should we consider also "auto-refactor"?
- if there's backward compatibility do we want to include such check?
If we are ok with the approach proposed by Kamil I can evaluate those
changes and create issues so the work can be split.
----------------------------------------------------------------
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]
