[
https://issues.apache.org/jira/browse/BIGTOP-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581443#comment-13581443
]
Konstantin Boudnik commented on BIGTOP-637:
-------------------------------------------
Roman,
it isn't about forks of "the code": the original patch was solving an exact
issue that any user of the VM would face immediately.
What BIGTOP-547 try to solve a much broader problem that structures HDFS for
almost anything in the verse, except for that particular case that YARN depends
on. The performance that script is another issue: I don't think it is
acceptable UX to stretch VM boot for much longer than the Linux boot sequence
takes. That said - I don't see how that ticket is related here. After all: the
VM doesn't come with anything but plain Hadoop, so why bother? "Let's have it
just in case" mentality, perhaps?
Avoiding dups is great. But avoiding dups in any mkdir and chmod command in the
project sounds plain insane if you ask me.
> Update boxgrinder appliance for the coming release
> --------------------------------------------------
>
> Key: BIGTOP-637
> URL: https://issues.apache.org/jira/browse/BIGTOP-637
> Project: Bigtop
> Issue Type: Bug
> Affects Versions: 0.4.0
> Reporter: Bruno Mahé
> Assignee: Konstantin Boudnik
> Fix For: 0.6.0
>
> Attachments:
> 0001-BIGTOP-637.-Update-boxgrinder-appliance-for-the-comi.patch,
> BIGTOP-637-2.patch.txt, BIGTOP-637.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
