Re:Re: Re: Support java/11/17/21

://issues.apache.org/jira/browse/HADOOP-18197?focusedCommentId=17820711=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17820711 >[3] https://github.com/apache/hadoop/pull/6593 > >On Wed, 10 Jul 2024 at 13:15, lisoda wrote: >> >> Hello Sir. >> Hadoop upgr

Re:Re: Support java/11/17/21

; 写道： We are working towards supporting JDK-17, should take couple of months, we don’t have a planned deadline for that as of now Btw. hadoop didn’t drop support for JDK-8…. -Ayush On 10 Jul 2024, at 12:52 PM, lisoda wrote:  Hi. Currently, Iceberg/hadoop/spark and the rest of the third-party

Support java/11/17/21

Hi. Currently, Iceberg/hadoop/spark and the rest of the third-party frameworks have dropped support for JAVA8 (or are planning to do so). When will HIVE be able to support a higher version of the JDK and what progress has been made in this regard?

Some problems encountered when reading ICEBERG with vectorisation turned on

Hi. I am using HIVE 4.0.0 to read ICEBERG tables. I am having some problems with it, so if someone could guide me, that would be great. Env: hadoop3.3.6 hive4.0.0 tez0.10.2 iceberg1.4.3 iceberg-table: hadoop-catalog-table/location_based_table Question 1: How

Re: Blog article 'Performance Tuning for Single-table Queries'

 Replied Message | From | Sungwoo Park | | Date | 12/24/2023 00:06 | | To | user@hive.apache.org | | Cc | | | Subject | Blog article 'Performance Tuning for Single-table Queries' | Hello Hive users, I have published a new blog article 'Performance Tuning for Single-table

when enable reducededuplication, count(distinct)+group by very slow

Hi team. I found that when I enable reduceduplication, count(distinct)+GroupBy becomes very slow. Is there a problem with reduceduplication? test query info: | CONFIG | SQL | TIME | | hive.optimize.reducededuplication=true | select count(1) from(select uni_shop_id,partner,count(distinct

A deadLock problem

Hi Team. [HIVE-27944] When HIVE-LLAP reads the ICEBERG table, a deadlock may occur. - ASF JIRA (apache.org) I submitted this ISSUE, if anyone can help me I would appreciate it. Tks.

Re:Re: hive can not read iceberg-parquet table

Hi. Following your suggestion, I created three ISSUE: [HIVE-27901] Hive's performance for querying the Iceberg table is very poor. - ASF JIRA (apache.org) [HIVE-27900] hive can not read iceberg-parquet table - ASF JIRA (apache.org) [HIVE-27898] HIVE4 can't use ICEBERG table in subqueries - ASF

Re:Re: hive can not read iceberg-parquet table

Sorry, I don't have an account with jira at the moment. I was rejected by the administrator when I applied for an account earlier. He thought that such issues could be discussed in an email. I'll try to apply for an account again.

Re:Re: hive can not read iceberg-parquet table

1. TEZ_VERSION 0.10.3 SNAPSHOT 2. iceberg table is cow table. insert small data will get same error. 3.using orc-iceberg is ok. 4. disable vectorized and using parquet is ok.

hive can not read iceberg-parquet table

Hi team. I am currently testing HIVE-4.0.0-BETA. For better read performance, we use the Iceberg-Parquet table. However, we have found that HIVE is currently unable to handle iceberg-parquet tables correctly. Example: CREATE EXTERNAL TABLE iceberg_dwd.b_qqd_shop_rfm_parquet_snappy STORED BY

Re: [EXTERNAL] Re: Slow Hive query with a lot of 'get_materialized_views_for_rewriting'

May I ask when hive4 can be released? Replied Message | From | Butao Zhang | | Date | 11/17/2023 12:24 | | To | user@hive.apache.org | | Cc | | | Subject | Re: [EXTERNAL] Re: Slow Hive query with a lot of 'get_materialized_views_for_rewriting' | Thanks for the info. I checked

Re:Re: Re: Hive's performance for querying the Iceberg table is very poor.

plied Message ---- | From | lisoda | | Date | 11/9/2023 14:25 | | To | | | Subject | Re:Re: Re: Hive's performance for querying the Iceberg table is very poor. | Incidentally, I'm using a COW table, so there is no DELETE_FILE. 在 2023-11-09 10:57:35，"Butao Zhang" 写道： Hi lisoda. Yo

Re:Re: Re: Hive's performance for querying the Iceberg table is very poor.

Incidentally, I'm using a COW table, so there is no DELETE_FILE. 在 2023-11-09 10:57:35，"Butao Zhang" 写道： Hi lisoda. You can check this ticket https://issues.apache.org/jira/browse/HIVE-27347 which can use iceberg basic stats to optimize count(*) query. Note: it didn't t

Re:Re: Re: Hive's performance for querying the Iceberg table is very poor.

uld be supported even today on Hive master, but 4.0.0 would have them running for sure. -Ayush On Tue, 24 Oct 2023 at 14:51, lisoda wrote: Thanks. I would like to know if hive currently supports push to ICEBERG table partition under JOIN condition. Because I see HIVE-27734 is not yet compl

Re: Announce: Hive-MR3 with Celeborn,

Thanks. I will try. Replied Message | From | Sungwoo Park | | Date | 10/24/2023 20:08 | | To | user@hive.apache.org | | Cc | | | Subject | Announce: Hive-MR3 with Celeborn, | Hi Hive users, Before the impending release of MR3 1.8, we would like to announce the release of Hive-MR3

Re:Re: Hive's performance for querying the Iceberg table is very poor.

tables? 在 2023-10-24 11:03:07，"Ayush Saxena" 写道： Hi Lisoda, The iceberg jar for hive 3.1.3 doesn't have a lot of changes, We did a bunch of improvements on the 4.x line for Hive-Iceberg. You can give iceberg a try on the 4.0.0-beta-1 release mentioned here [1], we ha

Re: Hive's performance for querying the Iceberg table is very poor.

Apache Iceberg, Apache Hudi and Apache Hive. Here is a video of connecting the 2 products through a webinar StarRocks did with Tabular (authors of Apache Iceberg). https://www.youtube.com/watch?v=bAmcTrX7hCI=10s On Mon, Oct 23, 2023 at 7:18 AM lisoda wrote: Hi Team. I recently was testing

Hive's performance for querying the Iceberg table is very poor.

Hi Team. I recently was testing Hive query Iceberg table , I found that Hive query Iceberg table performance is very very poor . Almost impossible to use in the production environment . And Join conditions can not be pushed down to the Iceberg partition. I'm using the 1.3.1 Hive