Unfortunately, there's no webUI for extended column yet. we're still working on it.
You can edit the cube desc json directly, refer to KYLIN_HOME/examples/test_case_data/localmeta/cube_desc/test_kylin_cube_without_slr_desc.json as an example, we have two extended column measure there: SITE_EXTENDED_1 and SITE_EXTENDED_2 after you manually edit the cube desc json, you also need to erase the line "signature", so that a new cube desc signature can be automatically generated. On Tue, Jun 28, 2016 at 12:30 AM, Yiming Liu <[email protected]> wrote: > Get it. Thanks Dong & Leilei. > > 2016-06-27 22:14 GMT+08:00 移动苏州研发中心-陈雷雷 <[email protected]>: > > > Hi YiMing > > 1,How did you add the extended column, through the GUI or REST API? > > I added the extended column through the GUI with kylin version > > 1.5.2.1. When you defined a cube, it has two actions on the cube. The > > second is to edit the json of the cube. In the json, it have measures > which > > you defined. All you have to do is to add json segment as fllows. The > value > > (PROVINCE_ID) in parameter is the PK in fact table and the value > > (PROVINCE_NAME) in next_parameter is the FK in fact table. > > { > > "name": "3", > > "function": { > > "expression": "EXTENDED_COLUMN", > > "parameter": { > > "type": "column", > > "value": "PROVINCE_ID", > > "next_parameter": { > > "type": "column", > > "value": "PROVINCE_NAME", > > "next_parameter": null > > } > > }, > > "returntype": "extendedcolumn(100)" > > }, > > "dependent_measure_ref": null > > } > > > > 2,Why the wrong json was introduced? > > First time, I did not add the next_parameter like this. You need > > tell kylin which is the PK and which is the FK. > > { > > "name": "3", > > "function": { > > "expression": "EXTENDED_COLUMN", > > "parameter": { > > "type": "column", > > "value": "PROVINCE_ID", > > "next_parameter": null > > }, > > "returntype": null > > }, > > "dependent_measure_ref": null > > } > > > > you can see details in KYLIN-1313 ( > > https://issues.apache.org/jira/browse/KYLIN-1313). > > ------------------ 原始邮件 ------------------ > > *发件人:* "Yiming Liu";<[email protected]>; > > *发送时间:* 2016年6月27日(星期一) 晚上9:46 > > *收件人:* "移动苏州研发中心-陈雷雷"<[email protected]>; > > *抄送:* "dev"<[email protected]>; > > *主题:* Re: EXTENDED_COLUMN-build error > > > > Hi Leilei, > > > > Could you explain a little more about the wrong json? How did you add the > > extended column, through the GUI or REST API? Why the wrong json was > > introduced? > > > > > > 2016-06-27 17:15 GMT+08:00 移动苏州研发中心-陈雷雷 <[email protected]>: > > > >> problem solved. > >> > >> > >> the json is wrong. > >> > >> > >> the right json is like this : > >> { > >> "name": "3", > >> "function": { > >> "expression": "EXTENDED_COLUMN", > >> "parameter": { > >> "type": "column", > >> "value": "PROVINCE_ID", > >> "next_parameter": { > >> "type": "column", > >> "value": "PROVINCE_NAME", > >> "next_parameter": null > >> } > >> }, > >> "returntype": "extendedcolumn(100)" > >> }, > >> "dependent_measure_ref": null > >> } > >> > >> > >> > >> ------------------ 原始邮件 ------------------ > >> 发件人: "ShaoFeng Shi";<[email protected]>; > >> 发送时间: 2016年6月25日(星期六) 晚上8:27 > >> 收件人: "dev"<[email protected]>; > >> > >> 主题: Re: EXTENDED_COLUMN-build error > >> > >> > >> > >> hi leilei, no attachement received, seems Apache mailing list doesn't > >> support it; Could you please try some way else or send it to my mailbox? > >> Thanks; > >> > >> 2016-06-24 20:43 GMT+08:00 移动苏州研发中心-陈雷雷 <[email protected]>: > >> > >> > hi all: > >> > > >> > I added a extended_column cell_name and when I build the cube it > >> > failed. I don't know why. The diagnosis zip is in the attachement. > >> > > >> > > >> > > >> > >> > >> > >> -- > >> Best regards, > >> > >> Shaofeng Shi > >> > > > > > > > > -- > > With Warm regards > > > > Yiming Liu (刘一鸣) > > > > > > -- > With Warm regards > > Yiming Liu (刘一鸣) > -- Regards, *Bin Mahone | 马洪宾*
