Changes between Initial Version and Version 1 of ApertureRdfContainerProblems

Timestamp:

02/01/06 10:51:42 (20 years ago)

Author:

sauermann

Comment:

--

ApertureRdfContainerProblems

@@ +1 @@
+= Problems with RDFContainer =
+
+= Solution: own in-mem sail? =
+
+Leo: How about making our own in-memory sail, that does not support transactions, context, etc.
+It is just needed to ship RDF from the DataAccessor to the CrawlerHandler.
+The CrawlerHandler then has to read it again and copy all the triples to another repository
+
+Then, the default RDFContainer (in-mem sesame) must not contain "context" anymore. Context is only used when creating the RDFContainer via the factory methods of CrawlerHandler.
+
+ * pro: for 80% of the use cases, it gets simpler (extracting data to things like gnowsis or Lucene)
+ * pro: for the 20% of the use cases where the DataAccessor directly streams into the RDFContainer (=the sesame database), the CrawlerHandler can provide a context-aware RDFContainer.
+ * con: we have to write it.
+
+=  Problem autocommit =
+
+When you use a SesameRDFContainer, its Repository typically has its 
+auto-commit mode switched off for performance reasons. However, this 
+breaks the contract of RDFContainer's API. The reason is that statements 
+in the repository are not visible until a commit is performed. So when 
+you do a put() for a certain property and you later do a put() for the 
+same property with a different value, you expect that the latter put() 
+overwrites the former value. However, when the repository hasn't been 
+committed yet, replaceInternal won't see the first value. Likewise, the 
+get methods will not return a value for that property. When you finally 
+commit, you end up with both values being stored, leading to a 
+MultipleValuesException upon retrieval.
+
+My example classes are already crowded with commit's to make sure 
+certain put and get methods work correctly. There is something to say 
+for this as these classes also provide the CrawlerHandler implementation 
+that manage the repository. However, I now had to add Sesame-specific 
+code in WebCrawler as it depends on the overwriting capability of the 
+put method.
+
+This is a problem with the SesameRDFContainer but I can imagine that 
+other implementations working with persistence storage facilities will 
+have similar issues.
+
+Although I still like the simplicity of the RDFContainer API, this is 
+another item on the list of problems I've had with it. Does anyone see a 
+simple solution for this? Other that adding a commit() method to 
+RDFContainer or using the Repository's auto-commit mode (hurts 
+performance badly)?
+