Revert "Deprecation of AutoML services: Add deprecation warnings and raise exceptions for already deprecated ones" #39753
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #38673
This PR constains explicit change filter warnings in
AutoMLTablesUpdateDatasetOperator
andAutoMLDeployModelOperator
by provideaction="error"
into the decorator which looks like an worst practice, because it can't be controlled by the end users.If this functional still exists and users could use it we should not raise an error here, user might want to control it by provide
-W
flag to the interpreter orPYTHONWARNINGS
env var: see Warning controlIf this functional not exists we could:
AirflowException
(we do not have appropriate exception, even if we add it it will available in Airflow 2.10+) in constructor (__init__
) methodThere is difference
deprecated and
removed`. Deprecated mean this functional still available (even if limited) but removed mean that this functional not available anymore. We should not use deprecated meaning in case when functional removed.There is an option to change by the separate PR instead of this revert.
cc: @VladaZakharova @molcay @shahar1