kacpermuda commented on code in PR #40589:
URL: https://github.com/apache/airflow/pull/40589#discussion_r1669047207
##########
airflow/providers/openlineage/conf.py:
##########
@@ -145,3 +145,8 @@ def execution_timeout() -> int:
"""[openlineage] execution_timeout."""
option = conf.get(_CONFIG_SECTION, "execution_timeout", fallback="")
return _safe_int_convert(str(option).strip(), default=10)
+
+
+@cache
+def include_full_task_info() -> bool:
+ return _is_true(conf.get(_CONFIG_SECTION, "include_full_task_info",
fallback="False"))
Review Comment:
Yes, what you're saying makes sense and it probably would be even easier for
the user to debug (the whole Airflow stops working unless you provide a valid
value). I don't know, i thought our approach makes sense but maybe we should
change it back. Any thoughts @mobuchowski @JDarDagran ? I think I proposed it
as we tried as hard as possible not to break anything in Airflow deployments,
even if somebody provided an OL config with a typo.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
