[
https://issues.apache.org/jira/browse/ARROW-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17658806#comment-17658806
]
Rok Mihevc commented on ARROW-1775:
-----------------------------------
This issue has been migrated to [issue
#17774|https://github.com/apache/arrow/issues/17774] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> 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: C++ - Plasma
> Reporter: Stephanie Wang
> Assignee: Stephanie Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.8.0
>
>
> 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
(v8.20.10#820010)
