[ https://issues.apache.org/jira/browse/LENS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411003#comment-15411003 ]
Hadoop QA commented on LENS-197: -------------------------------- Applied patch: [LENS-197-2.patch|https://issues.apache.org/jira/secure/attachment/12822266/LENS-197-2.patch] and ran command: mvn clean install -fae. Result: Success. Build Job: https://builds.apache.org/job/PreCommit-Lens-Build/780/ > Allow start and end times for columns in fact tables > ---------------------------------------------------- > > Key: LENS-197 > URL: https://issues.apache.org/jira/browse/LENS-197 > Project: Apache Lens > Issue Type: Improvement > Components: cube > Reporter: Amareshwari Sriramadasu > Assignee: Sushil Mohanty > Attachments: LENS-197-2.patch > > > We can have columns being promoted/demoted from one aggregate fact to other, > with usage of columns in reports. > We need this for the following use cases: > # If field is moved to a lower cost fact: Since the fact is having lower cost > it will be picked up for processing, but if the life of column queried does > not fit in the range queried, a higher level fact should be picked up. If > lower level fact is picked, it would lead to wrong results. > # If field is moved to a higher cost fact, i.e. its life ending in a lower > cost fact. Again, depending on the range queried, either lower or higher > level fact should be picked up. It will be more like optimization for this > case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)