You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/06/26 05:42:48 UTC
[jira] [Updated] (GORA-12) Semantics of DataStore.delete*
[ https://issues.apache.org/jira/browse/GORA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated GORA-12:
----------------------------------
Fix Version/s: (was: 0.1-incubating)
0.2-incubating
> Semantics of DataStore.delete*
> ------------------------------
>
> Key: GORA-12
> URL: https://issues.apache.org/jira/browse/GORA-12
> Project: Gora
> Issue Type: Bug
> Components: storage
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Fix For: 0.2-incubating
>
> Attachments: GORA-12.patch
>
>
> Behavior of delete* calls in DataStore is insufficiently defined. Some unit tests in DataStoreUtil seem to indicate that after a successful call to delete the subsequent queries should not return deleted items. Other tests indicate that an additional DataStore.flush() call is needed.
> If we could rely on the latter assumption this would allow for some important optimizations in the implementations of DataStore - bulk updates that are visible only after an update transaction is finished are usually much less expensive to perform than equivalent multiple item by item transactions.
> Therefore I propose to strengthen the meaning of delete* calls, so that their effects are guaranteed to be visible to get/execute ONLY after a subsequent flush() call.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira