[
https://issues.apache.org/jira/browse/ARROW-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532370#comment-16532370
]
Yuhong Guo commented on ARROW-2788:
-----------------------------------
I agree with you. When the Delete function is used to delete a single object,
it is OK give some message when the object is in undesirable status. However,
when we delete a list of objects, there are too many status combinations. It is
hard to give out a proper status hint.
We can implement a cache to store the objects to-be-deleted which are in use
and clean the object later when it is released.
> [Plasma] Defining Delete semantics
> ----------------------------------
>
> Key: ARROW-2788
> URL: https://issues.apache.org/jira/browse/ARROW-2788
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Philipp Moritz
> Priority: Major
>
> We should define what the semantics of Plasma's Delete operation is,
> especially in the presence of errors (object in use is deleted, non-existing
> object is deleted).
> My current take on this is the following:
> Delete should be a hint to the store to delete, so if the object is not
> present, it should be a no-op. If an object that is in use is deleted, the
> store should delete it as soon as the reference count goes to zero (it would
> also be ok, but less desirable in my opinion, to not delete it).
> I think this is a good application of the "Defining errors away" from John
> Ousterhouts book (A Philosophy of Software Design).
> Please comment in this thread if you have different opinions so we can
> discuss!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
