[
https://issues.apache.org/jira/browse/LENS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595570#comment-14595570
]
Hudson commented on LENS-605:
-----------------------------
SUCCESS: Integrated in Lens-Commit #831 (See
[https://builds.apache.org/job/Lens-Commit/831/])
LENS-605 : Fix Candidate pruning wrt sourcecolumns required for joinchains
(rajatgupta59: rev 5f859118c2ea49cc09dd59472d266064d36ca978)
* lens-cube/src/main/java/org/apache/lens/cube/parse/ExpressionResolver.java
*
lens-cube/src/main/java/org/apache/lens/cube/parse/DenormalizationResolver.java
*
lens-cube/src/test/java/org/apache/lens/cube/parse/TestDenormalizationResolver.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/CandidateTableResolver.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/JoinResolver.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/CubeQueryContext.java
> 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
>
> Attachments: LENS-605.3.patch
>
>
> 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)
