[
https://issues.apache.org/jira/browse/BIGTOP-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240785#comment-14240785
]
Evans Ye commented on BIGTOP-1555:
----------------------------------
[~jayunit100] as my point of view, I think it would be better to keep all the
configurations in {{vagrantconfig.yaml}}.
However, things like {{export COMPONENTS=yarn,pig && vagrant up}} can be doable.
Is there a reason why you'd like to use it in this way?
> remove mapred-app in related doc or code snippet after BIGTOP-1522
> ------------------------------------------------------------------
>
> Key: BIGTOP-1555
> URL: https://issues.apache.org/jira/browse/BIGTOP-1555
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 0.8.0
> Reporter: Evans Ye
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1555.1.patch
>
>
> In BIGTOP-1522, yarn absorb mapred-app since yarn and mapreduce are
> Indivisible. As a result some code snippet and readme in vagrant or docker
> provisioner might need to be update in order to reflect this change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
