ferruzzi commented on code in PR #53215:
URL: https://github.com/apache/airflow/pull/53215#discussion_r2208257897


##########
airflow-core/src/airflow/models/deadline.py:
##########
@@ -98,6 +98,61 @@ def _determine_resource() -> tuple[str, str]:
             f"{self.deadline_time} or run: {self.callback}({callback_kwargs})"
         )
 
+    @classmethod
+    @provide_session
+    def remove_deadlines(cls, *, session: Session, conditions: dict[Column, 
Any]) -> int:
+        """
+        Remove deadlines from the table which match the provided conditions 
and return the number removed.
+
+        NOTE: This should only be used to remove deadlines which are 
associated with
+            successful dagruns. If the deadline was missed, move it to the 
`missed_deadlines`
+            table after executing the callback.
+        TODO:  Create the missed_deadlines table (Ramit)
+
+        :param conditions: Dictionary of conditions to evaluate against.
+        :param session: Session to use.
+        """
+        from airflow.models import DagRun  # Avoids circular import
+
+        # Assemble the filter conditions.
+        filter_conditions = [column == value for column, value in 
conditions.items()]
+        if not filter_conditions:
+            return 0
+
+        try:
+            # Get deadlines which match the provided conditions and their 
associated DagRuns.
+            deadline_dagrun_pairs = (
+                session.query(Deadline, 
DagRun).join(DagRun).filter(and_(*filter_conditions)).all()
+            )
+        except SQLAlchemyError as e:
+            invalid_column = next(iter(conditions.keys()))  # Get the first 
key that caused the error.
+            message = f"Invalid column '{invalid_column}' specified in 
conditions while resolving deadlines. Rolling back changes."
+            logger.exception(message)
+            session.rollback()

Review Comment:
   I think you are right, I'll double check, but this may be unnecessary since 
the session.scalar should be a read-only transaction and the error would 
actually be thrown before the db is actually hit (while assembling the query).



-- 
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]

Reply via email to