[ 
https://issues.apache.org/jira/browse/KYLIN-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728688#comment-16728688
 ] 

Chao Long commented on KYLIN-3731:
----------------------------------

I see, you convert the array type column(*_impression_click_id_*) to 
string(*_product_id_*) and keep impression_click_id in the hive view. 

Do you send query with _*impression_click_id*_ in kylin? 

If you just query with *_product_id_*, I think you can remove  
*_impression_click_id_* from the hive view, so kylin will not load array type 
data.

If you do query with *_impression_click_id_*, please let me know how the query 
like.

To fix "Unsupported data type array<string>" exception, just need to skip 
segment pruning when the column data type is array.

> java.lang.IllegalArgumentException: Unsupported data type array<string> at 
> ---------------------------------------------------------------------------
>
>                 Key: KYLIN-3731
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3731
>             Project: Kylin
>          Issue Type: Bug
>          Components: Job Engine
>    Affects Versions: v2.5.1
>            Reporter: HongBo  Dai
>            Assignee: Chao Long
>            Priority: Critical
>              Labels: build
>             Fix For: v2.5.1
>
>         Attachments: error of kylin.txt, image-2018-12-20-10-59-04-060.png, 
> screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png
>
>
> As kylin was recently upgraded from 2.3 to 2.5.1, its data type of array 
> metadata was found to be unsupported and the following exception occurred
> "java. lang. IllegalArgumentException: Unsupported data type array", are in 
> kylin2.3 hive data storage array before running this type is no problem, 
> there is the lead in building a cube when the third step is as follows
> "org. apache. kylin. engine. mr. Exception. MapReduceException: no counters 
> for the job", could you tell me how to solve the problem without changing 
> data structure situation now? please  look up  attachment. 
> !image-2018-12-20-10-59-04-060.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to