[
https://issues.apache.org/jira/browse/JENA-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149755#comment-13149755
]
Rob Vesse commented on JENA-162:
--------------------------------
Personally as this is at the protocol level I'd like to see at least the
description built in Fuseki even if that description is just two lists of URIs
and have that attached to the query/execution context so it is accessible at
the storage/query engine layer.
>From our point of view we just need to be able to access the dataset
>description at the query engine layer so we'd prefer that this wasn't pushed
>down too far into the stack.
The command line option does not necessarily have to control whether the
storage layer accepts such queries merely that the protocol layer (Fuseki)
accepts them or not. Even with this option enabled the storage/query layer
should still have the final say in accepting/rejecting the query
> Add FROM/FROM NAMED support to Fuseki
> -------------------------------------
>
> Key: JENA-162
> URL: https://issues.apache.org/jira/browse/JENA-162
> Project: Jena
> Issue Type: New Feature
> Components: Fuseki
> Affects Versions: Fuseki 0.2.1
> Reporter: 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 TestQuery.java 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
