Makes sense.
Also I see commit on branch-3: https://github.com/apache/hive/pull/2869/files
Details:
[hive] branch branch-3 updated: HIVE-25795: Update log4j2 version to 2.16.0 for
branch-3 (Naveen Gangam)
ngangam pushed a commit to branch branch-3
in reposito
it’s committed only for master where we dn’t have this.
Only for branch-2 and branch-3, we need to handle this file. Please see,
following discussion for same..
https://github.com/apache/hive/pull/2863
If you are interested, you raise PR for branch-2 and branc-3.
From: Sundaram, Ramakrishnan
Sai Hemanth Gantasala created HIVE-25813:
Summary: CREATE TABLE x LIKE storagehandler-based-source fails
Key: HIVE-25813
URL: https://issues.apache.org/jira/browse/HIVE-25813
Project: Hive
Steve Carlin created HIVE-25812:
---
Summary: GetResultSchema service called in ERROR state
Key: HIVE-25812
URL: https://issues.apache.org/jira/browse/HIVE-25812
Project: Hive
Issue Type: Improvem
+ security
From: "Sundaram, Ramakrishnan"
Date: Wednesday, December 15, 2021 at 1:32 PM
To: "dev@hive.apache.org"
Subject: Regarding log4j2 upgrade: HIVE-25804, HIVE-25795 related to
CVE-2021-44228
Hi,
I see in HIVE-25804 and HIVE-25795, testutils/ptest2/pom.xml is not upgraded to
latest vers
Hi,
I see in HIVE-25804 and HIVE-25795, testutils/ptest2/pom.xml is not upgraded to
latest versions.
Is this a miss? Or the change is not needed?
Regards,
Ram
Viktor Csomor created HIVE-25811:
Summary: Fix TestMiniLlapLocalCliDriver#testCliDriver[sysdb]
caused by the HIVE-25737
Key: HIVE-25811
URL: https://issues.apache.org/jira/browse/HIVE-25811
Project:
Hello all!
In the recent week there were 2 new log4j vulnerabilities discovered (CVE-2021-45046, CVE-2021-44228) - and since we use log4j in Hive; existing installations might be
affected as well.
Doing a new Hive release on any existing line would probably need a longer timeframe - and doing
Hi projects!
A little while ago I informed the Hadoop and HBase projects of my intention
to rename the H nodes on ci-hadoop.apache.org. The proposal is at [1]. I
neglected to inform you guys who also use the same nodes.
The naming is really for Infra benefit , but should not really affect
project
