[ https://issues.apache.org/jira/browse/LENS-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128628#comment-16128628 ]
Rajat Khandelwal commented on LENS-1459: ---------------------------------------- Small enough diff. Attaching directly > Time union candidate creation phase is creating a combination with redundant > candidates > --------------------------------------------------------------------------------------- > > Key: LENS-1459 > URL: https://issues.apache.org/jira/browse/LENS-1459 > Project: Apache Lens > Issue Type: Bug > Components: cube > Reporter: Rajat Khandelwal > Assignee: Rajat Khandelwal > Attachments: LENS-1459.2017-08-16_16:28:29.patch > > > After the optimization in LENS-1452, Combinations as mentioned in the jira > summary can get created. Say the time range queried is {{\[f, t)}}, Candidate > {{a}} and {{b}} can cover {{\[f, m)}} and candidate {{c}} can cover {{\[m, > t)}}. Say a Union candidate is represented as {{U(cand1, cand2,...)}}. Then > the code creates {{U(a,b,c), U(a,c) and U(b,c)}}. If {{U(a,b,c)}} is picked > as final candidate, then one of {{a}} or {{b}} doesn't resolve partitions and > {{time_range_in}} clause is left as it is for that. -- This message was sent by Atlassian JIRA (v6.4.14#64029)