Fix handling of default value and serialization of Param class #33141
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.
-- Split PR form #31301 to reduce volume and concerns --
This PR fixes the behavior of the
Param
class and resolves problems found while implementing #31301. Problems found there:Param
object theArgNotSet
Object was passed out as value whendump()
was called - now if no default is provided, this is now masked withNone
.None
was provided as default the check forhas_value
returnedTrue
which is not really expected.Param
and the value was initialized toArgNotSet
then during DAG serialization the object in the value was converted to a string representation. Upon de-serialization aParam
with no default came out with the default value<airflow.utils.types.ArgNotSet object at 0x7fb1c6344c40>
as string. Fixed serialization and now theArgNotSet
object is supported to be serialized/deserialized properly.Adjusted pytests accordingly to prevent a regression.