You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@clerezza.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2014/01/18 15:07:19 UTC

[jira] [Resolved] (CLEREZZA-252) read-locks by sparql engine

     [ https://issues.apache.org/jira/browse/CLEREZZA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reto Bachmann-Gmür resolved CLEREZZA-252.
-----------------------------------------

    Resolution: Fixed
      Assignee: Reto Bachmann-Gmür

Locking in sparql engine. This allows for more optimizations than in TcManager, as an implementation might not need locks on all graphs during all the execution time.

> read-locks by sparql engine
> ---------------------------
>
>                 Key: CLEREZZA-252
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-252
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Reto Bachmann-Gmür
>            Assignee: Reto Bachmann-Gmür
>
> Currently its the responsability of the applications to lock the graphs against which they direct a query. The sparql query engine (engines or tcManager) should find against which MGraphs a query is targettted at and lock the respective MGraphs.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)