You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/07/01 07:06:45 UTC
[jira] [Commented] (GORA-12) Semantics of DataStore.delete*
[ https://issues.apache.org/jira/browse/GORA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696521#comment-13696521 ]
Hudson commented on GORA-12:
----------------------------
Integrated in goraOracle #6 (See [https://builds.apache.org/job/goraOracle/6/])
Apply patch for GORA-12: Semantics of DataStore.delete* contributed by Andrzej Bialecki. (Revision 8cda8a401d28a02338fab466f8641976c9ea5e0f)
Apply patch for GORA-12: Semantics of DataStore.delete* contributed by Andrzej Bialecki. (Revision 18d2fc2cce689f2ca3af70dd7a43959121ac4413)
GORA-120 Dirty fields are not correctly applied after serialization and map clearance (Revision 9f6611e931ae122f69c5aee5aac95e72f6bf778d)
commit to address GORA-123 & update to CHANGES.txt (Revision 4572936a4e76a8537e6e725bd09224310f921f74)
GORA-129 redundant conf field in HBaseStore (Revision 838dbb14bb82aada29d247b1557fef64f9eefc6b)
GORA-127 Result objects are not closed properly from GoraRecordReader (Revision bf010f26487edbfdfd79588df01fe5c9458ca40b)
trivial commit to address GORA-122 and update to CHANGES.txt (Revision 6c1cf81074f71979dd4dbf022c997bb1df99ddfd)
GORA-125 Clean up logging libraries (Revision 8faaf51de5a59c0ef054b127f726f1102bb14491)
GORA-125 Clean up logging libraries v2 (Revision 16accd4425801e350fdfa30876c1f64cc2888756)
reverse commit to r1373630 as GORA-125 breaks trunk (Revision d39962e57bd4644de8b1b04625c8dc0c68c5d8aa)
Result = FAILURE
mattmann :
Files :
* gora-core/src/main/java/org/apache/gora/store/DataStore.java
* gora-core/src/test/java/org/apache/gora/store/DataStoreTestUtil.java
mattmann :
Files :
* CHANGES.txt
ferdy :
Files :
* gora-core/src/main/java/org/apache/gora/persistency/StatefulMap.java
* CHANGES.txt
* gora-core/src/main/java/org/apache/gora/persistency/impl/PersistentBase.java
* gora-core/src/main/java/org/apache/gora/persistency/StatefulHashMap.java
* gora-core/src/main/java/org/apache/gora/avro/PersistentDatumReader.java
lewismc :
Files :
* gora-tutorial/pom.xml
* CHANGES.txt
* gora-cassandra/pom.xml
* gora-sql/pom.xml
* sources-dist/pom.xml
* gora-core/pom.xml
* gora-hbase/pom.xml
* gora-accumulo/pom.xml
ferdy :
Files :
* CHANGES.txt
* gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java
enis :
Files :
* CHANGES.txt
* gora-core/src/main/java/org/apache/gora/mapreduce/GoraRecordReader.java
lewismc :
Files :
* CHANGES.txt
lewismc :
Files :
* gora-tutorial/pom.xml
* gora-cassandra/pom.xml
* pom.xml
* gora-core/pom.xml
* gora-hbase/pom.xml
* CHANGES.txt
* gora-sql/pom.xml
lewismc :
Files :
* gora-tutorial/pom.xml
* gora-sql/pom.xml
* gora-hbase/pom.xml
* gora-accumulo/pom.xml
* gora-core/pom.xml
* pom.xml
* gora-cassandra/pom.xml
lewismc :
Files :
* CHANGES.txt
* gora-core/pom.xml
* gora-cassandra/pom.xml
* gora-accumulo/pom.xml
* gora-tutorial/pom.xml
* gora-sql/pom.xml
* gora-hbase/pom.xml
* pom.xml
> Semantics of DataStore.delete*
> ------------------------------
>
> Key: GORA-12
> URL: https://issues.apache.org/jira/browse/GORA-12
> Project: Apache Gora
> Issue Type: Bug
> Components: storage
> Reporter: Andrzej Bialecki
> Assignee: Chris A. Mattmann
> Fix For: 0.2
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira