-
Notifications
You must be signed in to change notification settings - Fork 654
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
GH-2462: Fuseki reload configuration #2464
Conversation
603a9fe
to
34be973
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code is looking good! Had a quick go-through and found nothing that seemed wrong.
Any plans to expose it in the UI too, @afs? Like the backup/delete actions, in the management part of the UI? Or will it be only available if the user or admin prepares the request and runs it directly from command-line or some other HTTP client?
Is this available in |
And can this feature be used to add new datasets? |
This discussion is showing that this is a big area. This PR isn't as grand as that. That would be a reason to split the UI in two - admin and workbench. But again we can have big plans and we need tio have a way to creep up on them. |
This PR is open and not finished. The commit log for the codebase shows what's available.
Yes - but not all types of datasets can be guaranted. Assemblers are too general. |
bc0c016
to
bd56d65
Compare
… as InitFusekiMain
GitHub issue resolved #2462
Pull request Description: Provide reload of the config.ttl with zero interruption of service.
The logging support code changes better isolate the logging implementation specific functions.
By submitting this pull request, I acknowledge that I am making a contribution to the Apache Software Foundation under the terms and conditions of the Contributor's Agreement.