Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jena.query.ResultSet.hasNext takes a long time in OntologyModelService.expandConcepts #43

Closed
taojing2002 opened this issue Dec 16, 2022 · 1 comment
Assignees
Milestone

Comments

@taojing2002
Copy link
Collaborator

In the dev cluster the jena.query.ResultSet.hasNext method takes about four seconds to finish. However, the second time to insert the same document, it almost takes 0 second to finish it. Somehow, there is a cache system there. The code looks like:

        Query query = QueryFactory.create(q);
        QueryExecution qexec = QueryExecutionFactory.create(query, ontModel);
        ResultSet results = qexec.execSelect();
        String name = field.getName();
        Set<String> values = new HashSet<String>();
         // results.hasNext() takes a long time
        while (results.hasNext()) {
          QuerySolution solution = results.next();
@artntek
Copy link
Collaborator

artntek commented Feb 6, 2024

added to #34 and closed

@artntek artntek closed this as completed Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants