Hi Shaofeng, many thanks for your reply. Just to confirm that per your example, if the “partition_date” are only used as a partition column and not being included in the dimension list, queries including it will work exactly the same as it are included both as a partition column and in the dimension list, is it right? If it is not, what’s the difference? Thanks again! Best, Feng.
发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用 ________________________________ 发件人: ShaoFeng Shi <shaofeng...@apache.org> 发送时间: Monday, September 24, 2018 2:41:55 PM 收件人: user 主题: Re: Segment columns and dimension columns Hi Feng, Usually, the partition date column is a dimension. But it is not required. For example, your table has two date columns: "partition_date" and "order_date"; You data is partitioned with the "partition_date" in Hive, so you'd better use the same in Kylin, but you can use the "order_date" as a dimension and "partition_date" not in dimension list. Francis Liang <soulvagr...@hotmail.com<mailto:soulvagr...@hotmail.com>> 于2018年9月19日周三 下午3:13写道： Hi: I am having a question regarding two types of columns mentioned above. If I am using a column as a segment column, such as DAY, and it’s required as the filter in queries, should I also put it in the dimension columns, or is it redundant to do so? If it’s included in the dimension columns, does it mean the records from different segments can’t be merged since the DAY field is different (DAY=20180918, DAY=20180919)? Thanks for your help! Best, Feng. 发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用 -- Best regards, Shaofeng Shi 史少锋
