You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2019/01/04 21:41:01 UTC
[jira] [Assigned] (JENA-1656) Make DatasetGraphMonitor
transaction-aware
[ https://issues.apache.org/jira/browse/JENA-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne reassigned JENA-1656:
-----------------------------------
Assignee: Andy Seaborne
> Make DatasetGraphMonitor transaction-aware
> ------------------------------------------
>
> Key: JENA-1656
> URL: https://issues.apache.org/jira/browse/JENA-1656
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 3.10.0
> Reporter: Pip Cet
> Assignee: Andy Seaborne
> Priority: Minor
>
> In order to implement continuously-updated query result streams, I used a DatasetGraphMonitor to monitor when the relevant part of the dataset graph changed in order to re-run the query. However, there was a race condition because DatasetGraphMonitor informs its monitor of uncommitted changes; the query would be repeated too soon, meaning the changes would be missed.
> Adding the commit() method to the DatasetChanges interface and using it seems to avoid this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)