[jira] [Commented] (KYLIN-981) Cube wizard need be able to write CubeInstance directly

["Zhong,Jason (JIRA)" <ji...@apache.org>]

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

Zhong,Jason commented on KYLIN-981:
-----------------------------------

After discussion we finally will not support edit CubeInstance on UI since it's runtime metadata.

here is comment from luke which discussed by us.

“
More comments about CubeDesc and CubeInstance:
1. All human being inputs, relative to source data, data model, settings,
are go to CubeDesc, as metadata.
2. All machine (kylin application) generated runtime information, including
dictionary, segments, hbase htable, statistics, are go to CubeInstance, as
runtime metadata.

More further, the "copy" action will only need copy cube definition
persistent in CubeDesc and create new one with different UUID and Name.

Hope that make sense for these two different metadata types:)
”


> Cube wizard need be able to write CubeInstance directly
> -------------------------------------------------------
>
>                 Key: KYLIN-981
>                 URL: https://issues.apache.org/jira/browse/KYLIN-981
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Web 
>    Affects Versions: v0.7.2, v0.7.1
>            Reporter: Shaofeng SHI
>            Assignee: Zhong,Jason
>
> On 8/29/15, 9:42 AM, "Li Yang" <li...@apache.org> wrote:
> Saw a strange field on CubeDesc called "retentionRange". It duplicates with
> the same name property on CubeInstance, and got a comment saying -- "this
> field will not be serialized ,can be deserialized to front javascript"
> What is this for? I got a feeling something is not done in the correct way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)