clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CLEREZZA-802) Allow to enforce fastlane usage
Date Mon, 15 Jul 2013 09:16:50 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708336#comment-13708336
] 

Reto Bachmann-Gmür commented on CLEREZZA-802:
---------------------------------------------

About 1) No, Iterating is certainly not an option and in fact this was never done. Even when
not enforcing fastlane we just choose the fastlane if the default graph is ignored by the
query.

About 2) This is just getSingleTargetTcProvider(Collections.singleton(defaultGraphName))

About TripleCollection.getProvider() ) No a triple collection is just that, a collection of
triples, thus I'm against all proposals to add name, dataset, webid of owner, network origin
or other stuff to it. If such things are needed then new classes should be created to represent
them.
                
> Allow to enforce fastlane usage
> -------------------------------
>
>                 Key: CLEREZZA-802
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-802
>             Project: Clerezza
>          Issue Type: Bug
>          Components: rdf.core
>            Reporter: Minto van der Sluis
>            Assignee: Minto van der Sluis
>
> The new sparql fastlane reverts to slowlane if the query contains multiple multiple graphs.
A special option is required to allow to ensure fastlane usage if required. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message