Hi If you are willing to work on this that would be great, for various personal reasons I am not able to act as a formal mentor for GSoC this year but others who are familiar with the update code (Stephen Allen) are acting as mentors this year.
Right now there is no experimental branch anymore because I deleted it as my early efforts was obsoleted by Stephen's streaming update changes that were merged in 2.10.0. Stephen may have some ideas on how best to implement this under the new model. The basic task itself is simple but there are a number of things to consider: - Cancellation for streaming vs non-streaming update engines - Leveraging existing query cancellation if an update is stuck in the query portion of a DELETE/INSERT - Interaction with transaction mechanisms -> cancellation should almost certainly render a transaction as un-committable and require a rollback I will be around on the list to answer questions and offer ideas but I won't be able to be a full mentor Rob On 4/16/13 8:43 PM, "Yigang Zhou" <[email protected]> wrote: >Dear Sir/Madam, > >I'd like to contribute to Jena in GSoC 2013 on the project of "SPARQL >Updates are not cancelable". Actually, I have successfully completed 3 >GSoC >projects directly related to Jena: > - GSoC 2009 [1]: I developed a Tupelo plug-in for NCSA using Jena, which >transfers arbitrary data into RDF triples by DFDL. > - GSoC 2010 [2]: I developed the semantic storage plug-in for DSpace, >which manages digital collections and their metadata in RDF triple store, >powered by Tupelo, Jena and Mulgara. > - GSoC 2012 [3]: I developed a Cytoscape plugin, which uses Jena to send >the SPARQL queries to Biological ontology endpoints and render the results >as Cytoscape graphs. >You can see that all of the projects are about Semantic Web, which I major >in as a PhD student. I have good knowledge of the semantic technologies >(e.g. RDF, OWL, SPARQL). I have strong Java coding capabilities, familiar >with design patterns, unit testing and git/svn/maven development >environment. Rich experience with Jena, I know its interfaces and their >usages. I've not looked into the insight of Jena before. But I'm quite >interested in getting involved in this summer. > >For the project of "SPARQL Updates are not cancelable", I'm now studying >the source code of Jena ARQ to figure out how cancellation works during >query execution [4]. It seems that Dr. Rob Vesse would be the potential >mentor. But I can't find his email address. Could you please cc him? He >mentioned in the JIRA [5] that there's a svn branch of >"Experimental/cancellable-updates" to experiment on this feature. Could >you >please tell me where it is? > >yours, >Yigang Zhou > >[1] http://www.ncsa.illinois.edu/News/09/0827Studentspursue.html >[2] >https://wiki.duraspace.org/display/GSOC/GSOC10+-+Storage+Service+Implement >ations+Based+on+Semantic+Content+Repository >[3] http://ceur-ws.org/Vol-952/paper_43.pdf >[4] https://issues.apache.org/jira/browse/JENA-29 >[5] https://issues.apache.org/jira/browse/JENA-382
