Bigtop
  1. Bigtop
  2. BIGTOP-303

Rename Bigtop packages to reflect TLP status of packaged projects

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.2.0
    • Fix Version/s: 0.3.0
    • Component/s: general
    • Labels:
      None

      Description

      All of the projects packaged by Bigtop have had TLP status for quite some time. It would be nice to reflect that in the package names. Here's what needs to be renamed:

      hadoop-0.20 -> hadoop
      hadoop-hbase -> hbase
      hadoop-zookeeper -> zookeeper
      hadoop-hive -> hive
      hadoop-pig -> pig

      Please chime in on ramifications of this rename. My cursory check on http://pkgs.org didn't reveal any naming conflicts with the proposed package names.

        Activity

        Roman Shaposhnik created issue -
        Hide
        Roman Shaposhnik added a comment -

        This is, perhaps, specific to Hadoop 0.23 branch, but it would be extremely nice to split Hadoop packaging into HDFS, YARN and MAPREDUCE

        Show
        Roman Shaposhnik added a comment - This is, perhaps, specific to Hadoop 0.23 branch, but it would be extremely nice to split Hadoop packaging into HDFS, YARN and MAPREDUCE
        Hide
        Bruno Mahé added a comment -

        +1 on the rename

        +1 On Apache Bigtop helping Apache Hadoop itself to have better separation between its different parts. But this is not something Apache Bigtop can tackle itself. Patches would have to be made upstream as well as convince upstream.of that benefit
        I would rather separate this issue into another ticket so the issue of renaming projects to reflect their TLP status could be tackled by non-commiter looking for an easy ticket to start with.

        Show
        Bruno Mahé added a comment - +1 on the rename +1 On Apache Bigtop helping Apache Hadoop itself to have better separation between its different parts. But this is not something Apache Bigtop can tackle itself. Patches would have to be made upstream as well as convince upstream.of that benefit I would rather separate this issue into another ticket so the issue of renaming projects to reflect their TLP status could be tackled by non-commiter looking for an easy ticket to start with.
        Roman Shaposhnik made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Roman Shaposhnik made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Gavin made changes -
        Workflow no-reopen-closed, patch-avail [ 12645331 ] patch-available, re-open possible [ 12666053 ]
        Roman Shaposhnik made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        24d 22h 1m 1 Roman Shaposhnik 04/Jan/12 17:55
        In Progress In Progress Resolved Resolved
        13s 1 Roman Shaposhnik 04/Jan/12 17:55
        Resolved Resolved Closed Closed
        173d 22h 3m 1 Roman Shaposhnik 26/Jun/12 16:58

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development