-
Notifications
You must be signed in to change notification settings - Fork 659
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
Cancellable spatial property functions #2930
Labels
enhancement
Incrementally add new feature
Comments
Aklakan
pushed a commit
to AKSW/jena
that referenced
this issue
Jan 8, 2025
…ctions by creating iterators lazily.
4 tasks
Aklakan
pushed a commit
to AKSW/jena
that referenced
this issue
Jan 8, 2025
…ctions by creating iterators lazily.
Aklakan
pushed a commit
to AKSW/jena
that referenced
this issue
Jan 8, 2025
…ctions by creating iterators lazily.
Aklakan
pushed a commit
to AKSW/jena
that referenced
this issue
Jan 8, 2025
…ctions by creating iterators lazily.
Aklakan
pushed a commit
to AKSW/jena
that referenced
this issue
Feb 6, 2025
…ctions by creating iterators lazily.
Aklakan
pushed a commit
to AKSW/jena
that referenced
this issue
Feb 6, 2025
…ctions by creating iterators lazily.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
5.3.0-SNAPSHOT
Feature
In
jena-geosparql
, many (if not all) property functions do not respect query cancellation.For example, accidentally executing a query such as below creates a cross product of all geometries in the store which may run for days, weeks or longer, regardless of the query timeout setting.
The proposed solution is to improve the implementations in
jena-geosparql
to make more use of theQueryIter
machinery which provides the cancellation system.Are you interested in contributing a solution yourself?
Yes
The text was updated successfully, but these errors were encountered: