Re: Start releasing the master branch

Thanks for pushing this forward Peter! Being the RM for this huge release was not an easy task. Let's now aim for smaller and much more frequent releases. Personally, I would prefer to keep the alpha-X suffix for a while so I would opt for 4.0.0-alpha-2-SNAPSHOT for the next iteration. Best, Sta

Re: Start releasing the master branch

Thanks to everyone who helped to create the Hive 4.0.0-alpha-1 release! I really hope this helps our users to try out our previously unreleased new features. As a last step of the release process, I will update the versions for the next release. I would like to ask your opinion about the next vers

Re: Start releasing the master branch

Hi Team, If everyone agrees, tomorrow I would like to start the release process for 4.0.0-alpha-1. Is there any outstanding blocker jira that you know of? Thanks, Peter > On 2022. Mar 9., at 17:01, Stamatis Zampetakis wrote: > > I just logged HIVE-26022 [1] which seems to be another potent

Re: Start releasing the master branch

I just logged HIVE-26022 [1] which seems to be another potential blocker for 4.0.0-alpha-1. Best, Stamatis [1] https://issues.apache.org/jira/browse/HIVE-26022 On Thu, Mar 3, 2022 at 3:54 PM Peter Vary wrote: > Hi Team, > > Here is our status: > We collected the blocker tickets and marked them

Re: Start releasing the master branch

Hi Team, Here is our status: We collected the blocker tickets and marked them with fixVersion 4.0.0-alpha-1: https://issues.apache.org/jira/issues/?filter=-1&jql=project%20%3D%20HIVE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.0.0-alpha-1

Re: Start releasing the master branch

Will continue this discussion on the #hive ASF slack. If you are interested, please join. We will do updates here time-to-time, so the ones who are not using slack can participate that way. > On 2022. Mar 2., at 11:11, Peter Vary wrote: > > Good idea Zoltan, joined the channel. > I would like

Re: Start releasing the master branch

Good idea Zoltan, joined the channel. I would like to scope reasonably small, so I agree with focusing on 4.0.0-alpha-1 > On 2022. Mar 2., at 11:01, Zoltan Haindrich wrote: > > Hey, > > regarding 4.0.0 / 4.0.0-alpha-1 target/fix versions in the jira: > * I think we should change all already re

Re: Start releasing the master branch

Hey, regarding 4.0.0 / 4.0.0-alpha-1 target/fix versions in the jira: * I think we should change all already resolved tickets with fix version 4.0.0 to have fix version 4.0.0-alpha-1 ** this could be postponed until we are actually releasing the thing as I think everyone committing to the master

Re: Start releasing the master branch

Agree with Peter, creating JIRAs is the way to go. Putting the appropriate priority (e.g., BLOCKER) and version (4.0.0 or 4.0.0-alpha-1) when creating the JIRA should be enough to keep us on track. I am mentioning both 4.0.0 and 4.0.0-alpha-1 because eventually I think we are gonna move everything

Re: Start releasing the master branch

Hi Team, Could we create tickets for the issues? I think it would be good to collect the issues/potential blockers in the jira instead of having a complicated mail thread. If we set the target version to 4.0.0-alpha-1, then we can easily use the following filter to see the status of the tasks:

Re: Start releasing the master branch

Hello Alessandro, For the latest commit, loading ORC tables fails (with the log message shown below). Let me try to find a commit that introduces this bug and create a JIRA ticket. --- Sungwoo 2022-03-02 05:41:56,578 ERROR [Thread-73] exec.StatsTask: Failed to run stats task java.io.IOExcep

Re: Start releasing the master branch

I just logged HIVE-25995 [1]; this might be another blocker for 4.0.0-alpha-1. If that's not the case feel free to change the priority of the ticket. [1] https://issues.apache.org/jira/browse/HIVE-25995 On Tue, Mar 1, 2022 at 7:29 PM Alessandro Solimando < alessandro.solima...@gmail.com> wrote:

Re: Start releasing the master branch

Hi Sungwoo, last time I tried to run TPCDS-based benchmark I stumbled upon a similar situation, finally I found that statistics were not computed, so CBO was not kicking in, and the automatic retry goes with CBO off which was failing for something like 10 queries (subqueries cannot be decorrelated,

Re: Start releasing the master branch

Hello Hive team, I wonder if anyone in the Hive team has tried the TPC-DS benchmark on the master branch recently. We occasionally run TPC-DS system tests using the master branch, and the tests don't succeed completely. Here is how our TPC-DS tests proceed. 1. Compile and run Hive on Tez (not H

Re: Start releasing the master branch

Hey, Great to hear that we are on the same side regarding these things :) For around a week now - we have nightly builds for the master branch: http://ci.hive.apache.org/job/hive-nightly/12/ I think we have 1 blocker issue: https://issues.apache.org/jira/browse/HIVE-25665 I know about one more

Re: Start releasing the master branch

Release for 3.1.3 is underway. Initial set of targetted backports are complete. I will follow the remaining steps to have a build soon. Would be nice to release at a regular cadence. On Tue, Feb 22, 2022 at 6:18 AM Peter Vary wrote: > I would vote for 4.0.0-alpha-1 or similar for all of the com

Re: Start releasing the master branch

I would vote for 4.0.0-alpha-1 or similar for all of the components. When we have more stable releases I would keep the 4.x.x schema, since everyone is familiar with it, and I do not see a really good reason to change it. Thanks, Peter > On 2022. Feb 10., at 3:34, Szehon Ho wrote: > > +1 tha

Re: Start releasing the master branch

+1 that would be awesome to see Hive master released after so long. Either 4.0 or 4.0.0-alpha-1 makes sense to me, not sure how we would pick any 3.x or calendar date (which could tend to slip and be more confusing?). Thanks in any case to get the ball rolling. Szehon On Wed, Feb 9, 2022 at 4:55

Re: Start releasing the master branch

Hey, Thank you guys for chiming in; versioning is for sure something we should get to some common ground. Its a triple problem right now; I think we have the following things: * storage-api ** we have "2.7.3-SNAPSHOT" in the repo *** https://github.com/apache/hive/blob/0d1cc7c5005fe47759298

Re: Start releasing the master branch

Hi All! A purely technical question: what will the SNAPSHOT version become after releasing Hive 4.0.0? I think this is important, as it defines and reflects the future release plans. Currently, it's 4.0.0-SNAPSHOT, I guess it's since Hive 3.0 + branch-3. Hive is an evolving and super-active proje

Re: Start releasing the master branch

Hello everyone, thank you for starting this discussion. I agree that releasing the master branch regularly and sufficiently often is welcome and vital for the health of the community. It would be great to hear from others too, especially PMC members and committers, but even simple contributors/fo

Re: Start releasing the master branch

Hello, Thanks for starting the discussion Zoltan. I strongly believe that it is important to have regular and often releases otherwise people will create and maintain separate Hive forks. The latter is not good for the project and the community may lose valuable members because of it. Going forw

Start releasing the master branch

Hey All, We didn't made a release for a long time now; (3.1.2 was released on 26 August 2019) - and I think because we didn't made that many branch-3 releases; not too many fixes were ported there - which made that release branch kinda erode away. We have a lot of new features/changes in the c