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

Use alternative SPARQL parser #403

Open
rubensworks opened this issue Feb 22, 2019 · 3 comments
Open

Use alternative SPARQL parser #403

rubensworks opened this issue Feb 22, 2019 · 3 comments

Comments

@rubensworks
Copy link
Member

rubensworks commented Feb 22, 2019

Issue type:

  • ➕ Feature request

Description:

SPARQL.js is currently being used for parsing SPARQL queries. This library works great, but is unfortunately quite big when webpacked. For this reason (and also lack of modularity), we may want to look into implementing a custom parser.

Edit: included from @jeswr's issue #1018:

There are some use-cases in which it would be beneficial to process SPARQL queries in a stream-like manner. For instance an INSERT DATA query containing a large number of triples to insert would be better processed in real-time rather than needing to buffer all the changes in memory before making the update.

One way of achieving this would be to create a new algebra library where property access on the algebra return promises that resolve when processing has completed, and anything that was an array in sparqlalgebrajs becomes an AsyncIterable. Consequently it could potentially be worth looking into this when work on supporting SPARQL 1.2 starts.

@joachimvh
Copy link
Member

This is actually a sparqlalgebra.js issue since that's the only thing that makes use of it I think?

@rubensworks
Copy link
Member Author

Indeed, kind of. But it can be developed independently though. Also, if this new parser would output parsed queries in the same format, then sparqlalgebra.js could simply plug in this new parser.

@rubensworks
Copy link
Member Author

Related to #386

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development
  
To do (prio:high)
Development

No branches or pull requests

2 participants