[
https://issues.apache.org/jira/browse/KYLIN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201358#comment-16201358
]
Wang Cheng commented on KYLIN-2931:
-----------------------------------
Hi Jianhua,
can you paste table's name under /table_ext, to verify if it has been separated
by projects.
> Update correct cardinality for the modified table
> -------------------------------------------------
>
> Key: KYLIN-2931
> URL: https://issues.apache.org/jira/browse/KYLIN-2931
> Project: Kylin
> Issue Type: Bug
> Components: Web
> Affects Versions: v2.0.0
> Reporter: peng.jianhua
> Assignee: peng.jianhua
> Priority: Minor
> Labels: patch
> Attachments:
> 0001-KYLIN-2931-Update-correct-cardinality-for-the-modifi.patch, 01.PNG,
> 02.PNG, 03.PNG, 04.PNG, 05.PNG
>
>
> 1,Add project_1 and project_2,each project has the table kylin_sales_copy;
> 2,Do the following steps:
> a,use 'create table kylin_sales_copy as select * from kylin_sales;' to copy
> table kylin_sales;
> b,load table kylin_sales_copy and calculate column cardinality in project_1
> and project_2,please refer to 01.png;
> c,use 'drop table kylin_sales_copy;' to drop table kylin_sales_copy;
> d,use 'create table kylin_sales_copy as select
> TRANS_ID,PART_DT,LSTG_FORMAT_NAME,LEAF_CATEG_ID,LSTG_SITE_ID,SLR_SEGMENT_CD,PRICE
> from kylin_sales where price < 20;' to create the new kylin_sales_copy table;
> Now the structure of kylin_sales_copy has changed, the same as the
> cardinality.
> 3,Reload table kylin_sales_copy in project_1 or project_2,we found that the
> cardinality is not change,please refer to 02.png.
> However,I found that the new cardinality was calculated but not update on the
> web by debug the code,please refer to 03.png,04.png.It should update correct
> cardinality like 05.png.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
