and email of the author (e.g.,
Co-authored-by: Marton Bod )
B5. If the reviewer is different from committer (or merge via GitHub UI)
use "Reviewed-by:" followed by the name and email of the reviewer (e.g.,
Reviewed-by: Stamatis Zampetakis )
B6. Use "Co-authored-by"/"Reviewed-
ft.com> wrote:
> Hi @Stamatis Zampetakis , @David ,
>
>
>
> Our current implementation using DateTimeFormatter is not backward
> compatible and it leads to migration issues.
>
> One of our customer who have this use-case where we don’t have a better
> options to m
gt; > <
> https://mail-archives.apache.org/mod_mbox/calcite-dev/202109.mbox/%3ccafqnwdzys+gemeeevhreggjedpmjn5bc4bvecdusgrtcykv...@mail.gmail.com%3e
> >
> > which
> > led to consensus.
> >
> > Best regards,
> > Alessandro
> >
> > On Fri, 24 Sept 2
Hi Sebastian,
Thanks for bringing this up.
The ASF is rather explicit about category-x licenses [1] and LGPL is part
of them; they are not allowed neither in the source nor in the convenience
binary releases [2].
They can be present in the repo, used during the build, but must not be
part of the
Hi all,
Currently, we have some (MariadDB, MySQL, Oracle) Category-X [1] JDBC
drivers in some parts of the project. Sometimes they are included using the
dependency section with test and some others by relying on
download-maven-plugin [2].
Using test scope is kind of OK but it comes with the risk
ver...if that comes back after these changes we may ask to update the
> scanner because we only use it in test runtime.
>
> cheers,
> Zoltan
>
> On 11/10/21 11:59 AM, Stamatis Zampetakis wrote:
> > Hi all,
> >
> > Currently, we have some (MariadDB, MySQL, Oracle) Cate
hese bugs). I still cannot fathom why
> someone
> >>>>> using
> >>>>>> oozie would want a fat jar of hive (as opposed to hive server or
> >>>>> hivejdbc)
> >>>>>> . If I had to do that, i would just use shell action. You all
Congrats Zhihua! Excellent list of contributions in many areas, well
deserved.
Best,
Stamatis
On Thu, Jan 20, 2022 at 1:38 PM Peter Vary
wrote:
> Congratulations!
>
> > On 2022. Jan 20., at 8:58, Zoltan Haindrich wrote:
> >
> > Hey all,
> >
> > Apache Hive's Project Management Committee (PMC)
Hi team,
Almost one year has passed since the last exchange in this discussion and
if I am not wrong there has been no effort to revive Hive-on-Spark. To be
more precise, I don't think I have seen any Spark related JIRA for quite
some time now and although I don't want to rush into conclusions, th
Hi all,
This email is an attempt to converge on which Hive/Tez/MR properties
someone should use in order to schedule a compaction on specific queues.
For those who are not familiar with how queues are used the YARN capacity
scheduler documentation [1] gives the general idea.
Using specific queues
Hi all,
In the current master, there are two approaches for performing compactions
of ACID tables [1]:
* using hard-coded MapReduce jobs (aka. CompactorMR [2]);
* using HiveQL queries (aka. QueryCompactor [3]) and delegating the
execution to the underlying engine (MR, Tez, other);
The motivation
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
t part of the query based
> compactor (and they need to be)?
>
> I’m pretty sure QB compaction does not yet honor the “WITH OVERWRITE
> TBLPROPERTIES” clause in an ALTER TABLE… COMPACT… statement. This could be
> something to add in the future.
>
> I agree that documenting QB compaction
Welcome Ayush!
Excellent contributions in many different components of Hive, very well
deserved!
Best,
Stamatis
On Mon, Feb 7, 2022 at 6:32 PM aasha medhi
wrote:
> Congratulations Ayush. Well deserved !!
>
> On Mon, Feb 7, 2022 at 10:36 PM Laszlo Pinter >
> wrote:
>
> > Congrats Ayush!
> >
>
It's great to see another ACID guru joining the PMC :)
Congrats Denys!
Best,
Stamatis
On Mon, Feb 7, 2022 at 6:56 PM Alessandro Solimando <
alessandro.solima...@gmail.com> wrote:
> Congratulations Denys! :)
>
> On Mon, 7 Feb 2022 at 18:37, Pravin Sinha wrote:
>
> > Congrats, Denys !
> >
> > On
HIVE-25595 is currently not
> compatible with the new config as it was developed for the old
> compactor.mapred... property:
>
> https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/txn/compactor/CompactorUtil.java#L31
> This also needs to be handled
c which should be good enough for the discussion.
>
> R, Janos
>
>
> Stamatis Zampetakis ezt írta (időpont: 2022. febr.
> 7., H, 23:44):
>
>> Thanks Janos for the feedback.
>>
>> If I understand well your suggestion is support all
> release... :)
> > >>>>
> > >>>> cheers,
> > >>>> Zoltan
> > >>>>
> > >>>>
> > >>>>
> > >>>> On 2/9/22 10:23 AM, L?szl? Bodor wrote:
> > >>>>> Hi All!
&g
ber will
> >>>>>>> also suggest that the actual software is fully compatible - and
> >>> only
> >>>>>>> bugs are being fixed - which will not be true...
> >>>>>>>
> >>>>>>> I really like the
sues/?
> jql=project%20%3D%20hive%20and%20resolutiondate%20%20is%20empty%20and%20(fixVersion%20%20in%20(%274.0.0%27)%20or%20cf%5B12310320%5D%20%20in%20(%274.0.0%27))
>
> I think for faster communication regarding these things we could also
> utilize the #hive channel on the ASF slack - w
Hi Martijn,
Worth mentioning that the community is also actively working to get the
next major release out, namely 4.0.0-alpha-1, in the next few weeks.
After getting the first cut of 4.0.0 out we should discuss if we can
reasonably support older branches.
The history so far shows that all the de
I confirm what Pau said, the only supported JDK is 8. Upgrade to JDK 11 has
started [1] but was paused due to various problems. I don't know if anyone
is actively working on fixing this at the moment.
Best,
Stamatis
[1] https://issues.apache.org/jira/browse/HIVE-22415
On Thu, Mar 10, 2022 at 10:
Hello,
+1 to everything Peter said.
Moreover a few other things/reminders which could make our life easier.
No commits/merges over broken master.
If there is a non-flaky failure in master then whoever notices it first,
please create a JIRA and add any relevant info. This will notify everyone
th
; >> Hi,
> >>
> >> Could we keep a redirect page at the old place, or a CNAME resolution?
> >>
> >> Best,
> >> Adrian
> >>
> >> --
> >> 发件人:Stamatis Zampetakis
&g
wse/INFRA-20776
[2] https://issues.apache.org/jira/browse/INFRA-23007
[3] https://github.com/apache/hive/tree/master/docs
[4] https://github.com/apache/hive-site
On Tue, Mar 15, 2022 at 9:11 PM Stamatis Zampetakis
wrote:
> Hi,
>
> From the discussion in INFRA-20776, it seems
Hi Peter,
Many thanks for rolling out the RC and for resolving many of the blocker
issues that were remaining.
In general, it is a good practice to include the commit hash (which tags
the release) and the checksum hashes of the release artifacts [1] in the
vote email to minimize the chances of ma
tps://cwiki.apache.org/confluence/display/Hive/HowToRelease <
> https://cwiki.apache.org/confluence/display/Hive/HowToRelease> wiki page
> as well
>
> Thanks,
> Peter
>
> > On 2022. Mar 22., at 18:22, Stamatis Zampetakis
> wrote:
> >
> > Hi Peter,
> >
Thanks for pushing this forward Naveen.
I checked the released sources in apache-hive-3.1.3-src and they contain
modified LGPL files violating the ASF release policy.
The problem is the same reported under HIVE-25665. I think the fix
should be backported to branch-3 before moving forward with the
Ubuntu 20.04.4 LTS, jdk1.8.0_261, Apache Maven 3.6.3
* Checked signatures and checksums OK
* Checked diff between repo and release sources (diff -qr hive
apache-hive-4.0.0-alpha-1-src) OK
* Built from git tag (mvn clean install -DskipTests -Pitests) OK
* Built from release sources (mvn clean i
Hey Janos,
You brought up an interesting subject.
I haven't worked on the code around the authentication process so cannot
foresee the impact on the codebase but high level your idea seems
reasonable to me.
I would be favorable in such a change but I would definitely like to see
some tests and d
:
>
> > 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
> >
> >
> >
Ubuntu 20.04.4 LTS, jdk1.8.0_261, Apache Maven 3.6.3
* Checked signatures and checksums OK
* Checked for checkstyle modified LGPL files OK
* Checked for illegal licenses in release binaries (jars) using [1] OK
* Built from git tag (mvn clean install -DskipTests -Pitests) OK
* Built from relea
Ubuntu 20.04.4 LTS, jdk1.8.0_261, Apache Maven 3.6.3
* Checked signatures and checksums OK
* Checked for checkstyle modified LGPL files OK
* Checked for illegal licenses in release binaries (jars) using [1] OK
* Checked diff between repo and release sources (diff -qr hive
apache-hive-3.1.3-src
Hi all,
The current master has many critical bug fixes as well as important
performance improvements that are not backported (and most likely never
will) to the maintenance branches.
Backporting changes from master usually requires adapting the code and
tests in questions making it a non-trivial
sically agree on everything you
>> wrote.
>>
>> I just wanted to add that this kind of proposal might sound harsh,
>> because in many contexts upgrading is a complex process, but it's in
>> nobody's interest to keep release branches that are missing important
Apparently there is now a JIRA, HIVE-26226 [1], about removing jdk.tools so
let's continue the discussion there.
Best,
Stamatis
[1] https://issues.apache.org/jira/browse/HIVE-26226
On Thu, May 5, 2022 at 6:27 PM Alessandro Solimando <
alessandro.solima...@gmail.com> wrote:
> Hi again,
> actual
Will announce shortly.
>
>
> Naveen
>
> On Fri, Apr 8, 2022 at 3:32 AM Stamatis Zampetakis
> wrote:
>
> > Ubuntu 20.04.4 LTS, jdk1.8.0_261, Apache Maven 3.6.3
> >
> > * Checked signatures and checksums OK
> > * Checked for checkstyle modified LGPL files OK
>
Thanks Peter and Zoltan for starting this discussion. Apologies for the
delay but I had the impression that I already sent this email.
I definitely agree with the idea of having quarterly releases no matter
what they are called (alpha, beta, or other).
I wouldn't base the decision to move from al
Hi Simhadri,
Thanks for starting this discussion Simhadri.
I am cc'ing the user list as well so that we have a better idea if there
are any active users.
Personally I am not that familiar with the Druid module.
* Is it currently broken?
* Do we have active tests?
* Does it need significant effor
It's the first time that I see a spellchecker in action in the projects
that I contribute to so I can't formulate an opinion before I use it for
sometime.
Activating in every module or removing altogether may be a bit premature at
this stage.
I would suggest keeping things as they are right now an
Hi Guangming,
There was a recent discussion about EOL Hive releases [1] but it was not
conclusive.
Feel free to reopen that thread if you have some thoughts on the subject.
Best,
Stamatis
[1] https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s
On Sun, Jun 19, 2022 at 11:20 AM Guan
://cwiki.apache.org/confluence/display/HADOOP/EOL+%28End-of-life%29+Release+Branches
On Tue, May 10, 2022 at 2:51 PM Stamatis Zampetakis
wrote:
> Thanks everyone for sharing your thoughts. I am happy to see so many
> people involved in the discussion.
>
> I would say that the current 4.0.
Hi Alessandro,
Sonar integration will definitely help in improving cope quality and
preventing bugs so many thanks for pushing this forward.
I went over the PR and it is in good shape. I plan to merge it in the
following days unless someone objects.
We can tackle further improvements in follow up
n we introduce Sonar analysis and see what people
> think.
>
> Best regards,
> Alessandro
>
> On Tue, 9 Aug 2022 at 16:38, Stamatis Zampetakis
> wrote:
>
> > Hi Alessandro,
> >
> > Sonar integration will definitely help in improving cope quality and
>
Hi Rohan and team,
The work sounds exciting thanks for considering contributing back to the
community.
The design document didn't arrive cause attachements are not allowed in
many Apache lists.
Maybe as a first step it would be nice to share a link to a Google doc
where people can add comments a
Hi all,
It's great to see some effort in improving the website. The POC from
Simhadri looks really cool; I didn't check the content but I love the look
and feel.
Now regarding the current process for modifying and updating the website
there is some info in this relatively recent thread [1].
Movi
.
>>
>> I like the look and feel of the new website, and I agree with Stamatis
>> that having the website sources in the Hive repo, and automatically
>> publishing the site upon commits would be very beneficial.
>>
>> Best regards,
>> Alessandro
>>
&g
suggestions regarding the design and content of the website over there, for
>>> anything else we can always come back here if we are blocked on something,
>>> or if something more needs to be done in this context.
>>>
>>> -Ayush
>>>
>>> On 21-S
Hi all,
This is a small tip/reminder for everyone using JIRA.
It is very common and convenient to refer to other tickets by adding the
HIVE-X pattern in summary, description, and comments.
The pattern allows someone to navigate quickly to an older JIRA from the
current one but not the other
Hi everyone,
The past discussions around the version used in JIRA can be found in the
following threads [1, 2].
As Ayush mentioned there are ~3K resolved tickets with Fix Version 4.0.0
but most of them are also tagged with 4.0.0-alpha1 [3].
I can easily remove the 4.0.0 tag from those tickets an
)%20AND%20fixVersion%20in%20(4.0.0-alpha-2)
>
> Regards,
> Denys
>
> On Thu, Oct 20, 2022 at 11:26 AM Stamatis Zampetakis
> wrote:
>
> > Hi everyone,
> >
> > The past discussions around the version used in JIRA can be found in the
> > following threads [1,
VE/administer-versions?status=unreleased
>
> -Ayush
>
> On Thu, 20 Oct 2022 at 15:51, Stamatis Zampetakis
> wrote:
>
>> No script at all, I am just going to use the "Bulk Update" feature in
>> JIRA.
>>
>> I will wait 24h in case there are object
Thanks for putting this together Naveen!
The reports are usually for the whole quarter [1] so when describing
membership data, project activity, etc, we shouldn't restrict the info to
the last month.
Note that membership and project activity sections are somewhat incomplete.
Please check the inst
inging this up.
>
> On Fri, Oct 14, 2022 at 5:06 AM Stamatis Zampetakis
> wrote:
>
>> Hi all,
>>
>> This is a small tip/reminder for everyone using JIRA.
>>
>> It is very common and convenient to refer to other tickets by adding the
>> HIVE-X pa
-1 (non-binding)
Ubuntu 20.04.5 LTS, java version "1.8.0_261", Apache Maven 3.6.3
* Verified signatures and checksums OK
* Checked diff between git repo and release sources (diff -qr hive-git
hive-src) KO (among other *.iml files present in release sources but not in
git)
* Checked LICENSE, NOTIC
Hive PMC members can provide edit rights to the wiki.
@Naveen, Dennys, Adam: Can someone please give write privileges to Chris?
Best,
Stamatis
On Fri, Oct 28, 2022 at 8:41 AM Chris Nauroth wrote:
> Hi everyone,
>
> Regarding this page:
>
>
> https://cwiki.apache.org/confluence/display/hive/con
3c071d70cf62961dc90a251a0f45e47
> apache-hive-4.0.0-alpha-2-bin.tar.gz
> f2814aadeca56ad1d8d9f7797b99d1670f6450f68ff6cae829384c9c102cd7a9
> apache-hive-4.0.0-alpha-2-src.tar.gz
>
> Thanks,
> Denys
>
> On Fri, Oct 28, 2022 at 12:28 PM Stamatis Zampetakis
> wrote:
>
taking time to verify this RC!
> Unfortunately, we didn't get enough votes to go ahead with the release.
>
> Closing this vote as unsuccessful.
>
> Kind regards,
> Denys
>
> On Fri, Oct 28, 2022, 15:56 Stamatis Zampetakis wrote:
>
> > I think that having a proper NOT
Hey everyone,
It would be nice to have a new release from branch 3 although it might not
be that trivial to get out.
It will definitely require a bit of investment from multiple people
including the PMC and the committers of the project. Note that the last
vote for alpha2 was unsuccessful due to
+1 (non-binding)
Ubuntu 20.04.5 LTS, java version "1.8.0_261", Apache Maven 3.6.3
* Verified signatures and checksums OK
* Checked diff between git repo and release sources (diff -qr hive-git
hive-src) OK
* Checked LICENSE, NOTICE, and README.md file OK
* Built from release sources (mvn clean ins
Hi everyone,
Due to the large amount of spam account creation the ASF INFRA team has
disabled the JIRA account creation [1].
>From the 11th of November, contributors who wish to have a JIRA account (to
create, assign, watch, etc issues) will need to request an account through
an ASF PMC.
Other p
gt;
>> -Pravin
>>
>> On Tue, Nov 15, 2022 at 5:57 PM Stamatis Zampetakis
>> wrote:
>>
>>> Hi everyone,
>>>
>>> Due to the large amount of spam account creation the ASF INFRA team has
>>> disabled the JIRA account creation [1].
&
s for release blockers
> (jiras with labels "hive-4.0.0-must"). There are currently only 2 jiras
> tagged as blockers for 4.0.
>
> If you could tag the jiras for 3.2 release the same way, and add a quick
> filter, that would be great.
>
> Thank you again
> Naveen
>
&
Hi Sungwoo,
Many thanks for sharing your findings; interesting observations.
If you can please also share the project versions that you used for running
the experiments.
Best,
Stamatis
On Tue, Nov 15, 2022 at 12:46 PM Sungwoo Park wrote:
> Hello,
>
> I ran the TPC-DS benchmark using Metastore
Many thanks to everyone who made this release happen and especially Denys
for leading this effort!
Best,
Stamatis
On Wed, Nov 16, 2022 at 5:25 PM Denys Kuzmenko wrote:
> The Apache Hive team is proud to announce the release of Apache Hive
> version 4.0.0-alpha-2
>
> The Apache Hive (TM) data wa
, 2022 at 9:59 PM Stamatis Zampetakis
wrote:
> Logged https://issues.apache.org/jira/browse/INFRA-23905 for the creation
> of the new mailing list.
>
> On Tue, Nov 15, 2022 at 9:57 PM Abhay Chennagiri
> wrote:
>
>> +1, Thank you, Stamatis.
>>
>> On Tue, Nov 15, 202
Hi all,
In order to track changes who change the behavior of an existing component
or break public APIs we could adopt the use of JIRA labels as it is done in
other projects.
There are various existing labels used for this purpose in JIRA:
* Breaking-Change,
* breaking-api,
* breaking,
* breaking
Hello,
Regarding the inconsistency you describe in the window function, indeed it
seems to be a bug. However, I would double-check with the SQL standard
to be sure there is no intentional deviation and/or test the query in
different DBMS.
As far as it concerns the behavior of the aggregate functi
Hi team,
I don't think you need any kind of special permissions to enable pre-commit
tests for branch-3. I have the impression that just committing an
appropriate Jenkinsfile (e.g., HIVE-24331 [1]) should do the trick.
Best,
Stamatis
[1] https://issues.apache.org/jira/browse/HIVE-24331
On Wed,
for 3.2.0
> pipeline
>
> Hi Stamatis,
>
> Sure, thanks a lot for your help. Will make that change and update this
> mail thread.
>
> Thanks,
> Aman.
>
> From: Stamatis Zampetakis
> Sent: Wednesday, December 7, 2022 1:42 PM
> To: d
Congrats Ayush! Very well deserved!
Thanks for all the hard work that you are putting for the project and
always being there when people ask for help.
Best,
Stamatis
On Tue, Dec 20, 2022 at 7:51 AM Sankar Hariappan via user <
u...@hive.apache.org> wrote:
> Congrats Ayush!
>
>
>
> Thanks,
>
> Sa
JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=osIglpTld3PtOPyFhGBLTSU9Ku1FWngPMofNQXILpyM%3D&reserved=0
> >
> > The JenkinsFile is picked from the PR while running rather than the
> target
> > branch.
> >
> > -Ayus
tent update with the
>framework change. In this case, we can make the other changes incrementally
>at a later stage.
>
>
> Thanks!
> Simhadri G
>
> On Wed, Oct 5, 2022 at 3:41 PM Stamatis Zampetakis
> wrote:
>
>> Thanks for staying on top of this Simhadri.
&
ks
> > >
> > > On Sat, 14 Jan 2023 at 00:03, Naveen Gangam
> > wrote:
> > >
> > >> Hello Hive Community,
> > >> Apache Hive PMC is pleased to announce that Stamatis Zampetakis has
> > >> accepted the Apache Hive PMC's invitation to be
Hi all,
It appears that most of the current moderators of the Hive mailing lists
are not very active in the project thus messages and subscriptions may take
a while to be approved.
I am planning to request myself to be added as moderator to all lists but
it would be could nice if two more people
While the numbers give some insight, they do not tell the complete story of
how much Laszlo has helped drive the project forward.
Congrats Laszlo and thanks for everything that you have done for the
project.
Best,
Stamatis
On Sun, Jan 29, 2023 at 11:05 PM Sai Hemanth Gantasala <
saihema...@cloud
Krisztian's impact on the project has been immense, particularly in areas
such as rewriting, view maintenance, iceberg integration, sub-query
processing, and top-k pushdown, to name a few.
His contributions cannot be fully captured by the numbers and go beyond
what they can indicate.
Keep up the a
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 b
Congratulations Laszlo!
ACID and compactions are a complex beast and the slightest problem there
can have a huge impact in the system.
Many thanks for all your work in this area that makes the life of the rest
of us much easier.
Best,
Stamatis
On Wed, Feb 8, 2023 at 9:46 AM Akshat m wrote:
> C
In a rather short time Alessandro made many significant contributions for
the project.
He fixed many crucial issues with CBO adding also utils to fast diagnose
problems and quickly unblock production breakage.
He introduced Sonar in CI which is a big step for monitoring and improving
code quality,
> > > Sent: Tuesday, February 7, 2023 4:46 PM
> > > To: dev@hive.apache.org
> > > Subject: [EXTERNAL] Re: Branch-3 backports and build stability
> > >
> > > +1
> > > also, if I merged something that I thought was for test stability (but
> > > ins
I am +1 on removing/deprecating Hive on Spark since we've done this on
master and apparently nobody is interested in this feature.
Best,
Stamatis
On Wed, Feb 22, 2023 at 8:18 AM Aman Raj
wrote:
> Hi team,
>
> We have been trying to fix Hive on Spark test failures for a long time. As
> of now, b
Some people raised a valid point that branch-3 is a maintenance branch. If
we really aim 3.2.0 to be a maintenance release then we should minimize
breaking changes and prohibit new features. In this case Spark cannot go
away and the only thing we can do is deprecate it. It also means that we
should
ontribute-JIRA
>
> On Thu, 17 Nov 2022 at 16:43, Stamatis Zampetakis
> wrote:
>
>> The jira-reque...@hive.apache.org has been created and I added relevant
>> instructions on how to request a JIRA account in the wiki [1]. Feel free to
>> improve as you see fit!
>>
#HowToContribute-JIRA
[2] https://issues.apache.org/jira/browse/INFRA-24306
On Fri, Mar 3, 2023 at 9:31 AM Stamatis Zampetakis
wrote:
> Thanks for bringing this up Ayush.
>
> Yes we should update the wiki to reflect the new process; if nobody does
> it in the following days I wil
Hi Kirti,
Thanks for bringing up this topic.
The master branch already has many new features; we don't need to wait for
more to cut a GA.
The main criterion for going GA is stability thus I would consider
regressions as the only blockers for the release.
If I recall well the only regressions di
ub.com/apache/hive/pull/3599
>
> HIVE-26220 <https://issues.apache.org/jira/browse/HIVE-26220>
> Shade & relocate dependencies in hive-exec to avoid conflicting with
> downstream projects
>
> HIVE-26644 <https://issues.apache.org/jira/browse/HIVE-26644>
> Int
Hello,
I am not sure what a branch cut actually refers to. As I mentioned in the
past I am not in favor of maintaining multiple release branches; the cost
is high and the number of volunteers is simply not enough. I am willing to
reconsider if things change in the near future.
Apart from that, ha
ould be great if someone could review pull requests for
> subtasks in HIVE-26654. (I moved to HIVE-26654 three tickets that I previously
> requested code review for.)
>
> Best,
>
> --- Sungwoo
> [1] https://issues.apache.org/jira/browse/HIVE-27138
>
> On Fri, 10 Mar 2023, Stam
Hi all,
As discussed in another thread [1], it might be a good idea to agree
on the next 4 release managers (RM) beforehand to maintain as much as
possible a stable release cadence.
I can volunteer to be the RM for the next Hive release. Other any
other volunteers for the rest?
4.0.0 Stamatis
Regarding correctness, I think it makes sense to change default values and
possibly add a warning note when there's a known risk of wrong results.
Needless to say that we should try to fix as many issues as possible; we
still need volunteers to review open PRS.
Performances regressions are trickie
Hi everyone,
In the last Hive board report someone mentioned that the volume of Jira
notification emails to the dev list is huge especially when compared to
emails send by actual humans making it hard for someone to follow what's
happening in the project.
I personally share their viewpoint. For a
lly this mailing list will
> be useful to outside contributors as well.)
>
> --- Sungwoo Park
>
> On Sat, 25 Mar 2023, Stamatis Zampetakis wrote:
>
> > Hi everyone,
> >
> > In the last Hive board report someone mentioned that the volume of Jira
> > notificat
;. We are
> > ready to push new features and improvements on branch-3 now.
> >
> > I really want to thank Vihang Karajgaonkar, Chris Nauroth, Lazlo Bodor,
> > Stamatis Zampetakis and Sankar Hariappan without whom this would not at
> all
> > have been possible
Just logged https://issues.apache.org/jira/browse/INFRA-24440 to move
this forward.
Best,
Stamatis
On Thu, Mar 30, 2023 at 11:12 AM Stamatis Zampetakis wrote:
>
> I will proceed with the changes needed to move the Jira traffic out of the
> dev list sometime next week.
>
> If th
Hi Steve,
The way that we currently represent lateral views on the physical plan is
not great. I'm sure there are good reasons of why people went forward with
the approach of introducing specialized operators for that purpose but as
the history has shown the current representation is causing us lo
Hey Laszlo,
Dependency injection is a very powerful and useful tool/design pattern.
I don't think there is a particular reason for which Hive does not use
DI framework apart maybe from the fact that we have lots of legacy
code that existed before DI became that popular.
I am open to ideas and su
INFRA-24440 is resolved so all JIRA traffic now goes to issues@hive.
Don't forget to subscribe to that list if you wish to follow the
creation of new tickets etc.
Best,
Stamatis
On Fri, Apr 7, 2023 at 9:55 AM Stamatis Zampetakis wrote:
>
> Just logged https://issues.apache.org/jira/b
Just to be clear, I am in favor of introducing DI frameworks in Hive
where it makes sense. As Attila said, we don't want to get stuck with
legacy code forever. When a concrete proposal comes up we can discuss
benefits vs drawbacks.
Regarding stability I agree it is a pressing issue but Hive is an
I think we all agree that DI can be beneficial in general.
However, it's hard to say yes or no on something before having a
concrete case to discuss; it doesn't have to be a PR but we need to
work on a specific Hive use-case and list advantages/disadvantages of
the proposal.
Best,
Stamatis
On Mo
1 - 100 of 474 matches
Mail list logo