It seems user had defined a lookup table in the cube, while finally there is no dimension from that lookup table; The workaround is to create a new cube without that lookup table.
Anyway, this should be a bug, I created a JIRA to fix it: https://issues.apache.org/jira/browse/KYLIN-644 On 3/17/15, 2:32 PM, "hongbin ma" <[email protected]> wrote: >can you go to cubes tab ,select your cube, open the sub tabs called >"json" >and send us the content? > >On Mon, Mar 16, 2015 at 9:35 PM, Luke Han <[email protected]> wrote: > >> Forward to mailing list for further support >> >> 在 2015年3月16日星期一 UTC-7下午4:18:07，Kaine写道： >>> >>> >>> An error occured when I try to build a cube. I examined the log and >>>found >>> this : >>> >>> INSERT OVERWRITE TABLE kylin_intermediate_ZSJ_19700101000000_ >>> 2922789940817071255_96c192af_6191_4a13_b827_02c9d5eb1a7d SELECT >>> FACT_TABLE.QKDYDM >>> ,FACT_TABLE.NY >>> FROM DEFAULT.ZSJ_FACT_YT as FACT_TABLE >>> INNER JOIN DEFAULT.ZSJ_DIM_NY as null >>> ON FACT_TABLE.NY = null.YEARMONTH >>> INNER JOIN DEFAULT.ZSJ_DIM_ORG as null >>> ON FACT_TABLE.QKDYDM = null.YTDM >>> >>> How can there be 'join xxx as null' in this sentence? >>> >>
