-
Notifications
You must be signed in to change notification settings - Fork 328
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
Apply Operand Closure clean up #3205
Conversation
Some suggestions are here: #3193 (comment) |
126a14c
to
bd40696
Compare
bd40696
to
aedddb9
Compare
92c68aa
to
d1ec187
Compare
d1ec187
to
3bcb798
Compare
Can we add some tests to check that closure cleanup are actually executed? |
9228143
to
960a7e4
Compare
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.
LGTM
029e213
to
9ae0ea5
Compare
201395f
to
c73744f
Compare
4080e71
to
ef47200
Compare
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.
LGTM.
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.
LGTM
* Initially implemented closure clean up * Initially implemented support for ray task mode * Add an option to selectively clean up or disable this feature * code refactor * Try to fix vineyard pickle error * code refactor * code refactor and avoid duplicated logic key generation * code refactor * add additional tests and code refactor * code refactor * refactor additional tests * misc * code refactor * improve procedure of storage_put to work regardless of context instances (cherry picked from commit 148bed8)
* Initially implemented closure clean up * Initially implemented support for ray task mode * Add an option to selectively clean up or disable this feature * code refactor * Try to fix vineyard pickle error * code refactor * code refactor and avoid duplicated logic key generation * code refactor * add additional tests and code refactor * code refactor * refactor additional tests * misc * code refactor * improve procedure of storage_put to work regardless of context instances (cherry picked from commit 148bed8)
* Initially implemented closure clean up * Initially implemented support for ray task mode * Add an option to selectively clean up or disable this feature * code refactor * Try to fix vineyard pickle error * code refactor * code refactor and avoid duplicated logic key generation * code refactor * add additional tests and code refactor * code refactor * refactor additional tests * misc * code refactor * improve procedure of storage_put to work regardless of context instances (cherry picked from commit 148bed8)
* Initially implemented closure clean up * Initially implemented support for ray task mode * Add an option to selectively clean up or disable this feature * code refactor * Try to fix vineyard pickle error * code refactor * code refactor and avoid duplicated logic key generation * code refactor * add additional tests and code refactor * code refactor * refactor additional tests * misc * code refactor * improve procedure of storage_put to work regardless of context instances (cherry picked from commit 148bed8)
* Initially implemented closure clean up * Initially implemented support for ray task mode * Add an option to selectively clean up or disable this feature * code refactor * Try to fix vineyard pickle error * code refactor * code refactor and avoid duplicated logic key generation * code refactor * add additional tests and code refactor * code refactor * refactor additional tests * misc * code refactor * improve procedure of storage_put to work regardless of context instances (cherry picked from commit 148bed8)
What do these changes do?
Under ray task mode, func key, i.e. ray.ObjectRef, shall be serialized by Ray rather than Mars. As a result, relevant tests are temporarily disabled for Github checks but passed locally with some modifications.
Lifecycle management of UDF storage object is planned in another PR.
Related issue number
#3193
Check code requirements