From 3f6078716c38e23ec438d490854dd20240f1bcf9 Mon Sep 17 00:00:00 2001 From: JamieDeMaria Date: Tue, 30 Jan 2024 12:22:19 -0500 Subject: [PATCH] comment --- .../dagster/_core/execution/context/invocation.py | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/python_modules/dagster/dagster/_core/execution/context/invocation.py b/python_modules/dagster/dagster/_core/execution/context/invocation.py index 3e27abb7dcbe9..ca3b80c1e630e 100644 --- a/python_modules/dagster/dagster/_core/execution/context/invocation.py +++ b/python_modules/dagster/dagster/_core/execution/context/invocation.py @@ -66,6 +66,17 @@ def _property_msg(prop_name: str, method_name: str) -> str: class BaseDirectExecutionContext: + """Base class for any direct invocation execution contexts. Each type of execution context + (ex. OpExecutionContext, AssetExecutionContext) needs to have a variant for direct invocation. + Those direct invocation contexts have some methods that are not available until the context + is bound to a particular op/asset. The "bound" properties are held in PerInvocationProperties. + There are also some properties that are specific to a particular execution of an op/asset, these + properties are held in DirectExecutionProperties. Direct invocation contexts must + be able to be bound and unbound from a particular op/asset. Additionally, there are some methods + that all direct invocation contexts must implement so that the will be usable in the execution + code path. + """ + @abstractmethod def bind( self,