[
https://issues.apache.org/jira/browse/CLEREZZA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030497#comment-13030497
]
Alexander Schäfer commented on CLEREZZA-219:
--------------------------------------------
The GraphListener would benefit from transactions, as changes could be combined
and presented in the List<GraphEvent> parameter. Allowing code to know if
changes are grouped together.
For the cris platform, without grouping of changes, the system is repeatedly
working with the same data, as it does not know if the incoming changes will
continue or not. The current work around is grouping over time (100ms e.g.) and
merging any events occurring in that time frame.
If it is possible to detect a writelock-release? This would allow to detect the
boundaries of change-groups. However an explicit "commit" would still be a
preferred.
> in rdf.core: Introduce atomicity and isolation for graph manipulation
> ---------------------------------------------------------------------
>
> Key: CLEREZZA-219
> URL: https://issues.apache.org/jira/browse/CLEREZZA-219
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Manuel Innerhofer
>
> It should be possible to modify a graph and commit all changes to the graph
> at the same time or dismiss the modifications.
> Use Case:
> A POST request with form data is sent to the clerezza platform. The form-data
> of the request contains the contact information of a user. The clerezza
> platform starts to fill the data into the content graph. At one point the
> submitted email address is check for validity and throws an
> IlleagalFormatException. It is desirable that the information already added
> to the graph is not commited and can be dismissed by the server code.
> Furthermore the already added data should have never been visible to other
> processes accessing the content graph. Only when a explicit "commit" command
> was executed should the modifications be visible to other processes only
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
