You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2015/06/16 14:21:00 UTC
[jira] [Commented] (LENS-605) Candidate pruning is going wrong wrt
sourcecolumns required for joinchains
[ https://issues.apache.org/jira/browse/LENS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587942#comment-14587942 ]
Amareshwari Sriramadasu commented on LENS-605:
----------------------------------------------
Review request put up at https://reviews.apache.org/r/35459/
> Candidate pruning is going wrong wrt sourcecolumns required for joinchains
> --------------------------------------------------------------------------
>
> Key: LENS-605
> URL: https://issues.apache.org/jira/browse/LENS-605
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
> Affects Versions: 2.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 2.2
>
>
> Say we have two chainref denorm-columns in cube:
> dcol1, dcol2.
> Fact1 does not have both columns - but dcol1 is available through its key, dcol2 is not available, then Fact1 is not getting pruned.
> It should have been pruned because dcol2 is not available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)