kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KYLIN-1366) Bind metadata version with release version
Date Wed, 27 Jan 2016 17:03:39 GMT

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

Hao Chen commented on KYLIN-1366:
---------------------------------

[~mahongbin] 

I think it's very clear to add version for metadata: https://github.com/haoch/kylin/commit/9802371361ba4b4a6efb225be6d2451a82326d42

But a few questions:
1) Should the metadata version always keep consistent with kylin project version?
2) how do you think to load the value of version? From configuration, system.properties or
something else as the best practice? 

> Bind metadata version with release version
> ------------------------------------------
>
>                 Key: KYLIN-1366
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1366
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Metadata
>    Affects Versions: all
>            Reporter: hongbin ma
>            Assignee: Hao Chen
>              Labels: newbie
>             Fix For: v2.1
>
>
> Currently metadata does not have special property to identify its version, even though
we already versions of metadata in 1.x, 2.0 and 2.x. If each file in the metadata is bound
with version it will be easier for upgrading related issues.



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

Mime
View raw message