[
https://issues.apache.org/jira/browse/LENS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273569#comment-14273569
]
Jaideep Dhok commented on LENS-197:
-----------------------------------
If there is a time range - [d1, d3] And column C in F1 with life [d1, d2] and
in F2 with life [d2, d3] (d1 < d2 < d3). Cost(F1) < Cost(F2)
Are we saying if the query time range is [d1, d3] We have to pick up *both* F1
and F2? According to current time range validation code, neither of them will
be picked up.
> 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
>
> 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)
