Mailing-List: contact gora-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: gora-dev@incubator.apache.org
Message-ID: <20214694.31831288969487471.JavaMail.jira@thor>
Date: Fri, 5 Nov 2010 11:04:47 -0400 (EDT)
From: "Andrzej Bialecki  (JIRA)" <jira@apache.org>
To: gora-dev@incubator.apache.org
Subject: [jira] Commented: (GORA-12) Semantics of DataStore.delete*
In-Reply-To: <28516791.31591288969003559.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrzej Bialecki  commented on GORA-12:
---------------------------------------

Actually, the semantics of put() should be tightened the same way, too.

> 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 
>
> 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.
-
You can reply to this email to add a comment to the issue online.