uranusjr commented on code in PR #70225:
URL: https://github.com/apache/airflow/pull/70225#discussion_r3793066038


##########
providers/standard/src/airflow/providers/standard/sensors/asset.py:
##########
@@ -0,0 +1,225 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+from __future__ import annotations
+
+from typing import TYPE_CHECKING, Any
+
+from airflow.providers.common.compat.module_loading import import_string
+from airflow.providers.common.compat.sdk import (
+    Asset,
+    AssetAlias,
+    BaseSensorOperator,
+    PokeReturnValue,
+)
+from airflow.providers.standard.version_compat import AIRFLOW_V_3_4_PLUS
+
+if TYPE_CHECKING:
+    from collections.abc import Callable, Sequence
+    from datetime import datetime
+
+    from airflow.providers.common.compat.sdk import Context
+
+
+def _count_satisfied(count: int, expected_count: int) -> bool:
+    """
+    Return whether the number of (processed) asset events satisfies the 
expectation.
+
+    ``expected_count == -1`` means "at least one" (``count >= 1``); any other 
value
+    requires an exact match (``count == expected_count``).
+    """
+    if expected_count == -1:
+        return count >= 1
+    return count == expected_count

Review Comment:
   This means we won’t be able to do “at least n” where n > 1. Instead of 
having a magic number `-1`, maybe we can add a separate “policy” flag?
   
   Asset partitioning already introduced a similar concept with `MinimumCount`, 
and `WaitForAll`. Maybe this can use the same vocabulary?



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