You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "hongbin ma (JIRA)" <ji...@apache.org> on 2015/09/01 13:24:45 UTC

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

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

hongbin ma commented on KYLIN-981:
----------------------------------

I'm wondering why retentionRange has to be a property on cubeintance?
the same for autoMergeTimeRanges.

It would be easier for metadata manipulation if all of such configurations reside in cubedesc,
so will reduce our frontend efforts.

> 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)