...
Please refrain from editing descriptions and comments if possible, as edits spam the mailing list and clutter JIRA's "All" display, which is otherwise very useful. Instead, preview descriptions and comments using the preview button (icon below the comment box) before posting them. Keep descriptions brief and save more elaborate proposals for comments, since descriptions are included in JIRA's automatically sent messages. If you change your mind, note this in a new comment, rather than editing an older comment. The issue should preserve this history of the discussion.
To open a JIRA issue, click the Create button on the top line of the Hive summary page or any Hive JIRA issue. When in doubt about how to fill in the form, take a look at what was done for other issues. Note that Fix Version/s should not be tagged until an issue is closed, and then, it is tagged by the committer closing it to indicate which version the fix went into. Fix Version/s is not used to request which version it should go into – you can put such requests in the comments.
Here are some Hive JIRA issues that you can use as examples:
- bug: HIVE-8485,
- improvement: HIVE-10165
- task:
- new feature: HIVE-7088
For examples that have not yet been committed, see the activity stream at the bottom of the Hive summary page or the list of most recent issues.
Generating Thrift Code
Some portions of the Hive code are generated by Thrift. For most Hive changes, you don't need to worry about this, but if you modify any of the Thrift IDL files (e.g. metastore/if/hive_metastore.thrift and service/if/hive_service.thrift), then you'll also need to regenerate these files and submit their updated versions as part of your patch.
...