-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Feature request] Federated ASK/EXISTS queries sent to remote server #147
Comments
HiYou may try this :Ask { service <uri> { select * where { s p o } limit 1 } }RegardsOlivier
-------- Message d'origine --------De : Pierre Maillot ***@***.***> Date : 11/10/2023 11:37 (GMT+01:00) À : Wimmics/corese ***@***.***> Cc : Subscribed ***@***.***> Objet : [Wimmics/corese] Federated ASK/EXISTS queries sent to remote server (Issue #147)
Is your feature request related to a problem? Please describe.
When I send a federated ASK query such as ASK { SERVICE { ?s ?p ?o } }, the Corese server sends the following query to the server:
select * where { ?s ?p ?o . } limit 1000
Describe the solution you'd like
I would like to know if there is a setting to put the limit of the sent query to 1 or if federated ASK queries could be sent to the remote server as ASK sub-queries instead of a SELECT one.
Describe alternatives you've considered
I can use the service extension feature, but it requires doing a lot of parsing/rewriting work on every query to automate the querying.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When I send a federated ASK query such as
ASK { SERVICE { ?s ?p ?o } }
, the Corese server sends the following query to the server:Describe the solution you'd like
I would like to know if there is a setting to put the limit of the sent query to 1 or if federated ASK queries could be sent to the remote server as ASK sub-queries instead of a SELECT one.
Describe alternatives you've considered
I can use the service extension feature, but it requires doing a lot of parsing/rewriting work on every query to automate the querying.
The text was updated successfully, but these errors were encountered: