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

Sean Mackrory edited comment on BIGTOP-1080 at 9/23/13 11:27 PM:
-----------------------------------------------------------------

+1 on the intent, but -0 on the implementation. I'd love to see more discussion 
around a simple, unified solution to isolating Bigtop's artifacts from other 
distributions and deployment methods.

I see where Mark's coming from and I've been concerned about the OS vendor 
distributions for some time. In fact, we're seeing some of that right now with 
name conflicts with the ideal names for the Avro and Spark packages. Package 
names are just one aspect, and I would bet that any other Hadoop distribution 
is also going to use /usr/bin/hadoop, /var/log/hadoop, etc. We'll need to do 
something like have package a Bigtop prefix for packages names (or make sure 
Bigtop repositories have higher priorities than base OS repositories), and 
enforce package conflicts for other distributions, or hope that the OS vendors 
*also* use alternatives in places where we have not yet.

I think this is a much bigger discussion and this patch is only a partial 
solution, so for now I think we should err on the side of simplicity until we 
can figure out a longer-term, bigger-picture strategy.
                
      was (Author: mackrorysd):
    +1 on the intent, but -0 on the implementation. I'd love to see more 
discussion 

I see where Mark's coming from and I've been concerned about the OS vendor 
distributions for some time. In fact, we're seeing some of that right now with 
name conflicts with the ideal names for the Avro and Spark packages. Package 
names are just one aspect, and I would bet that any other Hadoop distribution 
is also going to use /usr/bin/hadoop, /var/log/hadoop, etc. We'll need to do 
something like have package a Bigtop prefix for packages names (or make sure 
Bigtop repositories have higher priorities than base OS repositories), and 
enforce package conflicts for other distributions, or hope that the OS vendors 
*also* use alternatives in places where we have not yet.

I think this is a much bigger discussion and this patch is only a partial 
solution, so for now I think we should err on the side of simplicity until we 
can figure out a longer-term, bigger-picture strategy.
                  
> Change /usr/bin scripts to be alternatives instead of flat files
> ----------------------------------------------------------------
>
>                 Key: BIGTOP-1080
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1080
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Debian, General, RPM
>    Affects Versions: 0.7.0
>            Reporter: Mark Grover
>            Assignee: Mark Grover
>             Fix For: 0.7.0
>
>         Attachments: BIGTOP-1080.1.patch
>
>
> I think it would be a good idea to convert our /usr/bin scripts to be 
> alternatives (i.e. symlinks) instead of flat files just like our 
> configuration directories (/etc/component/config). It would make the package 
> deployment more flexible for our users.

--
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

Reply via email to