Or display the Raw with "Beta" or "Experimental" to warn user that it is
not a mature feature?

On Fri, Dec 16, 2016 at 12:30 PM, 康凯森 <[email protected]> wrote:

> +1.
> But the "RAW" measure is still some useful, we could improve it next year
> when we have time.
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "ShaoFeng Shi";<[email protected]>;
> 发送时间: 2016年12月15日(星期四) 中午12:05
> 收件人: "dev"<[email protected]>;
>
> 主题: [Discuss] Disable/hide "RAW" measure in Kylin web GUI
>
>
>
> Hello developers and users,
>
> I have a proposal want to disucss here, which is about the "RAW" measure in
> Kylin.
>
> The RAW measure was developed to solve the requirement for getting raw data
> when user drill down from high level to low levels. It's performance would
> be much better than fetching from source like Hive, so some users like it.
> This blog introduces it:
> https://kylin.apache.org/blog/2016/05/29/raw-measure-in-kylin/
>
> While it has some limitations:
> 1) always use dictionary encoding, which means it couldn't support UHC;
> since raw columns usually be transaction IDs, numbers, etc, the building
> cost is much higher than ordinary dimensions;
> 2) the raw messages for a dimension combination are persisted in one big
> cell,; When too many rows dumped in one cell, will get BufferOverflow
> error. This couldn't be predicted, so for an modeler or analyst he doesn't
> know whether this feature could work when he creates the cube.
> 3) seems no people maintains it;
>
> Based on above, I propose hiding this measure on Web GUI by default, so
> avoiding confusing user; If someone hear and want to use this, he still can
> enable it by simply set in kylin.properties.
>
> Any input is welcomed.
>
> --
> Best regards,
>
> Shaofeng Shi 史少锋
>

Reply via email to