[GitHub] [airflow] josh-fell commented on pull request #29346: Check Absence of files or objects via GCSObjectExistenceSensor

["josh-fell (via GitHub)" <gi...@apache.org>]

josh-fell commented on PR #29346:
URL: https://github.com/apache/airflow/pull/29346#issuecomment-1433383415

   I agree that the suggested parameter name is confusing in the context of this operator. I also feel that this is a very niche use case and pattern in a data pipeline. I could envision pipelines designed in such a way where the task that deletes the file triggers a DAG which can only begin when said file is delete (either through TriggerDagRunOperator or Datasets). Perhaps this is more of a design exercise rather than something a pre-packaged operator should offer. But, by all means, a custom operator or using the `GcsHook` to do what you need is highly-encouraged for custom use cases; it's one of the beauties of Airflow: it's extensibility.
   
   The generic operator would indeed solve both problems, but does create user impact between versions and a maintenance burden for a corner case IMO.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org