Hi Cheng, I had started the poll for deprecating Hive on Spark but we decided not to go with it. Kindly refer to the mail threads for the reason.
Thanks, Aman. ________________________________ From: Cheng Pan <cheng...@apache.org> Sent: Monday, April 24, 2023 6:52 PM To: dev@hive.apache.org <dev@hive.apache.org> Subject: [EXTERNAL] RE: Branch-3 backports and build stability [You don't often get email from cheng...@apache.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] +1 for removing Hive on Spark from 3.2. Hive on Spark has been out of maintenance for a long time, the related tests are broken in branch-2.3, and branch-3.1. The known Hadoop releases including CDP[1] HDP[2] MR3[3] removed the HoS in Hive3 too. Thus, I suppose HoS is deprecated since Hive 2.3 in fact, users won't be surprised if we remove it in 3.2. [1] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.cloudera.com%2Fcdp-private-cloud-upgrade%2Flatest%2Fupgrade-cdh%2Ftopics%2Fcdp-data-migration-hive-on-spark.html&data=05%7C01%7Crajaman%40microsoft.com%7Cee617b65454b4843387f08db44c701de%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638179393858255143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NMwd8yYlFePRyGAOBBZQCcPrVLJUkOPam12NTivMt0s%3D&reserved=0<https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/upgrade-cdh/topics/cdp-data-migration-hive-on-spark.html> [2] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.cloudera.com%2Ft5%2FSupport-Questions%2FDoes-Hive-on-Spark-supported-in-HDP-3-x%2Fm-p%2F280189&data=05%7C01%7Crajaman%40microsoft.com%7Cee617b65454b4843387f08db44c701de%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638179393858255143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lrUqr61V5n67Mm0OVM174g3Kl21ZxkJqVFrYzO0y71Q%3D&reserved=0<https://community.cloudera.com/t5/Support-Questions/Does-Hive-on-Spark-supported-in-HDP-3-x/m-p/280189> [3] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmr3project%2Fhive-mr3%2Fcommit%2F7f03e754953fbf47bfca141a19ce6cf257c70110&data=05%7C01%7Crajaman%40microsoft.com%7Cee617b65454b4843387f08db44c701de%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638179393858255143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FHwduobY9icOvy%2BMA5MXdREyoCa%2BtlpyY4DN6pDhGi8%3D&reserved=0<https://github.com/mr3project/hive-mr3/commit/7f03e754953fbf47bfca141a19ce6cf257c70110> On 2023/02/07 11:08:35 Stamatis Zampetakis wrote: Hi all, The build in branch-3 is not yet green; there are ~25 test failures. It is a common practice that we shouldn't push changes on top of a broken build unless they are addressing test failures. Some people (mainly Aman Raj, Chris Nauroth, and Laszlo Bodor) are working hard to stabilize the build for quite some time now. If you want to help out then start by reviewing, merging, and fixing things around test failures. It's not yet the time to bring new features, upgrades, bugs, etc., in branch-3. I would encourage committers to not approve such changes till we get back to a stable branch. Best, Stamatis Thanks, Cheng Pan
