Thanks, i will see tomorrow.


> 在 2020年1月10日,13:56,梅秋莹 <[email protected]> 写道:
> 
> Thank you very much! This is  compelete kylin log. You can see the error 
> message at 2020-01-08 16:04:12. If kylin dose not support view as a lookup 
> table, is there only one way to solve the problem? That is, creating entity 
> table.
> 
> 
> ------------------ 原始邮件 ------------------
> 发件人: "[email protected] 
> <mailto:[email protected]>"<[email protected] 
> <mailto:[email protected]>>;
> 发送时间: 2020年1月9日(星期四) 下午2:39
> 收件人: "user"<[email protected] <mailto:[email protected]>>;
> 主题: Re: Kylin support view as lookup table?
> 
> First, kylin does support using view as a lookup table. During the build 
> process, there is a special step to handle the case where the view is a 
> lookup table, called Materialize Hive View in Lookup Tables, it's main 
> process is as follows:
> 
> <[email protected]>
> From your logs, the error occurred in step Build Dimension Dictionary, at 
> this time step Materialize Hive View in Lookup Tables has been completed。
> 
> Can you provide a more complete kylin.log or reproduce the error on the 
> sample dataset?
> 
> 
> <[email protected]>
> 
>> 在 2020年1月9日,14:08,梅秋莹 <[email protected] <mailto:[email protected]>> 写道:
>> 
>> Dear Kyliners:
>> 
>>         1. Environment: kylin 2.6.3
>>         2. Question:
>>  
>>         In some articles, I notice that kylin support view as lookup table. 
>> In my model  and cube, there is  field “fpdate” and “date” in fact table, 
>> and the field "fpdate" and "date" both represnt date.
>>  So I created a PAYMENT_DATE_DIM as  entity table and a view called 
>> BILLING_PERIOD_DIM. These two table structures are identical.
>>         But when I build the cube, in the "Build Dimension Dictionary" step, 
>> kylin returned an error like this "hive view 替代物理表 build cube 时 
>> java.lang.ClassCastException: org.apache.hadoop.io 
>> <http://org.apache.hadoop.io/>.LongWritable cannot be cast to 
>> org.apache.hadoop.io.Text". How can I solve the problem? If kylin have some 
>> usage restriction?
>> 
>> <[email protected]>
>> <[email protected]>
>> 
> 
> <[email protected]><[email protected]><kylin.rar>

Reply via email to