Aklakan commented on issue #1557: URL: https://github.com/apache/jena/issues/1557#issuecomment-1264595049
* Yes, the data is in TDB * As you said, if there are 2+ FROM clauses a general distinct is made loading everything into in memory. Otherwise I suspect that the reason is the overhead of materializing the NodeIds into Nodes. > can be addressed by pushing down the work into TDB Yes, core of this issue and the PR are about having a general path for pushing the raw FROM clauses and the raw dataset configured in the assembler from Fuseki down to ARQ. I don't think this has to be TDB specific (e.g. a servlet specifically for TDB). With the current interfaces, the options for doing so seem to be reasonably limited to dataset, query or context. And I agree with your argument that components beneath Fuseki should receive a dataset that per-se only exposes the right amount quads w.r.t. to the protocol and security, as this makes it harder for other components/plugins to accidentally leak information. The remaining option is to also put the projected dataset into the context just like the named graph and default graphs. But I think it makes sense to have DynamicDataset as the central point for accessing this information (in the PR I added getters for them). > This isn't easy Yes, but - as said - I think the first step would be having an easy path from Fuseki to ARQ. > requirements that Vilnis Termanis Which requirements? It seems you forgot to post a link. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
