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-104) FALCON-86 introduces a backward incompatible change
Date Thu, 10 Oct 2013 08:46:43 GMT

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

Srikanth Sundarrajan commented on FALCON-104:
---------------------------------------------

+1. Looks good. Can be merged post verification of build

> FALCON-86 introduces a backward incompatible change
> ---------------------------------------------------
>
>                 Key: FALCON-104
>                 URL: https://issues.apache.org/jira/browse/FALCON-104
>             Project: Falcon
>          Issue Type: Sub-task
>    Affects Versions: 0.4
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>         Attachments: FALCON-104.patch
>
>
> Srikanth mentioned in an offline conversation that org.apache.falcon.entity.parser.ClusterEntityParser#validateRegistryInterface
introduces an incompatible change. Need to make sure catalog.service.impl is enabled before
validating. 
> One problem is in the current prod setup the cluster defn has a dummy text against this
interface means that falcon isn't able to load any cluster during startup. 
> This should be done conditionally if catalog service is enabled.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message