[
https://issues.apache.org/jira/browse/ARROW-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17659814#comment-17659814
]
Rok Mihevc commented on ARROW-2788:
-----------------------------------
This issue has been migrated to [issue
#19170|https://github.com/apache/arrow/issues/19170] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [Plasma] Defining Delete semantics
> ----------------------------------
>
> Key: ARROW-2788
> URL: https://issues.apache.org/jira/browse/ARROW-2788
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++ - Plasma
> 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
(v8.20.10#820010)
