gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doğacan Güney (JIRA) <j...@apache.org>
Subject [jira] Commented: (GORA-12) Semantics of DataStore.delete*
Date Fri, 05 Nov 2010 17:37:45 GMT

    [ https://issues.apache.org/jira/browse/GORA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928696#action_12928696

Doğacan Güney commented on GORA-12:

Ah, OK, I should have probably taken a look at your patch before asking for more time :)

Still, I agree with you that a well-documented and a consistent data model is very important...
More important than having it more features (i.e I don't mind put not making data available
immediately for now as long as it is a consistent behavior)

> Semantics of DataStore.delete*
> ------------------------------
>                 Key: GORA-12
>                 URL: https://issues.apache.org/jira/browse/GORA-12
>             Project: Gora
>          Issue Type: Bug
>            Reporter: Andrzej Bialecki 
>            Assignee: Andrzej Bialecki 
>         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
> 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.
You can reply to this email to add a comment to the issue online.

View raw message