Minor correction -- *subquery* should fulfill this case -- well, not
necessarily subquery, just put the count(..) on select clause and it should
work. However this kind of work is based on runtime calculation and does
not benefit Kylin's pre-calculate ability.

Having a flag column prepared on fact table is more preferable in terms of
performance. Kylin will be able to pre-aggregate sum(flag_column) and your
query at runtime will be lightening fast.

Cheers
Yang

On Mon, Mar 2, 2015 at 8:47 PM, Luke Han <[email protected]> wrote:

> subquery should fulfill this case. please have a try and let's know if
> there's any issue.
>
> And, if this is just indicate, can you process it in ETL phase when create
> Hive table?
>
> Thanks.
>
> Luke
>
>
>
> Best Regards!
> ---------------------
>
> Luke Han
>
> 2015-03-02 20:16 GMT+08:00 Santoshakhilesh <[email protected]>:
>
> > Hi All ,
> >
> >
> >
> >     While adding measures while making cube. The formulas supported are
> > count , max , min , ...
> >
> >
> >
> >     I have a case where the measure is simply not a count , max , min or
> > sum
> >
> >
> >
> >     I want to define based on the value of a column in fact table like
> > below.
> >
> >
> >
> >     count(case when column1 < 5 or column2 < 5 or column3 < 80 or column
> <
> > 15 then  1 else 0 end)
> >
> >
> >
> >     How do I support such measures using kylin ? Is there a way to do
> this
> > ?
> >
> >
> >
> > Regards,
> > Santosh Akhilesh
> > Bangalore R&D
> > HUAWEI TECHNOLOGIES CO.,LTD.
> >
> > www.huawei.com
> >
> >
> -------------------------------------------------------------------------------------------------------------------------------------
> > This e-mail and its attachments contain confidential information from
> > HUAWEI, which
> > is intended only for the person or entity whose address is listed above.
> > Any use of the
> > information contained herein in any way (including, but not limited to,
> > total or partial
> > disclosure, reproduction, or dissemination) by persons other than the
> > intended
> > recipient(s) is prohibited. If you receive this e-mail in error, please
> > notify the sender by
> > phone or email immediately and delete it!
> >
>

Reply via email to