Em.. this worth a JIRA. https://issues.apache.org/jira/browse/KYLIN-2206
On Wed, Nov 9, 2016 at 8:18 PM, roger shi <[email protected]> wrote: > Hi Ankur, > > Kylin doesn't support this kind of query " ... where fo.pick_due_ts >= > fo.last_update_ts ... ". You work around by creating view of the origin > table with a new column, for example larger_pick. The column's value is 1 > for pick_due_ts >= last_update_ts, otherwise the value is 0. > > Your query can be this: > select distinct count(*) from fulfill_order fo left join > fulfill_order_status fos on ( fo.fulfill_order_id = fos.fulfill_order_id > and fo.fulfill_order_status_code = fos.fulfill_order_status_code > and fo.last_update_ts= fos.status_update_timestamp > ) where fo.fulfill_order_status_code in (7,8) and fo.larger_pick = 1; > ________________________________ > 发件人: Ankur Kapoor <[email protected]> > 发送时间: 2016年11月9日 12:33:06 > 收件人: [email protected] > 主题: Re: Duplicate Column! Error coming while executing the query- Using > Kyline 1.6 Snapshot version > > Guys, please help me on this, I am kind of stuck! > > -- > View this message in context: http://apache-kylin.74782.x6. > nabble.com/Duplicate-Column-Error-coming-while-executing- > the-query-Using-Kyline-1-6-Snapshot-version-tp6230p6237.html > Sent from the Apache Kylin mailing list archive at Nabble.com. >
