-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Topic/fault tolerance #34
base: main
Are you sure you want to change the base?
Conversation
class RayPythonOperator(PythonOperator): | ||
|
||
def __init__(self, *, | ||
python_callable: Callable, | ||
op_args: Optional[List] = None, | ||
op_kwargs: Optional[Dict] = None, | ||
templates_dict: Optional[Dict] = None, | ||
templates_exts: Optional[List[str]] = None, | ||
**kwargs) -> None: |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, this is basically the implementation of the task?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you leave a docstring here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously, the ray decorator used the PythonOperator
.
Assigning the recovered objects as Task attributes requires modifying to the pre_execute
method of the PythonOperator
.
RayPythonOperator
subclasses the PythonOperator
; it sets a custom pre_execute
method and implements logic to enable attribute assignment.
- I will add docstrings explaining the implementation.
…m. Clean-up logs and docstrings. Standardize naming.
Fault Tolerance mechanism is now functional.
To-do: