Changeset View
Changeset View
Standalone View
Standalone View
python_modules/dagster/dagster/core/storage/output_manager.py
| Show First 20 Lines • Show All 49 Lines • ▼ Show 20 Lines | def copy_for_configured(self, description, config_schema, _): | ||||
| description=description or self.description, | description=description or self.description, | ||||
| resource_fn=self.resource_fn, | resource_fn=self.resource_fn, | ||||
| required_resource_keys=self.required_resource_keys, | required_resource_keys=self.required_resource_keys, | ||||
| output_config_schema=self.output_config_schema, | output_config_schema=self.output_config_schema, | ||||
| ) | ) | ||||
| class OutputManager(ABC): | class OutputManager(ABC): | ||||
| """Base class for user-provided output managers. OutputManagers are used to handle the outputs | """Base class for user-provided output managers. OutputManagers are used to handle the outputs | ||||
jordansanders: I wonder a) how much any of these docstrings remain useful and b) how much the… | |||||
| of solids. | of solids. | ||||
| The easiest way to define an OutputManager is with the :py:function:`output_manager` decorator. | |||||
| """ | """ | ||||
| @abstractmethod | @abstractmethod | ||||
| def handle_output(self, context, obj): | def handle_output(self, context, obj): | ||||
| """Handles an output produced by a solid. Usually, this means materializing it to persistent | """Handles an output produced by a solid. Usually, this means materializing it to persistent | ||||
| storage. | storage. | ||||
| Args: | Args: | ||||
| context (OutputContext): The context of the step output that produces this object. | context (OutputContext): The context of the step output that produces this object. | ||||
| obj (Any): The data object to be handled. | obj (Any): The data object to be handled. | ||||
| """ | """ | ||||
I wonder a) how much any of these docstrings remain useful and b) how much the OutputManager/InputManagers remain useful or if they should be folded into the IOManager base class.