I see... frontend should pass both CubeDesc and CubeInstance then. Duplicate property on CubeDesc just to pass to frontend does not make sense.
On Mon, Aug 31, 2015 at 2:25 PM, Shi, Shaofeng <[email protected]> wrote: > ³retentionRange" is an attribution defined on CubeInstance; While as Kylin > cube wizard doesn¹t write CubeInstance directly (it only has access on > CubeDesc); In order to allow user specify the value from front-end, this > property was duplicated on CubeDesc; Yes you¹re right, as properties will > be defined at CubeInstance level, the cube wizard need the capability to > write CubeInstance directly; JIRA is created for it: > > > https://issues.apache.org/jira/browse/KYLIN-981 > > > On 8/29/15, 9:42 AM, "Li Yang" <[email protected]> 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. > >
