falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-785) Document upgrade path from 0.5 to 0.6
Date Mon, 17 Nov 2014 01:53:40 GMT

    [ https://issues.apache.org/jira/browse/FALCON-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214189#comment-14214189

Srikanth Sundarrajan commented on FALCON-785:

[~svenkat], Sorry I haven't had the chance to get to this.

The document states that there are minor changes users need to be aware of. Are these documented
elsewhere? If so can we link them here?
+0.6-incubating is backwards compatible with 0.5-incubating. However, there are some minor
+to be aware of.

In general it would be good to cover the level of compatibility
1. If falcon-0.5 is being used, is falcon-0.6 a drop in replacement, where a new server version
is installed and users (refers to both administrators who maintain falcon server instance
and the users who submit and manage falcon entities) aren't expected to make any change.
2. If (1) above is not possible, can falcon-0.6 be installed and some server side configs
tweaked with no change to user entities. If so what are the changes that need to be made to
the server side configurations
3. If (1) & (2) aren't true, then it actually wouldn't be backward compatible and user
would have to take actions to move to falcon-0.6.

Can [~samarthg]/[~arpitgupta]/[~raghavgautam]/[~rostafiychuk] help in checking this compatibility?

> Document upgrade path from 0.5 to 0.6
> -------------------------------------
>                 Key: FALCON-785
>                 URL: https://issues.apache.org/jira/browse/FALCON-785
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: docs
>    Affects Versions: 0.6
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>             Fix For: 0.6, 0.7
>         Attachments: FALCON-785.patch

This message was sent by Atlassian JIRA

View raw message