[
https://issues.apache.org/jira/browse/LENS-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258737#comment-14258737
]
Rajat Khandelwal commented on LENS-88:
--------------------------------------
Some thoughts:
Assume the following:
(chain name on lhs, description on rhs)
cityState = basecube -> citydim -> statedim
cubeState = basecube -> statedim
Now the following query becomes valid:
{code}
cube select cubeState.name, cityState.name, sum(msr2) from baseCube
{code}
The following query should also be valid:
{code}
cube select cubeState.name, statedim.capital, sum(msr2) from baseCube
{code}
How about the following query:
{code}
cube select cubeState.name, cityState.name, statedim.capital, sum(msr2) from
baseCube
{code}
What join path would statedim.capital pick? Will it resolve for itself and
employ a new join or will it pick among the two joinpaths to statedim? Which
one will it pick?
So obviously the last query should not be accepted. It should be rejected with
the error that could not determine unique path to statedim.
> Support two different chains for same in same query
> ---------------------------------------------------
>
> Key: LENS-88
> URL: https://issues.apache.org/jira/browse/LENS-88
> Project: Apache Lens
> Issue Type: Task
> Components: cube
> Reporter: Amareshwari Sriramadasu
> Assignee: Rajat Khandelwal
> Fix For: 2.0
>
>
> LENS-41 adds capability to specify multiple join chains and querying the
> columns through chain.
> This task is to support two chains leading to same destination table with
> different chains.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
