Re: Re: Reg: Discussion on removal of deprecated APIs in the HMS thrift interface

2023-06-01 Thread Stamatis Zampetakis
Zhihua brought up a good point. Yes if it was introduced in 4.0.0-alpha and then was deprecated we can remove it. On Thu, Jun 1, 2023 at 1:00 PM Attila Turoczy wrote: > > +1 from me as well. Let's clean it up. Still, because we have struggled > with the data correctness issue, we have time to int

Re: Re: Reg: Discussion on removal of deprecated APIs in the HMS thrift interface

2023-06-01 Thread Attila Turoczy
+1 from me as well. Let's clean it up. Still, because we have struggled with the data correctness issue, we have time to introduce these changes. If won't fit then won't be a problem as well, as the next release will contain it. As I wrote earlier, as the 4.0 goes out I want to help to have regular

Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-01 Thread Attila Turoczy
Ayush just told me, the mailing list does not support images. It is a very sad world :-( Previous meme: https://imgflip.com/i/7nuzql On Thu, Jun 1, 2023 at 11:46 AM Attila Turoczy wrote: > OK. Then let's go with beta. Please start. (if not started already) a vote > for a release. > > I think we

Re:Re: Reg: Discussion on removal of deprecated APIs in the HMS thrift interface

2023-06-01 Thread dengzhhu653
Hi Thanks Sai for driving this, the request based API makes sense to me. For the removal of deprecated API: a) +1 if it is marked as deprecated in 3.x; b) If the API is introduced after 4.0.0-alpha, but tend to become obsolete in 4.x GA, I think we can remove it as well. Thanks, Zhihua. At 2

Re: Reg: Discussion on removal of deprecated APIs in the HMS thrift interface

2023-06-01 Thread Ayush Saxena
+1 to what Stamatis said, if it is there in 3.X we can explore their removal, else let them go in 4.x GA release and we can remove then in the subsequent release -Ayush > On 01-Jun-2023, at 3:08 PM, Stamatis Zampetakis wrote: > > Hello, > > Ideally we should deprecate APIs in one release an

Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-01 Thread Attila Turoczy
OK. Then let's go with beta. Please start. (if not started already) a vote for a release. I think we should have a more frequent release cadence. The community needs it, we need this, also without frequent release nobody will believe this project is healthy. I know the first will be the hardest, b

Re: Reg: Discussion on removal of deprecated APIs in the HMS thrift interface

2023-06-01 Thread Stamatis Zampetakis
Hello, Ideally we should deprecate APIs in one release and remove them in a subsequent major release. If the HMS deprecations were added in Hive 3.X then I am ok removing them now. Otherwise it is not really that we will remove deprecated APIs but we will remove regular APIs without any notice. B

Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-01 Thread Stamatis Zampetakis
+1 from me as well. Any alpha or beta name should be fine I have no strong preferences. On Wed, May 31, 2023, 2:30 PM László Bodor wrote: > Hi! > > +1 for creating a new release before GA in the presence of possible > correctness problems. I'm not 100% sure about alpha or beta, I'm fine with > a

Re: Move to JDK-11

2023-06-01 Thread Stamatis Zampetakis
Hey everyone, If we claim that Hive supports a certain JDK then we should compile and run tests with it. The more JDKs we can support the better for everyone but this comes at a cost (resources mostly). We should have a precommit run for every supported JDK (frequency to be determined once per da