-
Notifications
You must be signed in to change notification settings - Fork 16
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
Handle named graphs #43
Comments
To clarify, I'm not looking at the sublevel approach yet because I'm interested in provenance cross graph queries and graph per resource or graph per aspect patterns |
@jmatsushita I have not so much time to dig into this, so I would leave it to you. As a general rule, start simple and then optimize. |
Thanks for the input. I'll document my progress here. |
@jmatsushita @mcollina we've just published the first proof of concept of node-quadstore, an attempt at using LevelGraph's LevelDB-based storage approach with a quad-oriented indexing strategy to implement a graph database with native support for cross-graph queries. It still uses 6 indexes. As we do not want to re-invent the wheel, assuming our solution works out we'd be more than happy to contribute to LevelGraph in any way you might deem fit. |
feel free to send a PR to LevelGraph if you want to! :) |
Thinking through @jmatsushita's work in #54--which you can demo in a fork of the playground--it's not possible to keep the provenance of a single triple if it exists (or arrives via) two different named graphs. Try the example in that playground fork, and change 73 to 74...there will be a triple left behind so it's clear that 73 was inserted, but you'd not be able to re-compute the If the Thoughts? 💭 |
Hi @BigBlueHat thanks for your continued interest! Indeed this is a bug, or a design shortcoming of my fork, in the sense that it cannot work with There would need to be a change (or an option) in levelgraph in order for quads to be indexed. There was some chat about this on the levelgraph issue tracker levelgraph/levelgraph#43 It seems that As @elf-pavlik suggested in levelgraph/levelgraph#43 (and if quad indexing is added into Given all of this recent good work I would be inclined to watch that issue levelgraph/levelgraph#43 for possible addition of quad indexing into |
@jmatsushita @BigBlueHat I think a |
I'm definitely down for more collaboration! 😁 I'm already lurking in all the places. 😉 Exciting times ahead! |
With the recent version update, it is now possible to submit JSON-LD docs which includes an
@graph
key. However, named graphs are not handled yet. (More precisely, if there is a top level@id
then the@graph
value is just ignored).Given the discussion on levelgraph/levelgraph#43 I'm thinking of first implementing this using a
graph
triple property forput
, and a slowfilter
JS-land approach forget
.The performance penalty will be big on anything that tries to use named graphs but it's probably good to start here before doing anything more involved. Things will probably take shape as I implement but does this make sense @mcollina ?
The text was updated successfully, but these errors were encountered: