john-jac commented on PR #65789: URL: https://github.com/apache/airflow/pull/65789#issuecomment-4315032686
> It make sense to do it with PythonOperator because reading the head is not the final action they do... after the read the do something with it in the same function. That is very OK. > > I don't see the value of reading the file head just for sake of pushing to xcom. Can describe a real production use case for this? The primary use case is low-code/YAML-driven DAG generation (DagFactory, MWAA Serverless YAML workflows, and similar tools) where users can only reference pre-built operators — they can't use PythonOperator with custom callables or @task decorators. Without this operator, reading an S3 object is impossible in those environments. For traditional Python DAGs, I agree @task handles most read-then-process patterns well. But the gap in the operator catalog means low-code users have no path at all. It also pairs naturally with S3CreateObjectOperator as its read counterpart given that write has an operator and read doesn't. -- 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]
