Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Blocker Blocker
    • Resolution: Unresolved
    • Affects Version/s: 0.7.0
    • Fix Version/s: 0.8.0
    • Component/s: General
    • Labels:
      None

      Description

      Recently, more and more Linux distributions started to package bits and piece of the Bigtop stack natively. This leads to package name conflicts and also potentially file-name conflicts. Bigtop needs to figure out a way of co-existing with these.

      More here: http://mail-archives.apache.org/mod_mbox/bigtop-dev/201309.mbox/%3CCA%2BULb%2BvO8NSA_hnbg8RhWV8-boCe03NcELDAE8n19_%2B2c-oppA%40mail.gmail.com%3E

      There are no Sub-Tasks for this issue.

        Activity

        Hide
        Sean Mackrory added a comment -

        +1 - I like that better than the bigtop- prefix, as even though we do that with other components already, they're only components that are included as common dependencies - not as components we actually want for their own sake.

        Show
        Sean Mackrory added a comment - +1 - I like that better than the bigtop- prefix, as even though we do that with other components already, they're only components that are included as common dependencies - not as components we actually want for their own sake.
        Hide
        Mark Grover added a comment -

        Thanks all! I will take care of Spark.

        Show
        Mark Grover added a comment - Thanks all! I will take care of Spark.
        Hide
        Bruno Mahé added a comment -

        +1.
        I guess we only need a patch or two

        Show
        Bruno Mahé added a comment - +1. I guess we only need a patch or two
        Hide
        Peter Linnell added a comment -

        +1 Sounds completely sensible.

        Show
        Peter Linnell added a comment - +1 Sounds completely sensible.
        Hide
        Roman Shaposhnik added a comment -

        +1 to the proposal.

        Show
        Roman Shaposhnik added a comment - +1 to the proposal.
        Hide
        Mark Grover added a comment -

        For spark in Bigtop, there are 3 packages - spark, spark-master and spark-worker. The 'spark' package contains all core bits and default configuration pertaining to Spark. The 'spark-master' and 'spark-worker' package contain init scripts for the Spark worker and master services.

        While I think it's still a good idea to solve this naming conflict problem for all bigtop packages generally, in Spark's case in particular, I personally prefer renaming the 'spark' package to 'spark-core' package since that's closer to what it delivers anyways. Whatever decision we make about all packages for naming conflicts (like say prefixing all bigtop packages with 'bigtop-') will apply to spark as well, just like it would apply to any other bigtop package but perhaps, we should solve this immediate conflict by renaming the 'spark' package to 'spark-core' which in my opinion, is a better name anyways. Due of this conflict, it's not possible to install spark on Debian based systems today.

        What do you folks think?

        Show
        Mark Grover added a comment - For spark in Bigtop, there are 3 packages - spark, spark-master and spark-worker. The 'spark' package contains all core bits and default configuration pertaining to Spark. The 'spark-master' and 'spark-worker' package contain init scripts for the Spark worker and master services. While I think it's still a good idea to solve this naming conflict problem for all bigtop packages generally, in Spark's case in particular, I personally prefer renaming the 'spark' package to 'spark-core' package since that's closer to what it delivers anyways. Whatever decision we make about all packages for naming conflicts (like say prefixing all bigtop packages with 'bigtop-') will apply to spark as well, just like it would apply to any other bigtop package but perhaps, we should solve this immediate conflict by renaming the 'spark' package to 'spark-core' which in my opinion, is a better name anyways. Due of this conflict, it's not possible to install spark on Debian based systems today. What do you folks think?
        Hide
        Andrew Purtell added a comment -

        +1

        Show
        Andrew Purtell added a comment - +1
        Hide
        Konstantin Boudnik added a comment -

        Sounds good to me!

        Show
        Konstantin Boudnik added a comment - Sounds good to me!
        Hide
        Sean Mackrory added a comment -

        Shall we start with Spark? Other than Avro, which is not committed, it's the only one I know of that has a specific conflict right now. I quite like the idea of a bigtop- prefix (which we already do with some secondary components in our stack like jsvc and tomcat. If there are no objections I'll submit a patch to rename the spark* packages to bigtop-spark*.

        Show
        Sean Mackrory added a comment - Shall we start with Spark? Other than Avro, which is not committed, it's the only one I know of that has a specific conflict right now. I quite like the idea of a bigtop- prefix (which we already do with some secondary components in our stack like jsvc and tomcat. If there are no objections I'll submit a patch to rename the spark* packages to bigtop-spark*.

          People

          • Assignee:
            Roman Shaposhnik
            Reporter:
            Roman Shaposhnik
          • Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:

              Development