[
https://issues.apache.org/jira/browse/JENA-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464615#comment-17464615
]
Martin Pekár commented on JENA-2228:
------------------------------------
So queries are entirely handled in SolverLib?
I can see at some point I reach StageMatchTuple, which finally calls
NodeTupleTable.find(NodeId... ids). But this does of course use NodeTable to
get the NodeID.
Concretely, I thought NodeTupleTable.find() was used with Nodes as parameters,
then that uses TupleTable that identifies the index order and choose the
correct TupleIndex to query the B+ tree. Is this wrong? At the moment, it seems
like NodeTable is used for everything.
> Does Fuseki2 use TDB indexes or indexes for in-memory store?
> ------------------------------------------------------------
>
> Key: JENA-2228
> URL: https://issues.apache.org/jira/browse/JENA-2228
> Project: Apache Jena
> Issue Type: Question
> Components: Fuseki, TDB
> Affects Versions: Jena 3.17.0
> Environment: I am running the jena-fuseki-server-3.17.0.jar file from
> jena-fuseki2/jena-fuseki-server/target/ as follows
> {code:java}
> java -Xmx500g -jar fuseki-jenaclone.jar --tdb2 --loc=db/jena
> --timeout=1000000 /jena &{code}
> Reporter: Martin Pekár
> Priority: Major
> Fix For: Jena 3.17.0
>
>
> Based on logging messages inserted into various places in the indexes in the
> TDB module (NodeTupleTableConcrete, TupleIndexBase, NodeTableNative,
> BPlusTree), I can see that the B+ tree is only used once per query. I have
> inserted logging messages for every finding method to see which classes are
> used when querying. I would expect to the the B+ tree be used several times
> per query.
>
> I use the error logging level, and I inserted logging in the class
> constructors to make sure logging worked. I see construction of all the index
> classes.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
