[
https://issues.apache.org/jira/browse/JENA-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wolfgang Fahl updated JENA-1964:
--------------------------------
Description:
Even if i selected "Trivial" as a priority from a newbie's perspective this
issue might be essential.
As outlined in
[https://stackoverflow.com/questions/63874908/fuseki-configuration/63878809#63878809]
i was
* initimated by the complexity of the configuration process via files
* did not dare to use the dataset creation via the webgui due to the size of
my triple files fearing a timeout would happen.
[https://stackoverflow.com/a/63878809/1497139] shows that the solution is
indeed quite simple and I'd love to see this process automated. So if fuseki
would get some kind of command line switch e.g. "–createConfig" so that
{code:java}
java -jar fuseki-server.jar --tdb2 --loc=../data /wikidata --createConfig{code}
would make sure there is a symbolic link in the run/databases/wikidata and a
configuration file in run/configuration/wikidata.ttl
this would be great. The whole process from tdb import to dataset creation
could be automated that way so that after the import of mulitple datasets the
fuseki server would be allowing access to all datasets immediately. User's
would not have to bother with the complexities of the configuration this way.
Changes to the configuration file layout would be done by the software
according to the needs of the current version upon creation.
was:
Even if i selected "Trivial" as a priority from a newbie's perspective this
issue might be essential.
As outlined in
[https://stackoverflow.com/questions/63874908/fuseki-configuration/63878809#63878809]
i was
* initimated by the complexity of the configuration process via files
* did not dare to use the dataset creation via the webgui due to the size of
my triple files fearing a timeout would happen.
[https://stackoverflow.com/a/63878809/1497139] shows that the solution is
indeed quite simple and I'd love to see this process automated. So if fuseki
would get some kind of command line switch e.g. "–createConfig" so that
```
java -jar fuseki-server.jar --tdb2 --loc=../data /wikidata --createConfig
```
would make sure there is a symbolic link in the run/databases/wikidata and a
configuration file in run/configuration/wikidata.ttl
this would be great. The whole process from tdb import to dataset creation
could be automated that way so that after the import of mulitple datasets the
fuseki server would be allowing access to all datasets immediately. User's
would not have to bother with the complexities of the configuration this way.
Changes to the configuration file layout would be done by the software
according to the needs of the current version upon creation.
> (Optionally) add configuration when starting Jena with --loc from commandline
> -----------------------------------------------------------------------------
>
> Key: JENA-1964
> URL: https://issues.apache.org/jira/browse/JENA-1964
> Project: Apache Jena
> Issue Type: New Feature
> Components: Fuseki
> Affects Versions: Jena 3.16.0
> Reporter: Wolfgang Fahl
> Priority: Trivial
>
> Even if i selected "Trivial" as a priority from a newbie's perspective this
> issue might be essential.
> As outlined in
> [https://stackoverflow.com/questions/63874908/fuseki-configuration/63878809#63878809]
> i was
> * initimated by the complexity of the configuration process via files
> * did not dare to use the dataset creation via the webgui due to the size of
> my triple files fearing a timeout would happen.
> [https://stackoverflow.com/a/63878809/1497139] shows that the solution is
> indeed quite simple and I'd love to see this process automated. So if fuseki
> would get some kind of command line switch e.g. "–createConfig" so that
>
> {code:java}
> java -jar fuseki-server.jar --tdb2 --loc=../data /wikidata
> --createConfig{code}
> would make sure there is a symbolic link in the run/databases/wikidata and a
> configuration file in run/configuration/wikidata.ttl
> this would be great. The whole process from tdb import to dataset creation
> could be automated that way so that after the import of mulitple datasets the
> fuseki server would be allowing access to all datasets immediately. User's
> would not have to bother with the complexities of the configuration this way.
> Changes to the configuration file layout would be done by the software
> according to the needs of the current version upon creation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
