Agree to Peter and sunchao..
Even we are using the hive 3.x, we might contribute on bugfixes.
Even I am +1 on 1.x EOL as it's hard to maintain so many releases and time to
user's migrate to 2.x and 3.x.
On 09/05/22, 10:51 PM, "Chao Sun" wrote:
Agree to Peter above. I know quite a few p
Shall we put the core/shading to the blocker for 4.0.0?
Do we have a jira for it?
Thanks Sun Chao for bringing this up!
Peter
On Mon, May 9, 2022, 19:21 Chao Sun wrote:
> Agree to Peter above. I know quite a few projects such as Spark,
> Iceberg and Trino/Presto are depending on Hive 2.x and 3
Simhadri G created HIVE-26215:
-
Summary: Expose the MIN_HISTORY_LEVEL table through Hive sys
database
Key: HIVE-26215
URL: https://issues.apache.org/jira/browse/HIVE-26215
Project: Hive
Issue
Agree to Peter above. I know quite a few projects such as Spark,
Iceberg and Trino/Presto are depending on Hive 2.x and 3.x, and
periodically they may need new fixes in these. Upgrading them to use
4.x seems not an option for now since the core classified artifact has
been removed and the shading i
Anmol Sundaram created HIVE-26214:
-
Summary: Hive 3.1.3 Release Notes
Key: HIVE-26214
URL: https://issues.apache.org/jira/browse/HIVE-26214
Project: Hive
Issue Type: Improvement
Com
Jingxuan Fu created HIVE-26213:
--
Summary: "hive.limit.pushdown.memory.usage" better not be equal to
1.0, otherwise it will raise an error
Key: HIVE-26213
URL: https://issues.apache.org/jira/browse/HIVE-26213
royal created HIVE-26212:
Summary: hive fetch data timeout
Key: HIVE-26212
URL: https://issues.apache.org/jira/browse/HIVE-26212
Project: Hive
Issue Type: Bug
Components: HiveServer2
Af
Jingxuan Fu created HIVE-26211:
--
Summary: "hive.server2.webui.max.historic.queries" should be
avoided to be set too large, otherwise it will cause blocking
Key: HIVE-26211
URL: https://issues.apache.org/jira/browse/H
Hi Team,
My experience with the Iceberg community shows that there are some sizeable
userbase around Hive 2.x. I have seen patches, contributions to Hive 2.3.x
branches, and the tests are in much better shape there.
I would definitely vote for EOL Hive 1.x, but until we have a stable 4.x, I
wo
Hi Stamatis,
thanks for bringing up this topic, I basically 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
f
László Végh created HIVE-26210:
--
Summary: Fix tests for Cleaner failed attempt threshold
Key: HIVE-26210
URL: https://issues.apache.org/jira/browse/HIVE-26210
Project: Hive
Issue Type: Bug
11 matches
Mail list logo