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

Support Multiple Datasets #43

Open
no-reply opened this issue Feb 5, 2017 · 6 comments
Open

Support Multiple Datasets #43

no-reply opened this issue Feb 5, 2017 · 6 comments
Assignees

Comments

@no-reply
Copy link
Member

no-reply commented Feb 5, 2017

Allow multiple datasets in the cache service. The use case I have in mind for this is hosting multiple "authorities" in a single cache service.

Datasets are defined by the LD Fragments spec. We implement it in the Dataset model.

We should be able to introduce new datasets to act as additional subject cache endpoints. Ideally, it would be possible to put datasets in named graphs on a shared backend, or put them in separate backends.

@no-reply
Copy link
Member Author

no-reply commented Feb 9, 2017

Started work on this.

@no-reply
Copy link
Member Author

So, this is the point where I think I need to rework the config and/or the routes. I'm working on the most backward compatible ways to do this, but expecting this to require breaking changes. More info to come.

cc: @scande3 @elrayle

@no-reply
Copy link
Member Author

Initial work on this is here: https://github.com/ActiveTriples/linked-data-fragments/tree/feature/multi-dataset

I'm more confident that routing shouldn't be a compatibility issue, at this point; or if it is, it will be very minor. Config is still likely a problem.

@no-reply
Copy link
Member Author

https://github.com/ActiveTriples/linked-data-fragments/tree/feature/multi-dataset is updated with the latest work. A few PRs have been submitted representing some of that progress.

@no-reply
Copy link
Member Author

https://github.com/ActiveTriples/linked-data-fragments/tree/feature/multi-dataset is a finished branch with this feature. Two things need to happen in order for this to reach PR:

  • Reduce the VCR footprint.
    • Some of this should be manageable by using named cassettes; some of it may require refactoring.
  • Get the Blazegraph & Marmotta backends passing the backend shared examples.
    • These didn't pass the relatively simple examples merged previously, and the interface has drifted a bit out from under them. I'll do the Marmotta work in the next week-ish; blazegraph may take slightly longer.

@hackartisan
Copy link

@no-reply Is Marmotta work referenced in this last comment still outstanding? I assume the blazegraph work is.

Is it obvious what this work is by running the tests on the branch?

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