incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hasan Hasan <>
Subject Re: A question about Jena Sparql Engine and the TDB Store
Date Thu, 17 Mar 2011 15:37:11 GMT
Hi Olivier

Indeed, this "fastlane" support in executing sparql queries, where the
underlying triple store is jena, is something that still on our to do list.
However, if you would like to contribute and provide a patch, that would be
really appreciated.
Not sure about the effort needed to get the native TDB Dataset encapsulated
in the TripleCollection though. There may be some other wrappers in-between
which are inserted to provide security and locking mechanisms


On Thu, Mar 17, 2011 at 11:50 AM, Olivier Grisel <> wrote:

> Hi all,
> I am reading the source code of the Jena SPARQL / commons /  storage /
> tdb packages of clerezza and it seems that the Jena sparql engine is
> passed a generic Dataset implementation that wraps arbitrary clerezza
> triple collection, even though the TC implementation is based on a TDB
> implementation.
> I am afraid that this double wrapping / unwrapping mechanism will
> prevent ARQ to work efficiently at scale on large TDB triple stores.
> Is my reading correct? Would it be possible to refactor the API of
> either the JenaSparqlEngine to pass the native TDB dataset
> implementation to the sparql engine whenever it's based on Jena
> instead of always passing the generic Clerezza wrapper?
> Cheers,
> --
> Olivier

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