Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Andy Seaborne



On 25/11/17 23:05, Laura Morales wrote:

With the new snapshot most problems seems to be fixed. However I still get "WARN 
ModTDBDataset :: Unexpected: Not a TDB2 dataset for type DatasetTDB2" which I don't 
understand if it's OK or an error or a bug.


Are you sure you are running the latest? (tdb2.tdbloader is in
"apache-jena" zip file)

It works for me.


Yes, 3.6.
Then there has to be something wrong with the config file here 
https://jena.apache.org/documentation/tdb2/tdb2_fuseki.html (first listing).
I get the WARN when using --tdb, but I do not get it if I use --loc


Because it's assembler related.  --loc does not use an assembler.

(Fix just pushed to the master branch)





Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Laura Morales
> > With the new snapshot most problems seems to be fixed. However I still get 
> > "WARN ModTDBDataset :: Unexpected: Not a TDB2 dataset for type DatasetTDB2" 
> > which I don't understand if it's OK or an error or a bug.
> 
> Are you sure you are running the latest? (tdb2.tdbloader is in
> "apache-jena" zip file)
> 
> It works for me.

Yes, 3.6.
Then there has to be something wrong with the config file here 
https://jena.apache.org/documentation/tdb2/tdb2_fuseki.html (first listing).
I get the WARN when using --tdb, but I do not get it if I use --loc


Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Andy Seaborne

OK - I see what you are doing now.

The warning is harmless and I'll remove it.

(BTW --tdb and --desc are synomyms.  You only need one - the last one is 
the value actually used.)


Andy

On 25/11/17 22:17, Andy Seaborne wrote:



On 25/11/17 21:53, Laura Morales wrote:

Please could you try a development version? (which works for me).


With the new snapshot most problems seems to be fixed. However I still 
get "WARN  ModTDBDataset    :: Unexpected: Not a TDB2 dataset for 
type DatasetTDB2" which I don't understand if it's OK or an error or a 
bug.


Are you sure you are running the latest? (tdb2.tdbloader is in 
"apache-jena" zip file)


It works for me.

  tdb2.tdbloader --version
==>
Jena:   VERSION: 3.6.0-SNAPSHOT

     Andy


Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Andy Seaborne



On 25/11/17 21:53, Laura Morales wrote:

Please could you try a development version? (which works for me).


With the new snapshot most problems seems to be fixed. However I still get "WARN  
ModTDBDataset:: Unexpected: Not a TDB2 dataset for type DatasetTDB2" which I 
don't understand if it's OK or an error or a bug.


Are you sure you are running the latest? (tdb2.tdbloader is in 
"apache-jena" zip file)


It works for me.

 tdb2.tdbloader --version
==>
Jena:   VERSION: 3.6.0-SNAPSHOT

Andy


Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Laura Morales
> Please could you try a development version? (which works for me).

With the new snapshot most problems seems to be fixed. However I still get 
"WARN  ModTDBDataset:: Unexpected: Not a TDB2 dataset for type 
DatasetTDB2" which I don't understand if it's OK or an error or a bug.
I still get a very low number of triples loaded per second, around 30K. How can 
I control this value to increase the number of loaded triples?


Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Andy Seaborne



On 25/11/17 18:57, Laura Morales wrote:

https://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-fuseki/3.6.0-SNAPSHOT/


What's the difference between the files in "apache-jena-fuseki" and "jena-fuseki", as well as 
"apache-jena" and "jena"?



We use "apache-jena*" for the main delivery binaries.

"apache-jena-libs"   - maven artifact for the main Jena jars
"apache-jena"  - the binary distribution of Jena libraries
"apache-jena-fuseki" - the binary distribution of Fuseki
"jena-fuseki"- the intermediate parent POM for Fuseki1
"jena"   - the top POM and, (3.6.0-dev) the project parent

Andy


Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Laura Morales
> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-fuseki/3.6.0-SNAPSHOT/

What's the difference between the files in "apache-jena-fuseki" and 
"jena-fuseki", as well as "apache-jena" and "jena"?


Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Andy Seaborne



On 25/11/17 18:17, Laura Morales wrote:

Please could you try a development version? (which works for me).


Downloading now. I hope I can compile it :)
If the bug is still there, I'll report back.


You don't need to - the project builds development versions for testing 
on a daily basis. These are not releases and have not been approved by 
the PMC.


https://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-fuseki/3.6.0-SNAPSHOT/

They are dated and number so pick the latest (which is at the end)

Andy


Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Laura Morales
> Please could you try a development version? (which works for me).

Downloading now. I hope I can compile it :)
If the bug is still there, I'll report back.


Re: Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Andy Seaborne

This is the same issue as the UI upload bug.

Please could you try a development version? (which works for me).

Andy

On 25/11/17 14:39, Laura Morales wrote:

With the older Fuseki release, when I opened "query" UI at localhost:3030, the "SPARQL 
endpoint" was automatically filled with the dataset query URL 
"http://localhost:3030/ds/query;. With the new release, it looks like this is no longer the case 
(the field is empty). I don't know if it's a bug or a feature, but it's kinda handy to have it set by 
default. Even better would be a drop-down box that allows to select more URLs for the dataset (query, update, 
...).





Fuseki UI missing "SPARQL endpoint"

2017-11-25 Thread Laura Morales
With the older Fuseki release, when I opened "query" UI at localhost:3030, the 
"SPARQL endpoint" was automatically filled with the dataset query URL 
"http://localhost:3030/ds/query;. With the new release, it looks like this is 
no longer the case (the field is empty). I don't know if it's a bug or a 
feature, but it's kinda handy to have it set by default. Even better would be a 
drop-down box that allows to select more URLs for the dataset (query, update, 
...).