[
https://issues.apache.org/jira/browse/LENS-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264208#comment-14264208
]
Suma Shivaprasad edited comment on LENS-88 at 1/5/15 6:00 AM:
--------------------------------------------------------------
[~prongs] IMO , we should not accept 2 join chains during cube /dimension
creation itself . there will be 2 sets of users - oen ad admin - who will
create the chain and another a naive user who is not aware of whats happening
wrt joinchains. It would be better to surface the issue during DDL operation
itself instead of during query time.
The other approach is to handle 2 different join chains automatically and pick
up the one with the least amount of hops, for eg:
was (Author: suma.shivaprasad):
[~prongs] IMO , either we should not accept 2 join chains during cube
/dimension creation itself . there will be 2 sets of users - oen ad admin -
who will create the chain and another a naive user who is not aware of whats
happening wrt joinchains. It would be better to surface the issue during DDL
operation itself instead of during query time.
The other approach is to handle 2 different join chains automatically and pick
up the one with the least amount of hops, for eg:
> 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)
