[
https://issues.apache.org/jira/browse/LENS-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265804#comment-14265804
]
Amareshwari Sriramadasu commented on LENS-88:
---------------------------------------------
bq. I think its better to choose one among the N join chains automatically
instead of returning an error in this case since the end user may not be aware
which joinchain he should choose and the system should be able to make a
default decision with least no of hops as default or weights if available.
Going with least number of hops may not be the default solution always, and
there can be many chains with least hops as well. I would say we should not do
such resolution from system. JoinChain should have a qualifier as default, and
only chain to the destination table can be qualified as default. This can be
done at DDL time of the cube/chain creation to specify default chain for
destination table. This can done in this jira or separate jira. And if there is
only chain, we can always pick it as the default.
Thoughts?
> 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)
