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

No notifications with the default graph (or in triple mode) #68

Open
m-hatter opened this issue Jun 18, 2021 · 2 comments
Open

No notifications with the default graph (or in triple mode) #68

m-hatter opened this issue Jun 18, 2021 · 2 comments

Comments

@m-hatter
Copy link

Describe the bug
There are no notifications when the subscription (and update) queries use the default graph (by not specifying any graph in queries).

To Reproduce
Steps to reproduce the behavior via the SEPA Playground:

  1. Add subscription:
SELECT ?o WHERE {
  <http://sepatest/testsubj> <http://sepatest/hasValue> ?o
}
  1. Issue query:
DELETE {
    <http://sepatest/testsubj> <http://sepatest/hasValue> ?o
} INSERT {
    <http://sepatest/testsubj> <http://sepatest/hasValue> "c"
} WHERE {
  OPTIONAL {
    <http://sepatest/testsubj> <http://sepatest/hasValue> ?o
}}
  1. There are no notifications in the Subscribe tab. However, the same query as was used to subscribe, returns the new value.

Expected behavior
I expect to see notification about new value of the subject in the Subscribe tab of the Playground.

System information(please complete the following information):

  • OS: [Windows 10]
  • Engine version [SEPA Broker Ver 0.9.11] (though the jar file i downloaded is named engine-0.9.12.jar)
  • SparqlEnpoint used [blazegraph 2.1.6-SNAPSHOT]

Additional context
Yes, the simple fix from my side would be to use some explicitly specified graph, however, it turns out to be impossible, because I am planning to use Blazegraph with inference enabled as the endpoint, however, Blazegraph doesn't support inference in quads mode, and it obviously doesn't support graphs in triples mode.

@relu91
Copy link
Contributor

relu91 commented Jun 25, 2021

Hi! thank you for using SEPA and posting such a great issue description. We were able to reproduce the bug and we are working on solving it. We'll keep you posted 👍🏻

lroffia added a commit that referenced this issue Jun 25, 2021
@lroffia
Copy link
Contributor

lroffia commented Jun 25, 2021

Dear @m-hatter thank you very much! We fixed the issue and pushed new version of dev branch. Please check it and let us know!

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

3 participants