incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Vesse (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-162) Add FROM/FROM NAMED support to Fuseki
Date Wed, 14 Mar 2012 16:14:40 GMT


Rob Vesse commented on JENA-162:

The ability for Fuseki to accept queries with FROM/FROM NAMED clauses has been in Trunk for
a while now (and we've used this in production without issue)

As Andy says the current behavior assumes that the underlying query engine takes care of actually
interpreting the dataset description as and when it sees fit.  If that is a satisfactory resolution
to all I'll go ahead and close this issue?
> Add FROM/FROM NAMED support to Fuseki
> -------------------------------------
>                 Key: JENA-162
>                 URL:
>             Project: Apache Jena
>          Issue Type: New Feature
>          Components: Fuseki
>    Affects Versions: Fuseki 0.2.1
>            Reporter: Rob Vesse
>            Assignee: Rob Vesse
>              Labels: from, from-named, sparql
>         Attachments: FusekiFromSupport.patch
> Fuseki currently does not support FROM/FROM NAMED clauses returning a HTTP 400 error
if a user tries to make use of them
> The attached patch provides for optional enabling of this feature by a user specified
--from or --allowFrom switch when the server is started or programmtically via ARQ.getContext().set(Fuseki.enableFromClauses,
true).  Therefore unless a user turns this feature on by default the old behavior remains
in place.
> When enabled Fuseki will not reject queries with FROM/FROM NAMED in them and will use
DynamicDatasets.dynamicDataset() to build the dataset for queries, there is minimal overhead
for queries without FROM/FROM NAMED clauses as the code in DynamicDatasets appears to leave
the default dataset unchanged if no dataset description is present in the query AFAICT
> A small number of tests has been added to to test the behaviour, more
tests might be desirable and I can probably supply those if necessary but the ones given test
all the obvious combinations with the trivial test data used by TestQuery

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message