Versions Compared

Old Version 71

changes.mady.by.user Lefty Leverenz

Saved on

compared with

New Version 72

changes.mady.by.user Lefty Leverenz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: trivial edits: change double spaces to singles

...

This checklist tells you how to create accounts and obtain permissions needed by Hive contributors.  See See the Hive website for additional information.

  •  Create an Apache Software Foundation JIRA account if you do not already have one: Sign Up for JIRA.
    • The ASF JIRA system dashboard is here.
    • The Hive JIRA is here. 
  •  To review patches for JIRA tickets, use the Review Board.  If If you need an account, register here.  See See Review Process below for more information.
    • All Hive patches posted for review are listed here.
    • Individual JIRA tickets provide a link to the issue on the review board when a review request has been made.
    • For simple reviews, you can just read the patch attached to the JIRA ticket and post a comment.
  •  To contribute to the Hive wiki, follow the instructions in About This Wiki.
  •  To edit the Hive website, follow the instructions in How to edit the website.
  •  Join the Hive mailing lists to receive email about issues and discussions.

...

  • All public classes and methods should have informative Javadoc comments.
    • Do not use @author tags.
  • Code should be formatted according to Sun's conventions, with two exceptions:
    • Indent two (2) spaces per level, not four (4).
    • Line length limit is 100 chars, instead of 80 chars.
  • Contributions should not introduce new Checkstyle violations.
    • Check for new Checkstyle violations by running mvn checkstyle:checkstyle-aggregate, and then inspect the results in the target/site directory.
    • If you use Eclipse you should install the eclipse-cs Checkstyle plugin. This plugin highlights violations in your code and is also able to automatically correct some types of violations.
  • Contributions should pass existing unit tests.
  • New unit tests should be provided to demonstrate bugs and fixes. JUnit is our test framework:
    • You must implement a class that extends junit.framework.TestCase and whose class name starts with Test.
    • Define methods within your class whose names begin with test, and call JUnit's many assert methods to verify conditions; these methods will be executed when you run mvn test.
    • You can run all the unit tests with the command mvn test, or you can run a specific unit test with the command mvn test -Dtest=<class name without package prefix> (for example:   mvn test -Dtest=TestFileSystem).

...

As of June 2015, Hive has two "main lines", master and branch-1.  

All new feature work and bug fixes in Hive are contributed to the master branch. As of June 2015, releases from master are numbered 2.x.  2 The 2.x versions are not necessarily backwards compatible with 1.x versions.

...

Hadoop 1.x is no longer supported in Hive's master branch.  There There is no need to specify a profile for most Maven commands, as Hadoop 2.x will always be chosen.

...

If the name of your patch conforms to the naming convention shown above, the automated testing system will run precommit tests and post the results as a JIRA comment from Hive QA. The results give advisory +1 or -1 votes (SUCCESS or ERROR) based on whether all of the tests executed successfully and, more recently, whether existing tests are modified or new tests are included in the patch to cover the code changes.  For For examples, see the Hive QA comments on HIVE-9534 and HIVE-11752. Note that sometimes tests fail for reasons unrelated to the patch.

...

To retest a patch, you can cancel it and then resubmit it.  If If you do not cancel before resubmitting, Hive QA will ignore it.

To prevent precommit testing, include the case-sensitive phrase NO PRECOMMIT TESTS in the Description section of the JIRA issue. You can remove it later as needed.  For For examples, see HIVE-5289, HIVE-7343, and HIVE-7375.

...

...