[
https://issues.apache.org/jira/browse/FALCON-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958780#comment-14958780
]
Pallavi Rao commented on FALCON-1541:
-------------------------------------
[~pragya.mittal], as we discussed offline, the appropriate deploy.properties is
bundled along with .war of prism and server. So, we won't need to bundle it
again. Also, this is more of an internal file, which the users are not expected
to modify.
But, as we noted, when we build with -Pdistributed, falcon.war is bundling
deploy.properties (which has deploy.mode as embedded), although there is an
explicit exclude. We'll just need to fix that.
> Bundle deploy.properties while packaging falcon
> -----------------------------------------------
>
> Key: FALCON-1541
> URL: https://issues.apache.org/jira/browse/FALCON-1541
> Project: Falcon
> Issue Type: Bug
> Affects Versions: 0.8
> Environment: QA
> Reporter: Pragya Mittal
> Assignee: Pragya Mittal
> Attachments: FALCON-1541.patch
>
>
> Currently falcon is packaged in a way that deploy.properties are not a part
> of bundle. So when we deploy falcon in distributed mode, falcon has no way of
> knowing which mode it is in,thus considering embedded mode which is default
> by nature. This was discovered while testing FALCON-1515 and FALCON-1526. IMO
> falcon should bundle deploy.properties while packaging and handle the
> configurations depending on the mode of deployment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
