[
https://issues.apache.org/jira/browse/KYLIN-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928294#comment-17928294
]
Guoliang Sun commented on KYLIN-6023:
-------------------------------------
h3. Root Cause
Before updating, the latest record was retrieved from the database and updated,
but the properties that needed to be modified were not set.
The original code had test cases, but since the test environment used InMemory
storage, each call to `getModelById` returned the same object. Modifying
attributes using `nDataModel` would be captured by the logic in `copyForWrite`
(here, only the `id` of `nDataModel` is used to lock and fetch the latest value
of the record, which references the same `nDataModel`). Therefore, the test
case passed.
> Kylin5 model cannot be renamed
> ------------------------------
>
> Key: KYLIN-6023
> URL: https://issues.apache.org/jira/browse/KYLIN-6023
> Project: Kylin
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Guoliang Sun
> Priority: Major
>
> The rename interface in the UI submits successfully and returns a success
> response, but the model name remains unchanged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
