...
Please comment on issues in JIRA, making your concerns known. Please also vote for issues that are a high priority for you.
...
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 can be made in the comments.
Here are some several Hive JIRA issues that you can use as examples:
- bug: HIVE-8485, HIVE-8600, HIVE-9438, HIVE-11174
- new feature: HIVE-6806, HIVE-7088, HIVE-11103
- improvement: HIVE-7685, HIVE-9858, HIVE-10165
- task:
- test: HIVE-8601, HIVE-10637
- wish: HIVE-4563, HIVE-10427
- task: HIVE-7111,new feature: HIVE-70887789
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 issuesMany examples of uncommitted issues are available in the "Added recently" list on the issues panel.
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.
...