[
https://issues.apache.org/jira/browse/KYLIN-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17930130#comment-17930130
]
ASF subversion and git services commented on KYLIN-6042:
--------------------------------------------------------
Commit f477844343892748c24207a51431857e5be4d39a in kylin's branch
refs/heads/kylin5 from Guoliang Sun
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=f477844343 ]
KYLIN-6042 Fix the discard_table_index parameter to ensure that no detail
indexes are recommended
> Model acceleration interface: The parameter discard_table_index is not taking
> effect
> ------------------------------------------------------------------------------------
>
> Key: KYLIN-6042
> URL: https://issues.apache.org/jira/browse/KYLIN-6042
> Project: Kylin
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Guoliang Sun
> Priority: Major
>
> 1. When the parameter discard_table_index is true, detailed index suggestions
> are still generated. API: kylin/api/models/model_optimization
> 2. SQL reference
> {code:java}
> SELECT c.* FROM (
> select a.*, b.* from (
> SELECT LO_ORDERPRIOTITY AS LO_ORDERPRIOTITY
> FROM HANHAN_LOGICAL_VIEW.LOGICAL_VIEW_LINEORDER
> ) a
> right join (
> select * from (
> SELECT trim(C_NAME) AS C_NAME
> FROM SSB.CUSTOMER
> ) d
> ) b
> on trim(a.LO_ORDERPRIOTITY)=b.C_NAME
> ) c{code}
> 3. Two modelContexts were generated with the same targetModel. The
> findFirst() here caused the IndexRexItemMap in the second modelContext not to
> be removed, resulting in the successful creation of detailed index
> suggestions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
