You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Simon Helsen (JIRA)" <ji...@apache.org> on 2012/09/10 15:52:09 UTC
[jira] [Commented] (JENA-294) TransformFilterEquality does not
handle starting OPTIONAL well
[ https://issues.apache.org/jira/browse/JENA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451979#comment-13451979 ]
Simon Helsen commented on JENA-294:
-----------------------------------
although I would like this optimization problem be fixed at some point, we managed to get our client to change their query generator to bypass the problem. We are not aware of anyone else relying on the pattern, so for us the prioity is much lower now. It should certainly not inhibit a new release
> TransformFilterEquality does not handle starting OPTIONAL well
> --------------------------------------------------------------
>
> Key: JENA-294
> URL: https://issues.apache.org/jira/browse/JENA-294
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 2.7.4
> Reporter: Simon Helsen
> Assignee: Andy Seaborne
> Fix For: ARQ 2.9.4
>
> Attachments: filter-equality-13.rq, filter-equality-13.srj, jena-294-afs-1.patch, manifestPatchForOptFilterEquality.txt, patch.txt, patch.txt, test-filter-equality.zip
>
>
> There was one other case where our tests were stuck on a very slow query execution because transformFilterEquality failed to optimize. The problem is that the optimizer gives up whenever the WHERE clause starts with an OPTIONAL clause. The reason is that the generated algebraic formula starts with a TableUnit and this is not handled correctly.
> I have attached a patch which fixes the problem
--
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