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

Add support for additional query to always pull in fragments when source=="sparql" #76

Open
tdiepenbrock opened this issue Dec 11, 2020 · 0 comments
Assignees

Comments

@tdiepenbrock
Copy link
Contributor

Sparql queries frequently need to pull in fragments from managed ontology triples stored under the /triplestore/ directory in the database. The current implementation forces these triples to be excluded whenever a geospatial query is submitted in the request, which is almost almost always. The idea is to add an additional query field at the datasource level that would contain a query that would always be combined with the usual bounding query in a cts.orQuery():

let additionalOrQuery = datasource.additionalOrQuery != null ? datasource.additionalOrQuery : cts.falseQuery();
//datasource.additionalOrQuery is some query, possibly a cts.directoryQuery("/triplestore/", "infinity")

let finalBoundingQuery = cts.orQuery(boundingQuery, additionalOrQuery);
//...on with the rest of building the plan

@tdiepenbrock tdiepenbrock self-assigned this Dec 11, 2020
mfgumban referenced this issue Dec 17, 2020
adding support to always pull in fragments regardless of the bounding…
@rjrudin rjrudin added this to the 1.4.0 milestone Jan 3, 2023
rjrudin added a commit that referenced this issue Feb 8, 2023
Was verifying that #76 works, and noticed obvious duplication in how `const boundingQuery` was constructed, so extracted that into a new method.
rjrudin added a commit that referenced this issue Feb 8, 2023
Was verifying that #76 works, and noticed obvious duplication in how `const boundingQuery` was constructed, so extracted that into a new method.
@rjrudin rjrudin removed this from the 1.4.0 milestone Mar 20, 2023
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