You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "David W. Lotts (JIRA)" <ji...@apache.org> on 2016/09/03 02:02:21 UTC
[jira] [Commented] (RYA-167) Query Planner creates "Cross Product"
on Temporal Filters
[ https://issues.apache.org/jira/browse/RYA-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15460136#comment-15460136 ]
David W. Lotts commented on RYA-167:
------------------------------------
A quick and dirty work-around if your usage allows it, until we have a better solution:
The query optimizer implementation: QueryJoinOptimizer seems to rearrange the query plan to cause the cross-product for our test case.
So comment this line:
in file: /rya.sail/src/main/java/mvm/rya/rdftriplestore/RdfCloudTripleStoreConnection.java :
Around line 400:
(new mvm.rya.rdftriplestore.evaluation.QueryJoinOptimizer(stats)).optimize(tupleExpr, dataset, bindings);
It improves the number of temporal evaluations in the [Gist link above|https://gist.github.com/amihalik/24b584101f77d4c546dbb54bf75470b1] from 18 down to just 3.
> Query Planner creates "Cross Product" on Temporal Filters
> ---------------------------------------------------------
>
> Key: RYA-167
> URL: https://issues.apache.org/jira/browse/RYA-167
> Project: Rya
> Issue Type: Bug
> Components: sail
> Reporter: Aaron Mihalik
> Assignee: David W. Lotts
> Priority: Critical
>
> The query planner creates a "Cross Product" when there's a geo and two temporal filters.
> I created a gist with "Print line Debugging" updates to AccumuloTemporalIndexer, a RyaDirectExample exposing the query planning bug, and the output showing the bad query plan and evidence of a cross product:
> https://gist.github.com/amihalik/24b584101f77d4c546dbb54bf75470b1
> I explain the observed behavior on this gist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)