clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür <>
Subject Concurrency issue with SingleTdbTcProvider
Date Thu, 24 Oct 2013 16:47:27 GMT

I've jut created CLEREZZA-833. The problem is that nothing ensure readlocks
on accessing the set returned by:

    public Set<UriRef> listMGraphs() {
        return new UriRefSet( graphNameIndex, Symbols.MGraph );

The straight forward solution would be to copy the Set to a HashSet. But
I'm not sure how much this defeats the purpose of the
ScalableSingleTdbTcProvider approach.

Another issue that just occured are the (non M) Graphs. Given that the lock
is on the dataset one should also lock when iterating over the triples of a
graph. But as the API doesn't foresee TripleCollections with shared lock
there's no support for this.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message