[ 
https://issues.apache.org/jira/browse/JENA-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465399#comment-17465399
 ] 

Andy Seaborne commented on JENA-2228:
-------------------------------------

I do not understand your question nor what you are trying to do. Please explain 
the context.

bq. it’s getter methods are on triple/quad level, which is what I am looking 
for. 

You can call those methods - and the find method if you want.

Fuseki has nothing to do with this.

bq. I can’t find any other similar getter methods

Evaluation goes through general code working on triples or quads, through 
PatternMatchTDB2 to SolverRX to the NodeTupleTable.


> 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)

Reply via email to