here or perhaps
> this would be the sponsor
>
> On Tue, May 21, 2024 at 1:36 PM Stamatis Zampetakis wrote:
>>
>> Hey Eugene,
>>
>> Having a cluster for performance testing is a great idea and it is
>> something that has popped up in various contexts.
>&
Hey Eugene,
Having a cluster for performance testing is a great idea and it is
something that has popped up in various contexts.
The most common way to obtain such clusters is via sponsors (companies
or individuals) donating resources to the project. For example, the
Hive CI is now running
t; time (UTC -4)
>
> Another option is to do the interview in person in Bratislava, if you are
> coming to Community Over Code next month.
>
> —Rich
>
> > On May 4, 2024, at 9:04 AM, Stamatis Zampetakis wrote:
> >
> > Hey Rich,
> >
> > It would
+1 (binding)
On Fri, May 10, 2024 at 10:10 AM Denys Kuzmenko wrote:
>
> +1 (binding)
Hey Rich,
It would be great to have a podcast about Hive and the 4.0 release so
I am happy to volunteer. If there are more people willing to
participate I can definitely cede my place and let others do the
talking.
Best,
Stamatis
On Tue, Apr 30, 2024 at 4:25 PM Rich Bowen wrote:
>
> I saw the
Severity: moderate
Affected versions:
- Apache Hive 4.0.0-alpha-1 before 4.0.0
Description:
Improper Control of Generation of Code ('Code Injection') vulnerability in
Apache Hive.
The vulnerability affects the Hive JDBC driver component and it can potentially
lead to arbitrary code
t-minicluster
> & such problems by users keep on coming, eg [3]
>
> Anyone else, any thoughts?
>
> -Ayush
>
> [1] https://lists.apache.org/thread/cwtxnffoqpwgmdtlc9hyor2cm22djpkg
> [2] https://lists.apache.org/thread/23sshgolmbpcc01npqgt03woljdy6hdn
> [3] https://lis
Hey Simhadri, thanks for starting this discussion.
Maven has many limitations when it comes to publishing multiple
artifacts from the same module. In most cases, the end result is
broken and hard to use. The pom file that is published for a given
module is not able to describe correctly all
Hello,
I am not sure how to interpret the comments about HIVE-28121. Are we
waiting for HIVE-28121 to be merged for 2.3.10 or this release can
proceed even without it?
Best,
Stamatis
On Mon, Apr 22, 2024 at 10:37 AM Cheng Pan wrote:
>
> I made integration tests with Apache Spark[1] and Apache
t;
> On 2024/04/18 07:49:59 Stamatis Zampetakis wrote:
> > The 4.0.0 release was quite recent so I assume we don't have major
> > breaking changes in there at the moment so we could cut the release
> > directly from master as soon as we want. HIVE-28166 is already merged
> &
branch & the label if
> anyone wants that a particular ticket to be part of the 4.0.1 release.
>
> -Ayush
>
> On Wed, 17 Apr 2024 at 12:42, Stamatis Zampetakis wrote:
>>
>> Thanks for starting the discussion Ayush.
>>
>> Having frequent releases is defin
Hi all,
Following the INFRA policy [1] about handling current and older
releases, I just removed the following releases from the main download
site [2].
Apache Hive 1.2.2
Apache Hive 3.1.2
Apache Hive 1.2.2
Apache Hive 4.0.0-alpha-1
Apache Hive 4.0.0-alpha-2
Apache Hive 4.0.0-beta-1
The
Thanks for starting the discussion Ayush.
Having frequent releases is definitely needed so we should keep the
momentum going.
I had the impression from other threads that the next Hive release
would be 4.1.0 and that it would be cut from master. I would like to
understand how 4.0.1 is different
Great initiative and nice content. Overall, it looks great!
I have some minor comments. Is it possible to change permissions allow
comments from anyone or it has to be done on a per user basis?
Best,
Stamatis
On Fri, Apr 5, 2024 at 1:54 PM Ayush Saxena wrote:
>
> Hi All,
>
> Have been talking
The new Apache Hive 4.0.0 release brings roughly 5K new commits (since
Apache Hive 3.1.3) and it's probably the biggest release so far in the
history of the project. The numbers clearly show that this is a
collective effort that wouldn't be possible without a strong community
and many volunteers
-0 (binding)
Ubuntu 20.04.6 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 (4 empty directories in apache-hive-4.0.0-src)
Only in apache-hive-4.0.0-src/hcatalog:
The work on HIVE-27953 is now completed so the github.io sites are
officially down and the obsolete content is removed from the various
repos.
Many thanks Simhadri for leading all these efforts in modernising the
Hive website and dealing with the legacy sites.
Best,
Stamatis
On Wed, Mar 13,
Hello,
Indeed they have an impact on the readability and maintenance of the
class so I would be in favor of dropping them.
Checking the calls to HiveConf.ConfVars#getDescription [1] it seems
that line breaks are somewhat relevant for generating the
hive-default.xml.template and SHOW CONF command
Hey Soumyakanti,
Thanks for starting this discussion.
I like the idea of reducing boilerplate code and one way although not
the only one is using AOP. AOP libraries rely on code injection and
there are various pros/cons [1] when using such tools. If AspectJ is
the best option for this use-case I
security mailing list of Hive?
> sank...@apache.org
>
> Thanks,
> Sankar
>
> On 2024/01/22 13:53:53 Stamatis Zampetakis wrote:
> > For traceability purposes, please subscribe to the mailing list with
> > your @apache.org address. Any other requests will be denied f
ferences, which
> > I
> > > personally wanted to avoid, but yep we can take another approach as well.
> > > Good with me.
> > >
> > > For the Jira, yep we should, we aren't going to release this, so for fix
> > > version, maybe I will create a dev-b
want a separate Jira project under
> > Hive for these repos as well, We can explore that route if folks feel that
> > way.
> >
> > -Ayush
> >
> >
> > On Tue, 23 Jan 2024 at 13:35, Stamatis Zampetakis wrote:
> >
> >> Thanks for helping advance t
+0
I rarely open attachments from public mailing lists for security
reasons (unless we are talking for known safe extensions).
Moreover, I find it easier to glance through code if people share a
link to a PR or code in GitHub than if I have to download and apply a
patch locally.
I understand
and all of us can take care of things from there
> > slowly-slowly :-)
> >
> > Shout out, if anyone has objections around it.
> >
> > -Ayush
> >
> >
> > [1]
> > https://github.com/apache/hive/blob/1aeaff2057a2f4c241f8bcc53a2a529e6e7f45d4/Jen
AM Stamatis Zampetakis wrote:
>
> The security issues are of utmost importance to ASF projects and
> should be treated in a timely manner.
>
> Thanks Ayush for the reminder!
>
> Best,
> Stamatis
>
> On Mon, Jan 22, 2024 at 11:05 AM Ayush Saxena wrote:
>
19, 2024 at 11:28 AM Alessandro Solimando <
> > > >alessandro.solima...@gmail.com> wrote:
> > > >
> > > >> +1, thanks Stamatis
> > > >>
> > > >> On Fri, Jan 19, 2024, 11:14 Ayush Saxena wrote:
> > > >>
&g
The security issues are of utmost importance to ASF projects and
should be treated in a timely manner.
Thanks Ayush for the reminder!
Best,
Stamatis
On Mon, Jan 22, 2024 at 11:05 AM Ayush Saxena wrote:
>
> Hi Folks,
> In case any of the committers or PMC members are not subscribed to the
>
Hey everyone,
I noticed that in our official git repo [1] we have some kind of
feature/WIP branches (see list below). Most of them (if not all) are
stale, add noise, and some of them eat CI resources (storage and CPU)
since Jenkins picks them up for builds/precommits.
I would like to drop those
FYI: https://issues.apache.org/jira/browse/HIVE-28013
Best,
Stamatis
+1 (binding)
Best,
Stamatis
On Wed, Jan 17, 2024 at 8:21 AM Attila Turoczy
wrote:
>
> +1
>
> -Attila
>
> On Tue, 16 Jan 2024 at 22:18, Butao Zhang wrote:
>
> > +1
> >
> >
> >
> > Thanks,
> > Butao Zhang
> > Replied Message
> > | From | Ayush Saxena |
> > | Date | 1/17/2024 14:15 |
>
Hello,
There is a PR for addressing the problem [1] and it will be merged in
the next few days. In the meantime feel free to ignore the Sonar
errors; nothing too bad will happen by doing this.
Many thanks to Wechar Yu for jumping on this and pushing it forward.
Best,
Stamatis
[1]
> > branches.(Subjective Opinion)
> > >
> > > IMO, We should consider marking 1.x & 2.x as EOL, Resolve upgrade issues
> > > mentioned for 3.x->4.x and once resolved, if that doesn't require any
> > > changes on 3.x line and everyone is happy the
Hey Zsolt,
There have been a few discussions in the past about moving the
documentation from the wiki to the website and from what I recall
people were more or less in favor of moving towards this direction.
The main thing missing is volunteers that are willing to take on this
migration step.
+1 for enforcing style on new code. It will definitely save us from
additional review cycles.
Although I like checkstyle I tend to prefer tools that can
automatically apply and fix style violations such as spotless [1].
It seems that the spotless plugin can be configured to enforce
formatting
Hi all,
>From a quick code review, I get the impression that we may have
various runtime bugs around vectorized map joins on dates.
One problem is reported under HIVE-27943 but I suspect there are more
waiting to be found. For those searching to contribute to the project,
this area shouldn't be
Congratulations Butao, well deserved! Very glad to see another Iceberg
expert joining the team.
Best,
Stamatis
On Tue, Nov 21, 2023, 4:47 PM Butao Zhang wrote:
> Thank you to the Hive community for this honor. I will continue to
> contribute to the community with my efforts.
> Thanks all!
>
>
Hey Okumin,
Thanks for picking up this ticket and driving it forward.
I don't have a strong opinion between the two options.
On the surface the factory option seems simpler and possibly more
efficient but I am not sure if the changes under the PR are sufficient
to cover all usages in Hive.
On
; and I cannot see/recall any seed job that generates this test job, so we
> should consider adding this to the hive repo - similarly to the main
> precommit job's Jenkinsfile
> <https://github.com/apache/hive/blob/master/Jenkinsfile> - if possible.
>
> Regards,
> Laszlo Bodo
Hello,
I am looking into this as part of HIVE-27695. Till we commit the fix
feel free to ignore the tests that are failing with OOM related errors
in TestMiniTezCliDriver.
Best,
Stamatis
[1] https://issues.apache.org/jira/browse/HIVE-27695
On Wed, Oct 4, 2023 at 9:44 AM Zoltán Rátkai
wrote:
>
Apache Hive's Project Management Committee (PMC) has invited Sourabh
Badhya to become a committer, and we are pleased to announce that he
has accepted.
Sourabh has been doing some great work for the project. He has landed
important fixes in critical parts of Hive and made significant
,
Stamatis
[1] https://www.apache.org/dev/project-requirements#technical
On Wed, Sep 13, 2023 at 11:11 AM Ayush Saxena wrote:
>
> Hi Stamatis,
> Thanx for starting the thread, I can volunteer as well.
>
> -Ayush
>
> On Tue, 12 Sept 2023 at 13:43, Stamatis Zampetakis wrote:
Hey Chris,
Keep in mind that the core jar was removed some time ago [1, 2] so in
new releases (4.0.0 onwards) it will not be there.
I am not sure what integration you are trying to establish but it
would be definitely easier if you opt for something lighter like the
JDBC API and the Hive JDBC
For tracking purposes, I don't think we need something very elaborate.
A simple JIRA filter that includes priority (Blocker), target version
(4.0.0), and status (open) should be enough:
project =Hive and priority = Blocker and cf[12310320] = 4.0.0 and status = open
Best,
Stamatis
On Wed, Sep
. Needless to say
that since I am the one proposing it, I would like to be part of the
list.
Any additional thoughts or suggestions on how to improve this process
are very welcomed. Also if you like the idea and want to volunteer
please reply to this email to add yourself to the list.
Best,
Stamatis Zampetakis wrote:
>
> For the licensing question, I just created LEGAL-653 [1].
>
> [1] https://issues.apache.org/jira/browse/LEGAL-653
>
> On Thu, Aug 24, 2023 at 11:55 AM Stamatis Zampetakis
> wrote:
> >
> > Creating the new repos should be kind of tr
Hey Ayush,
I just wanted to highlight that the vote applies to all released
artifacts, not only the source packages. The source package is of
course the primary and most important deliverable but the PMC is
responsible for everything under downloads.apache.org and similar
places. Any additional
For the licensing question, I just created LEGAL-653 [1].
[1] https://issues.apache.org/jira/browse/LEGAL-653
On Thu, Aug 24, 2023 at 11:55 AM Stamatis Zampetakis wrote:
>
> Creating the new repos should be kind of trivial. I think I will be
> able to do it using https://selfserve.a
; > On 23-Aug-2023, at 6:19 PM, Zoltan Haindrich wrote:
> > >
> > > Hey Stamatis!
> > >
> > > I'm happy to donate these repos / help with the migration!
> > > I should have done it earlier - but it was never top priority...thank
> > you for init
Hi all,
Our precommit infrastructure uses code that resides in the following repos.
* https://github.com/kgyrtkirk/hive-test-kube
* https://github.com/kgyrtkirk/hive-toolbox
* https://github.com/kgyrtkirk/hive-dev-box
These are mainly maintained by Zoltán Haindrich who is always helpful
and
would prefer to replace it with a run
> script/configuration that runs Hive Server in a 'Mini' mode, for local
> development purposes.
>
> Thanks,
> Zsolt
>
>
> Stamatis Zampetakis ezt írta (időpont: 2023. aug. 22.,
> K, 18:06):
>
> > I am not against restoring it
I am not against restoring itest.jdbc.jars property but for this case
I prefer the explicit declaration of the dependency.
Adding an optional or test scope dependency is much simpler and works
out of the box. We don't need to download jars manually and we don't
need to remember how the system
Hey Laszlo,
Thanks a lot for pushing this forward. I really love the diff in the
PR that shows 120K lines of code less than before :)
Apache software is not very different from enterprise software so the
same applies to releases as well.
Cutting a new release/branch would mean that we have to
.apache.org/jira/browse/HIVE-27338>
> > was
> > about to solve licensing problems, and it achieved that, but maybe went too
> > far: I believe we should be able to provide jars to the test classpath,
> > e.g. jars that were downloaded beforehand, even manually.
> >
eady added you).
>
> cheers,
> Zoltan
>
>
> On 8/15/23 17:18, Stamatis Zampetakis wrote:
> > Hey all,
> >
> > I was wondering who has admin privileges for http://ci.hive.apache.org/ ?
> >
> > I would like to check and potentially upgrade some
Hey Zsolt,
I would divide this discussion into three topics:
1. What are the benefits of using the StartMiniHS2Cluster?
2. What other alternatives are there for testing HS2 with different
metastore DBMS?
3. How can we make StartMiniHS2Cluster work as before?
Regarding the point 1, I don't have
Hey all,
I was wondering who has admin privileges for http://ci.hive.apache.org/ ?
I would like to check and potentially upgrade some plugins that are
currently installed. Is it possible to get permissions to manage the
Jenkins instance?
As a side note we may want to document the current
The Apache Hive team is proud to announce the release of Apache Hive
version 4.0.0-beta-1.
The Apache Hive (TM) data warehouse software facilitates querying and
managing large datasets residing in distributed storage. Built on top
of Apache Hadoop (TM), it provides, among others:
* Tools to
Hey Zsolt,
Filtering works [1] but possibly the autofill feature works somewhat
differently. It may be necessary to establish a list of collaborators [2]
to achieve what you want. I don't know if there is another more transparent
way to do this. Probably the best way to move this forward is file
Thanks to everyone who has tested the release candidate and given
their comments and votes.
The tally is as follows.
3 binding +1s:
Stamatis Zampetakis
Denys Kuzmenko
Ayush Saxena
3 non-binding +1s:
Zhihua Deng
Sourabh Badhya
Simhadri Govindappa
No 0s or -1s.
Therefore, I am delighted
Hello Okumin,
As you mentioned the TIME datatype is part of the SQL standard and it
is also supported by many popular DBMS so it definitely makes sense to
add it to Hive.
I guess it was not implemented already cause users were able to store
times using other existing types so it never became a
Hi all,
I have created a build for Apache Hive 4.0.0-beta-1 Release Candidate 0.
Thanks to everyone who has contributed to this release.
You can read the release notes here:
https://github.com/apache/hive/blob/branch-4.0.0-beta-1/RELEASE_NOTES.txt
The commit to be voted upon:
Hello,
As usual I would advise against sudden drop of functionality,
especially SQL syntax. It would be better if we could disable/issue a
warning in one release and drop in the next to give users at least
some time to digest the changes.
How about the following:
In 4.0, disable the
to get it merged and give the
> release.?
>
> On 18/07/23, 2:39 PM, "Stamatis Zampetakis" <mailto:zabe...@gmail.com>> wrote:
>
>
> HIVE-27504 still lacks reviews from committers.
>
>
> Note that I will not be able to work on the release from 22/07 to
> 30
Thanks for pushing this forward Aman. The main focus at this point is
4.0.0-beta-1 so personally I don't have much free time to allocate to
Hive 3.x releases.
Best,
Stamatis
On Sat, Jul 29, 2023 at 12:21 PM Aman Raj wrote:
>
> Hi team,
>
> I have raised PR's in branch-3
13, 2023 at 6:33 PM Attila Turoczy
wrote:
>
> Thanks for the update! Can't wait for the beta :)
>
> -Attila
>
> On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis
> wrote:
>
> > Hey everyone,
> >
> > As you may have noticed there have been various t
Interesting read, thanks Akshat for putting this together. For those
that didn't know that Hive is a powerful data federation engine the
article is a great start. Looking forward to more great content!
Best,
Stamatis
On Wed, Jul 12, 2023 at 7:54 AM Ayush Saxena wrote:
>
> Thanx Akshat, it is up
Hello,
I don't know in what state is branch-2.3 right now but if someone is
willing to cut a release from there then sure why not. Just ensure
that LICENSE/NOTICE files conform to the ASF policy and the respective
JIRAs are backported. Probably some of the following JIRAs are
relevant (hoping
problems. I would like to avoid having last minute -1 votes due to
that.
Best,
Stamatis
[1] https://issues.apache.org/jira/browse/HIVE-27504
On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis wrote:
>
> Hey team,
>
> Small heads up regarding the progress of the 4.0.0-beta-1 relea
Hey everyone,
HPL/SQL has been part of Hive for a long time now. Surprisingly (at
least for me), the main website and documentation around HPL/SQL[1] is
not under the hive domain and I don't know how many people have access
to it. Looking at the website [1] at the moment some things appear
broken
Hello,
The tests under DbInstallBase [1] seem to do more or less what you
want. Check them out and if something is missing don't hesitate to
enrich them.
Best,
Stamatis
[1]
Hi all,
The Calcite community is organising a key signing party tomorrow [1].
Such events are extremely useful for growing the web of trust and are
particularly relevant for ASF committers which usually have to sign
artifacts and releases.
The event will not take more than a couple of minutes.
] https://www.apache.org/legal/resolved.html
[5] https://github.com/apache/hive/tree/master/binary-package-licenses
[6] https://www.mojohaus.org/license-maven-plugin/
On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis wrote:
>
> I can start preparing the RC towards the end of next week. If so
Hello,
I tend to agree with Sai; if we can run on demand the failed tests
that would be a cool feature. If we just rerun everything that fails
without questions asked we may do more harm than good. Taking into
account the fact that nobody runs all tests locally before submitting
a PR (cause it is
I can start preparing the RC towards the end of next week. If somebody
has more time and wants to start earlier I am fine to switch.
Best,
Stamatis
On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko wrote:
>
> great, this is the current list of release managers:
>
> 4.0.0 Stamatis Zampet
3, "Ayush Saxena" wrote:
> > >+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
> > >
> > >> O
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.
+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
>
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
>
> A note of thanks to Joydeep Sen Sharma, Carl Steinbach, Stamatis Zampetakis
> & Naveen Gangam for helping with the process. Attila Turoczy for the
> initial thoughts/idea.
>
> -Ayush
Hey all,
We already have nightly builds for Hive [1].
Do we need something more than that?
Best,
Stamatis
[1] http://ci.hive.apache.org/job/hive-nightly/
On Tue, May 23, 2023 at 9:03 AM vihang karajgaonkar wrote:
>
> I think there are many benefits like others in this thread suggested which
Thanks for updating the wiki Ayush! Definitely very helpful and
hopefully we can do it for other pages as well.
Slack is a very useful tool but personally I don't have much time to
monitor yet another channel of communication. I don't know if we
should encourage people to start discussions there
, 2023 at 11:52 AM Attila Turoczy
wrote:
>
> +2. Who is working now on the TPCDS regression? Can I / We help him/ her?
>
> -Attila
>
>
> On Tue, May 16, 2023 at 11:04 AM Stamatis Zampetakis
> wrote:
>
> > I agree with Attila we should do our best to come out with the
priorities of other JIRAs so that It may give us clarity
>> GO/NO-GO for 4.0.0 GA release and its timeline?
>>
>>
>>
>> Thanks,
>> Kirti
>>
>> On Sat, Mar 25, 2023 at 3:27 PM Stamatis Zampetakis
>> wrote:
>>
>> > Regarding
zy
> > wrote:
> >
> > +1
> >
> >> On Fri, May 12, 2023 at 4:01 PM Alessandro Solimando <
> >> alessandro.solima...@gmail.com> wrote:
> >> Hi Stamatis,
> >> I am experiencing the same too, so +1 from me.
> >> Best re
Hello,
Everything that happens in a GitHub PR creates a worklog entry under
the respective JIRA ticket.
For every worklog entry we receive a notification from j...@apache.org
when we are watching an issue. The worklog entry and email
notification usually appear messy.
Moreover, if we are
I checked the Pig repo and I see some recent activity. Rohini is actively
leading the effort towards a new Pig release. Given that there is proven
interest to maintain and contribute to this module I would prefer to keep
it for the time being unless there are major issues that I am not aware of.
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
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
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/browse
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
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
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
Stamatis Zampetakis created HIVE-27225:
--
Summary: Speedup build by skipping SBOM generation by default
Key: HIVE-27225
URL: https://issues.apache.org/jira/browse/HIVE-27225
Project: Hive
Stamatis Zampetakis created HIVE-27199:
--
Summary: Read TIMESTAMP WITH LOCAL TIME ZONE columns from text
files using custom formats
Key: HIVE-27199
URL: https://issues.apache.org/jira/browse/HIVE-27199
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. As
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
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
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
Stamatis Zampetakis created HIVE-27162:
--
Summary: Unify HiveUnixTimestampSqlOperator and
HiveToUnixTimestampSqlOperator
Key: HIVE-27162
URL: https://issues.apache.org/jira/browse/HIVE-27162
Stamatis Zampetakis created HIVE-27161:
--
Summary: MetaException when executing CTAS query in Druid storage
handler
Key: HIVE-27161
URL: https://issues.apache.org/jira/browse/HIVE-27161
Project
1 - 100 of 380 matches
Mail list logo
