THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
This page tracks the jiras requested for the release hive-0.14.
| Category | JIRA | Description | Status | Requestor |
|---|---|---|---|---|
| Improvement | HIVE-5690 | Support subquery for single sourced multi query | Pending review | Navis Ryu |
| Security | HIVE-6799 | HiveServer2 needs to map kerberos name to local name before proxy check | In progress | Vaibhav Gumashta |
| Improvement | HIVE-7946 | CBO: Merge CBO changes to Trunk | Patch Available | Ashutosh Chauhan |
| Metastore | HIVE-7689 | Enable Postgres as METASTORE back-end | Patch Available | Damien Carol |
The query I am using for tracking:
| Panel | ||
|---|---|---|
| ||
| project = Hive AND (affectedVersion = 0.14.0 OR fixVersion = 0.14.0) AND (priority = Critical OR priority = Blocker) AND (status = "Patch Available" OR status = "In Progress" OR status = Open OR status = "Documentation/Testcases Required" or status = "Documentation Required") |
I have removed the table that was used for tracking earlier. I have shared the query above that I am using to find jiras that need to be part of 0.14. I am also sharing below the instructions for getting jiras into 0.14 that I sent in an earlier email on the mailing list:
1. I am going to monitor all issues marked as blockers/criticals on a nightly basis. The list on the wiki is going to go away once I triage it for things like exceptions, failures etc. and feature requests that were already accepted.
2. If a developer feels that an issue marked as blocker is not really one, we can chat on the jira. Alternatively, please set the priority to blocker if you want a jira to be fixed in 0.14 so that I can check on it and decide the priority. If I think it is not a blocker, I will lower the priority after discussing on the jira.
3. Jira is going to be a single source of truth.
4. Once the blocker list goes to 0, I am going to create an RC.
5. Patches for blocker jiras are going to need to be double committed to both trunk and 0.14 by the one committing the jiraPlease let me know if I have missed any jiras. The rest of the jiras specified on the mailing list seem to have been checked in.