[
https://issues.apache.org/jira/browse/JENA-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494966#comment-17494966
]
Andy Seaborne commented on JENA-2282:
-------------------------------------
[~Car]
bq. Is current config - the dataset & endpoints specification in RDF - already
stored in a separate dataset or is it just read from RDF files as needed?
The state is in files. Having a system dataset didn't work out too well - it
gets out of step with the configuration files that the user edits. So the
config files are primary and read into the server.
Fuseki has admin operations that return the current stat as JSON. Endpoint
`/$/datasets`.
In a design let's be clear what is Fuseki-specific and what is going to work
for any endpoint. i..e try to introspect the server, and also allow the user to
type in an endpoint as well.
> Fuseki2 Query Store
> -------------------
>
> Key: JENA-2282
> URL: https://issues.apache.org/jira/browse/JENA-2282
> Project: Apache Jena
> Issue Type: Wish
> Components: Fuseki UI
> Affects Versions: Jena 4.4.0
> Reporter: Nicholas
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Many triplestore applications have a way to store SPARQL queries. These sorts
> of application parts are really useful: you can keep coming back to useful
> queries. If the queries can be named, then you can build up a query library.
> Not hard to make and super useful. Unless there is already an extension for
> this or plans for such, I'm happy to (have my staff) give this a go!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
