Measure column missing in Kylin 3.0 model

[Gayathri Rengarajan <ga...@hobsons.com>]

Hello

This may have been already addressed in an earlier email or documentation but sending an email since I could not find any reference.

When building a model in Kylin 3.0 noticed that we are unable to add a column as measure if that column has been used in a join condition with a look up table.
Any reason why this is the case? How to overcome this problem?

Thanks
Gayathri

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

Re: Measure column missing in Kylin 3.0 model

[Yaqian Zhang <Ya...@126.com>]

Hi:

I test this in my env.

I have create a model with a fact_table KYLIN_SALES and a lookup table KYLIN_CAL_DT, and the join condition is KYLIN_SALES.PART_DT = KYLIN_CAL_DT.CAL_DT,  both columns are added to the list of dimensions in this model.

Then I create a cube in this model, add PART_DT and CAL_DT to dimension, when I want to add PART_DT as measure, I need to check 'Also Show Dimensions’, then the dimensions column can be added as measures.



> 在 2020年7月30日，04:21，Gayathri Rengarajan <ga...@hobsons.com> 写道：
> 
> Hello
>  
> This may have been already addressed in an earlier email or documentation but sending an email since I could not find any reference.
>  
> When building a model in Kylin 3.0 noticed that we are unable to add a column as measure if that column has been used in a join condition with a look up table.
> Any reason why this is the case? How to overcome this problem?
>  
> Thanks
> Gayathri
>  
> 
> 
> Disclaimer
> 
> This message contains confidential information and is intended only for the intended recipients. If you are not an intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
>