[jira] [Commented] (JENA-1004) Dynamic datasets inconsistently supported in Fuseki.
[
https://issues.apache.org/jira/browse/JENA-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14650493#comment-14650493
]
ASF subversion and git services commented on JENA-1004:
---
Commit b56d50f75df22e15a66effeb2692c4f8b6b10675 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=b56d50f ]
JENA-1004: Dynamic dataset processing for all requests.
Dynamic datasets inconsistently supported in Fuseki.
Key: JENA-1004
URL: https://issues.apache.org/jira/browse/JENA-1004
Project: Apache Jena
Issue Type: Bug
Components: Fuseki
Affects Versions: Fuseki 2.0.0
Reporter: Andy Seaborne
Dynamic datasets, where the dataset to query is constructed out of the graphs
of the underlying dataset behave differently for in-memory and TDB datasets.
[TDB supports them
natively|https://jena.apache.org/documentation/tdb/dynamic_datasets.html]
when {{FROM}}, {{FROM NAMED}} are used.
{{SPARQL_QueryDataset#decideDataset}} provides the feature for SPARQL
protocol ({{default-graph-uri=}}, {{named-graph-uri=}} externally to the
dataset.
Other datasets do not support the feature. Henc, in-memory dataset services
does not support it when {{FROM}}, {{FROM NAMED}} used but does when
{{default-graph-uri=}}, {{named-graph-uri=}} used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (JENA-1005) Move off Log4j v1.
Andy Seaborne created JENA-1005: --- Summary: Move off Log4j v1. Key: JENA-1005 URL: https://issues.apache.org/jira/browse/JENA-1005 Project: Apache Jena Issue Type: Improvement Reporter: Andy Seaborne Priority: Minor Log4J v1 is approaching end-of-life. Jena uses slf4j for logging from code. Jena depends on log4j for controlling output in tests and for the output in commands. This is in the log4j explicit control utilities. Choices include: * Log4jv2 log4j v2 does not support log4j.properties. * Use java.util.logging (JUL) in some or all of those places. Others? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JENA-868) Fuseki2: docker: Redirected ports lead to wrong URLs.
[ https://issues.apache.org/jira/browse/JENA-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-868: --- Assignee: (was: Andy Seaborne) Fuseki2: docker: Redirected ports lead to wrong URLs. - Key: JENA-868 URL: https://issues.apache.org/jira/browse/JENA-868 Project: Apache Jena Issue Type: Bug Components: Fuseki Affects Versions: Fuseki 2.0.0 Environment: Docker https://registry.hub.docker.com/u/stain/jena-fuseki/ Reporter: Stian Soiland-Reyes (old) Priority: Minor If I use docker and jena-fuseki exposing the port on something other than the one it is running at, e.g. with -p 3031:3030 - then in the browser at http://localhost:3031/ when I go to *Manage datasets* - *Create dataset* I simply get error because it is trying to POST to http://localhost:3030/datasets instead of http://localhost:3031/datasets. This could make it tricky to expose the Fuseki server through firewalls, web servers etc, as one has to change the Fuseki port to match the public port. All URIs should be relative and not hard-code the port. (and not the host!) This is using fuseki-server.jar, I have not checked what happens if I do the same through tomcat/WAR. The workaround is to always expose the same port - e.g. add the argument --port=3031 docker run -p 3031:3031 stain/jena-fuseki ./fuseki-server --port=3031 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JENA-868) Fuseki2: docker: Redirected ports lead to wrong URLs.
[ https://issues.apache.org/jira/browse/JENA-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-868: --- Fix Version/s: (was: Fuseki 2.3.0) Fuseki2: docker: Redirected ports lead to wrong URLs. - Key: JENA-868 URL: https://issues.apache.org/jira/browse/JENA-868 Project: Apache Jena Issue Type: Bug Components: Fuseki Affects Versions: Fuseki 2.0.0 Environment: Docker https://registry.hub.docker.com/u/stain/jena-fuseki/ Reporter: Stian Soiland-Reyes (old) Priority: Minor If I use docker and jena-fuseki exposing the port on something other than the one it is running at, e.g. with -p 3031:3030 - then in the browser at http://localhost:3031/ when I go to *Manage datasets* - *Create dataset* I simply get error because it is trying to POST to http://localhost:3030/datasets instead of http://localhost:3031/datasets. This could make it tricky to expose the Fuseki server through firewalls, web servers etc, as one has to change the Fuseki port to match the public port. All URIs should be relative and not hard-code the port. (and not the host!) This is using fuseki-server.jar, I have not checked what happens if I do the same through tomcat/WAR. The workaround is to always expose the same port - e.g. add the argument --port=3031 docker run -p 3031:3031 stain/jena-fuseki ./fuseki-server --port=3031 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JENA-971) QueryBuilder does not properly construct UNIONs
[ https://issues.apache.org/jira/browse/JENA-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-971: --- Fix Version/s: (was: Jena 3.0.0) (was: Jena 2.13.1) QueryBuilder does not properly construct UNIONs --- Key: JENA-971 URL: https://issues.apache.org/jira/browse/JENA-971 Project: Apache Jena Issue Type: Bug Components: Jena Affects Versions: Jena 2.13.1, Jena 3.0.0 Reporter: Claude Warren Assignee: Claude Warren The QueryBuilder method addUnion() always adds a new union to the query pattern. It should only add one if the last element in the query pattern is not a union. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (JENA-1004) Dynamic datasets inconsistently supported in Fuseki.
[
https://issues.apache.org/jira/browse/JENA-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1004.
-
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Fuseki 2.3.1
Dynamic datasets now implemented by Fuseki as part of request processing.
Dynamic datasets inconsistently supported in Fuseki.
Key: JENA-1004
URL: https://issues.apache.org/jira/browse/JENA-1004
Project: Apache Jena
Issue Type: Bug
Components: Fuseki
Affects Versions: Fuseki 2.0.0
Reporter: Andy Seaborne
Assignee: Andy Seaborne
Fix For: Fuseki 2.3.1
Dynamic datasets, where the dataset to query is constructed out of the graphs
of the underlying dataset behave differently for in-memory and TDB datasets.
[TDB supports them
natively|https://jena.apache.org/documentation/tdb/dynamic_datasets.html]
when {{FROM}}, {{FROM NAMED}} are used.
{{SPARQL_QueryDataset#decideDataset}} provides the feature for SPARQL
protocol ({{default-graph-uri=}}, {{named-graph-uri=}} externally to the
dataset.
Other datasets do not support the feature. Henc, in-memory dataset services
does not support it when {{FROM}}, {{FROM NAMED}} used but does when
{{default-graph-uri=}}, {{named-graph-uri=}} used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Fwd: Final Deliveries of GSoC Project (JENA-491)
Hi Qihong,
I re-checked the code you commited. Most of the hashCode issues for
arq.qparse that Andy pointed out are due to the incorrect
serialization of the Template. The code can only deal with the quads
with the same graph node, for which it may not always be the case in
practcial terms. Please make sure each example syntax file can pass
the checking process of arq.qparse.
It's August now. You'd better hurry up and make the project completed
on time in the remaining weeks.
Best regards,
Ying Jiang
On Thu, Jul 30, 2015 at 6:03 AM, Andy Seaborne a...@apache.org wrote:
Output of
* each examnple syntax file (the queries are nonsense in practcial terms!)
* running arq.qparse on the file
* notes on what seems to be going on
Andy
File: syntax-quad-construct-01.arq
PREFIX : http://example/
CONSTRUCT { GRAPH :g { :s :p :o } } WHERE {}
Output of qparse --file syntax-quad-construct-01.arq
PREFIX : http://example/
CONSTRUCT
{ GRAPH http://example/g {:s :p :o .}
}
WHERE
{ }
Issue:
Minor: formatting of http://example/g should be :g
File: syntax-quad-construct-02.arq
PREFIX : http://example/
CONSTRUCT { GRAPH ?g { ?s ?p ?o } } WHERE { ?s ?p ?o }
Output of qparse --file syntax-quad-construct-02.arq
PREFIX : http://example/
CONSTRUCT
{ GRAPH ?g {?s ?p ?o .}
}
WHERE
{ ?s ?p ?o }
OK
File: syntax-quad-construct-03.arq
PREFIX : http://example/
CONSTRUCT { :s :p :o } WHERE {}
Output of qparse --file syntax-quad-construct-03.arq
PREFIX : http://example/
CONSTRUCT
{ GRAPH urn:x-arq:DefaultGraphNode {:s :p :o .}
}
WHERE
{ }
Issue:
Major: The output is contains GRAPH urn:x-arq:DefaultGraphNode
Note: urn:x-arq:DefaultGraphNode is for internal use only.
For syntax, that is a named graph just like http://example/g
File: syntax-quad-construct-04.arq
PREFIX : http://example/
CONSTRUCT {
GRAPH ?g { :s :p :o }
?s ?p ?o
}
WHERE
{ GRAPH ?g { ?s ?p ?o } }
Output of qparse --file syntax-quad-construct-04.arq
Check failure: reparsed query hashCode does not equal parsed input
query
Query (hashCode: 1768688961)=
PREFIX : http://example/
CONSTRUCT
{ GRAPH ?g {:s :p :o .
?s ?p ?o .}
}
WHERE
{ GRAPH ?g
{ ?s ?p ?o }
}
Query2 (hashCode: 1896249441)=
PREFIX : http://example/
CONSTRUCT
{ GRAPH ?g {:s :p :o .
?s ?p ?o .}
}
WHERE
{ GRAPH ?g
{ ?s ?p ?o }
}
PREFIX : http://example/
CONSTRUCT
{ GRAPH ?g {:s :p :o .
?s ?p ?o .}
}
WHERE
{ GRAPH ?g
{ ?s ?p ?o }
}
Issue:
The output puts the following triple into the GRAPH.
See also syntax-quad-construct-08.arq
File: syntax-quad-construct-05.arq
PREFIX : http://example/
CONSTRUCT {
?s ?p ?o
GRAPH ?g { :s :p :o }
}
WHERE
{ GRAPH ?g { ?s ?p ?o } }
Output of qparse --file syntax-quad-construct-05.arq
Check failure: reparsed query hashCode does not equal parsed input
query
Query (hashCode: -262437683)=
PREFIX : http://example/
CONSTRUCT
{ GRAPH urn:x-arq:DefaultGraphNode {?s ?p ?o .
:s :p :o .}
}
WHERE
{ GRAPH ?g
{ ?s ?p ?o }
}
Query2 (hashCode: -399379987)=
PREFIX : http://example/
CONSTRUCT
{ GRAPH urn:x-arq:DefaultGraphNode {?s ?p ?o .
:s :p :o .}
}
WHERE
{ GRAPH ?g
{ ?s ?p ?o }
}
PREFIX : http://example/
CONSTRUCT
{ GRAPH urn:x-arq:DefaultGraphNode {?s ?p ?o .
:s :p :o .}
}
WHERE
{ GRAPH ?g
{ ?s ?p ?o }
}
Issue:
Plain ?s ?p ?o has been put into a named graph
Adjacent blocks have merged.
File: syntax-quad-construct-06.arq
PREFIX : http://example/
CONSTRUCT {
GRAPH ?g { :s :p :o }
?s ?p ?o .
?s ?p ?o .
GRAPH ?g { ?s ?p ?o }
?s ?p ?o .
?s ?p ?o
GRAPH ?g { ?s ?p ?o }
}
WHERE
{ GRAPH ?g { ?s ?p ?o } }
Output of qparse --file syntax-quad-construct-06.arq
Check failure: reparsed query hashCode does not equal parsed input
query
Query (hashCode: -1800516808)=
PREFIX : http://example/
CONSTRUCT
{ GRAPH ?g {:s :p :o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .}
}
WHERE
{ GRAPH ?g
{ ?s ?p ?o }
}
Query2 (hashCode: -129418312)=
PREFIX : http://example/
CONSTRUCT
{ GRAPH ?g {:s :p :o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .}
}
WHERE
{ GRAPH ?g
{ ?s ?p ?o }
}
PREFIX : http://example/
CONSTRUCT
{ GRAPH ?g {:s :p :o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .
?s ?p ?o .}
}
WHERE
{ GRAPH ?g
{ ?s ?p ?o }
}
Issue:
Same as previous.
File: syntax-quad-construct-07.arq
PREFIX :
