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
