[
https://issues.apache.org/jira/browse/ARROW-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242191#comment-16242191
]
ASF GitHub Bot commented on ARROW-1775:
---------------------------------------
pcmoritz commented on issue #1289: ARROW-1775: Ability to abort created but
unsealed Plasma objects
URL: https://github.com/apache/arrow/pull/1289#issuecomment-342518983
+1 LGTM Will leave this open a bit longer in case there are more comments.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Ability to abort created but unsealed Plasma objects
> ----------------------------------------------------
>
> Key: ARROW-1775
> URL: https://issues.apache.org/jira/browse/ARROW-1775
> Project: Apache Arrow
> Issue Type: New Feature
> Components: Plasma (C++)
> Reporter: Stephanie Wang
> Labels: pull-request-available
>
> It would be useful to allow a Plasma client to abort an object that it
> created but hasn't yet sealed. After the abort, it should appear as if the
> object was never created all. The logic is similar to the delete case, except
> that the client must release the object atomically with the removal of the
> object from the cache and store.
> In Ray, for example, we need this for the distributed version of the Plasma
> store, where many Plasma clients transfer objects to each other. If a sending
> Plasma client fails during a transfer, we want to make sure that the
> receiving client can abort the transfer, so that we can later recreate the
> object successfully. Otherwise, we will fail with an error that the object
> already exists.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
