I think it's fine to backport this and do a release. Are we sure that's enough to make it run on JDK11? As noted in the bug there isn't an umbrella issue to make it JDK11 compatible. I don't know if anyone has tested Hive 2 on JDK11 or not.
Are you available to do the backport? If so, and we don't find any other JDK11 related issues, I can create a 2.3.6 release once you're done. Alan. On Thu, Aug 8, 2019 at 6:23 PM Hyukjin Kwon <[email protected]> wrote: > Hi all, > > > I am from Spark dev and had a question about feasibility of porting > HIVE-21584 > and minor release 2.3.x. > > Just to share full context, please take a look at > > https://issues.apache.org/jira/browse/HIVE-21639?focusedCommentId=16822802&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16822802 > TL;DR: with Hive 2.3.5, Spark is now very close to get through the > complicated > situation that has been locked for years. Thank you Yuming Wang and Alan > Gates > - it would have been impossible without all the efforts from you guys. > > > One problem found lately though, > Spark is trying to support JDK 11 but this seems blocked by HIVE-21584. > So, I and Spark > community are trying to find a way to get through. > > Firstly, I (and presumably some Spark community guys) thought Spark should > find its > own workaround or try to upgrade Hive to 4.0.0 in the upcoming release. > This possibility was checked and seems difficult. > It was already pretty a radical change to upgrade Hive 1.2.x to 2.3.5, > seems it's difficult to target upgrade to 4.0.0 in this release at this > moment. > > I understand HIVE-21584 was fixed in 4.0.0 and it might be difficult to > backport > through branch-3.x and 2.x; however, wanted to at least ask and now because > I thought porting HIVE-21584 into Hive 2.3.x branch is an option that > needs the > minimised efforts to permanently resolve all related issues, apparently, > blocked > for multiple years .. > > > Thanks for consideration in advance. >
