You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2017/11/15 15:53:01 UTC

[jira] [Assigned] (ARROW-1775) Ability to abort created but unsealed Plasma objects

     [ https://issues.apache.org/jira/browse/ARROW-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes McKinney reassigned ARROW-1775:
-----------------------------------

    Assignee: Stephanie Wang

> 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
>            Assignee: Stephanie Wang
>              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
(v6.4.14#64029)