GreenfishK opened a new issue, #1744: URL: https://github.com/apache/jena/issues/1744
### Version 4.3.2 ### What happened? I evaluated JenaTDB2 4.3.2 with a SPARQL-star [dataset](https://zenodo.org/record/7603263/files/bearc_alldata.TB_star_hierarchical.ttl?download=1) with 9.411.041 triples (4.9 GB). I loaded the dataset with the tdb2 loader as on-disk storage. Then I tried a set of rather complex rdf-star queries only to find that none of them was able to finish. I went on to pin down the issue and tried a very simple double-nested SPARQL-star query: ``` select * { <<<<?s ?p ?o>> ?a ?b >> ?x ?y. } ``` However, even this query could not finish. ``` 15:47:31 INFO Server :: Memory: 4.0 GiB 15:47:31 INFO Server :: Java: 17.0.5 15:47:31 INFO Server :: OS: Linux 5.15.0-58-generic amd64 15:47:31 INFO Server :: PID: 106127 15:47:31 INFO Server :: Started 2023/02/03 15:47:31 CET on port 3030 15:47:52 INFO Fuseki :: [5] POST http://localhost:3030/bearc_tb_sr_rs/sparql 15:47:52 INFO Fuseki :: [5] Query = select * { <<<<?s ?p ?o>> ?a ?b >> ?x ?y. } ``` The memory didn't seek to be the problem. I tried the same set of queries on GraphDB and they all needed only a few seconds. Is it possible that Jena generally performs poorly with SPARQL-star and even worse if there are multiple nesting levels? ### Relevant output and stacktrace _No response_ ### Are you interested in making a pull request? None -- 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]
