[
https://issues.apache.org/jira/browse/LENS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261977#comment-14261977
]
Amareshwari Sriramadasu edited comment on LENS-122 at 12/31/14 6:25 AM:
------------------------------------------------------------------------
bq. At the end, two different ASTs are available each for Fact1 and Fact2. Each
of them could lead to different joins depending on if the expressions need to
be realised via a join. How do we choose one of the queries in such a case?
This already taken care in JoinResolver through optional joining tables -
similar to denormalization resolver. In denormalizationresolver, rewrites the
context once the fact is picked, similarly expression resolver will also
rewrite context with picked fact.
was (Author: amareshwari):
bq. At the end, two different ASTs are available each for Fact1 and Fact2. Each
of them could lead to different joins depending on if the expressions need to
be realised via a join. How do we choose one of the queries in such a case?
This already taken care in JoinResolver through optional joining tables -
similar to denormalization resolver. In denormalizationresolver, rewrites the
context once the fact is picked, similarly we expression resolver will also
rewrite context with picked fact.
> Add multiple expressions to expression column
> ----------------------------------------------
>
> Key: LENS-122
> URL: https://issues.apache.org/jira/browse/LENS-122
> Project: Apache Lens
> Issue Type: New Feature
> Components: cube
> Reporter: Amareshwari Sriramadasu
> Assignee: Jaideep Dhok
> Fix For: 2.0
>
>
> There can be multiple expressions for an expression column and then
> expression resolver should replace them lazily.
> This was required to solve two usecases:
> # Allowing some fact tables to have expressions directly materialized
> # Having two different expressions in different facts for same expression
> column
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
