Hi! Given that TEZ-4577 fixes an issue, it would make sense to let Tez 0.10.5 happen sooner rather than later. Unfortunately, as Tez 0.10.4 introduced some api changes too (TEZ-4548), users cannot easily revert to 0.10.3. I'm wondering how much we can block a hive release because of this: making a new Tez release typically involves approving some already pending PRs to maintain project health (in 1-2 weeks), and then release + approve (normally during Jan 2025).
Regards, Laszlo Bodor Sungwoo Park <glap...@gmail.com> ezt írta (időpont: 2024. dec. 18., Sze, 13:17): > Hi, > > TEZ-4577[2] fixes a serious performance bug, which was introduced in the > latest release of Tez and can affect production queries. For example, > TPC-DS benchmark is affected by this bug. So, I also agree with Butao that > the next release of Hive should be packaged with a new version of Tez with > TEZ-4577. > > Thanks, > > --- Sungwoo Park > > On Sun, Dec 15, 2024 at 6:11 PM Butao Zhang <butaozha...@163.com> wrote: > >> Hi dev, >> >> As we discussed in this thread[1], we are planning to release >> the Apache Hive 4.1.x version. IMO, Many of Tez commits are coupled with >> Hive development. Therefore, should we release a new Tez version that >> matches the Hive 4.1.x? >> BTW, i saw TEZ-4577[2] which fixed a major bug, has landed >> master branch. I think this issue should be included a new vesion ASAP. >> >> wdyt? Thanks. >> >> [1] https://lists.apache.org/thread/106b045wh5g2bhy81o16vpk7y25t13jc >> [2] https://github.com/apache/tez/pull/367 >> >> >> Thanks, >> Butao Zhang >> >
