Hi team,
I've reviewed the open tickets and identified those most important for the Hive 4.2.0 release. To make it easier to track, I’ve created JIRA filters for each category: - Regressions <https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20and%20(affectedVersion%20in%20(4.0.0%2C%204.1.0%2C%204.0.1)%20or%20affectedVersion%20is%20EMPTY)%20and%20type%20%3D%20Bug%20and%20(priority%20in%20(Major%2C%20High%2C%20Critical%2C%20Blocker)%20or%20labels%20in%20(hive-4.2.0-must))%20and%20labels%20in%20(regression)%20and%20resolution%20%3D%20Unresolved%20and%20created%20%3E%20-400d%20order%20BY%20updated%20DESC> - tickets that exist in 4.1.0, but not in prior releases. - *Tickets lacking reproduction steps* <https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20and%20(affectedVersion%20in%20(4.0.0%2C%204.1.0%2C%204.0.1)%20or%20affectedVersion%20is%20EMPTY)%20and%20type%20%3D%20Bug%20and%20(priority%20in%20(Major%2C%20High%2C%20Critical%2C%20Blocker)%20or%20labels%20in%20(hive-4.2.0-must))%20and%20labels%20in%20(needs-repro-steps)%20and%20resolution%20%3D%20Unresolved%20and%20created%20%3E%20-400d%20order%20BY%20updated%20DESC>– repro steps are needed to determine whether they are regressions. - *4.2.0-must <https://issues.apache.org/jira/issues/?jql=labels%20%3D%20hive-4.2.0-must>* – tickets that were labeled as 4.2.0-must. I kindly request your help in the following: - For tickets already assigned: please review and fix them if possible for this release. If a ticket cannot be resolved at this time, please share the reason so we can track it properly. - For unassigned tickets: please review and consider picking up any that you can help with. - For tickets missing reproduction steps: I’ve already pinged the reporters and am waiting for their updates. Thank you very much for your support in ensuring a smooth and timely release! Best regards, Dmitriy Fingerman
