Re: Fwd: about hive4.0.0 error
Are you using MR execution mode? it was deprecated, see warning "Hive-on-MR is deprecated in Hive 2 and may not be available in the future versions. Consider using a different execution engine" On 2024/06/19 04:59:22 张三 wrote: > -- Forwarded message - > 发件人: 张三 > Date: 2024年6月19日周三 12:55 > Subject: about hive4.0.0 error > To: > > > Dear Hive team, > > I encountered an issue while using the latest version of Hive, 4.0.0. I am > not sure if this is a bug. The details are as follows: I am using Hadoop > version 3.3.6 and have set up a fully distributed cluster. The Hive version > is 4.0.0, with one master server and one client. Currently, I am connecting > to Hive via the Beeline client. When executing a join in Hive, I > encountered the following error: > > ``` > > 0: jdbc:hive2://node1:1> SELECT emp.emp_id, emp.emp_name, dept.dept_name > . . . . . . . . . . . . . .> FROM emp > . . . . . . . . . . . . . .> JOIN dept ON emp.dept_id = dept.dept_id; > INFO : Compiling > command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc): > SELECT emp.emp_id, emp.emp_name, dept.dept_name > FROM emp > JOIN dept ON emp.dept_id = dept.dept_id > INFO : No Stats for default@emp, Columns: emp_name, dept_id, emp_id > INFO : No Stats for default@dept, Columns: dept_name, dept_id > INFO : Semantic Analysis Completed (retrial = false) > INFO : Created Hive schema: > Schema(fieldSchemas:[FieldSchema(name:emp.emp_id, type:int, comment:null), > FieldSchema(name:emp.emp_name, type:strin > g, comment:null), FieldSchema(name:dept.dept_name, type:string, > comment:null)], properties:null)INFO : Completed compiling > command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc); > Time taken: 0.894 seconds > INFO : Concurrency mode is disabled, not creating a lock manager > INFO : Executing > command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc): > SELECT emp.emp_id, emp.emp_name, dept.dept_name > FROM emp > JOIN dept ON emp.dept_id = dept.dept_id > WARN : Hive-on-MR is deprecated in Hive 2 and may not be available in the > future versions. Consider using a different execution engine (i.e. tez > ) or using Hive 1.X releases.INFO : Query ID = > root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc > INFO : Total jobs = 1 > INFO : Starting task [Stage-4:MAPREDLOCAL] in serial mode > ERROR : Execution failed with exit status: 1 > ERROR : Obtaining error information > ERROR : > Task failed! > Task ID: > Stage-4 > > Logs: > > ERROR : /tmp/root/hive.log > ERROR : FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask > INFO : Completed executing > command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc); > Time taken: 4.461 seconds > Error: Error while compiling statement: FAILED: Execution Error, return > code 1 from org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask (state=08S0 > 1,code=1) > > ``` > > I checked the log on the Hive server at /tmp/root/hive.log and found the > following error information: > > ``` > > 2024-06-19T11:22:56,454 INFO [NotificationEventPoll 0] > HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: > name=metast > ore.batch.retrieve.max defaultValue=50 2024-06-19T11:23:01,656 INFO > [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr > cmd=scheduled_query_poll > 2024-06-19T11:23:56,375 INFO [NotificationEventPoll 0] > HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: > name=metast > ore.batch.retrieve.max defaultValue=50 2024-06-19T11:24:01,946 INFO > [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr > cmd=scheduled_query_poll > 2024-06-19T11:24:56,373 INFO [NotificationEventPoll 0] > HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: > name=metast > ore.batch.retrieve.max defaultValue=50 2024-06-19T11:25:02,197 INFO > [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr > cmd=scheduled_query_poll > 2024-06-19T11:25:56,376 INFO [NotificationEventPoll 0] > HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: > name=metast > ore.batch.retrieve.max defaultValue=50 2024-06-19T11:26:02,390 INFO > [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr > cmd=scheduled_query_poll > 2024-06-19T11:26:56,373 INFO [NotificationEventPoll 0] > HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: > name=metast > ore.batch.retrieve.max defaultValue=50 2024-06-19T11:27:02,660 INFO > [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr > cmd=scheduled_query_poll > 2024-06-19T11:27:48,645 INFO [00b77a5e-7cec-4e10-a0ae-f94450a56ab0 > HiveServer2-Handler-Pool: Thread-54] session.HiveSessionImpl: executing > SELEC > T emp.emp_id, emp.emp_name, dept.dept_nameFROM emp > JOIN dept ON emp.dept_id = dept.dept_id > 2024-06-19T11:27:48,654 INFO [00b77a5e-7cec-4e10-a0ae-f94450a
Fwd: about hive4.0.0 error
-- Forwarded message - 发件人: 张三 Date: 2024年6月19日周三 12:55 Subject: about hive4.0.0 error To: Dear Hive team, I encountered an issue while using the latest version of Hive, 4.0.0. I am not sure if this is a bug. The details are as follows: I am using Hadoop version 3.3.6 and have set up a fully distributed cluster. The Hive version is 4.0.0, with one master server and one client. Currently, I am connecting to Hive via the Beeline client. When executing a join in Hive, I encountered the following error: ``` 0: jdbc:hive2://node1:1> SELECT emp.emp_id, emp.emp_name, dept.dept_name . . . . . . . . . . . . . .> FROM emp . . . . . . . . . . . . . .> JOIN dept ON emp.dept_id = dept.dept_id; INFO : Compiling command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc): SELECT emp.emp_id, emp.emp_name, dept.dept_name FROM emp JOIN dept ON emp.dept_id = dept.dept_id INFO : No Stats for default@emp, Columns: emp_name, dept_id, emp_id INFO : No Stats for default@dept, Columns: dept_name, dept_id INFO : Semantic Analysis Completed (retrial = false) INFO : Created Hive schema: Schema(fieldSchemas:[FieldSchema(name:emp.emp_id, type:int, comment:null), FieldSchema(name:emp.emp_name, type:strin g, comment:null), FieldSchema(name:dept.dept_name, type:string, comment:null)], properties:null)INFO : Completed compiling command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc); Time taken: 0.894 seconds INFO : Concurrency mode is disabled, not creating a lock manager INFO : Executing command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc): SELECT emp.emp_id, emp.emp_name, dept.dept_name FROM emp JOIN dept ON emp.dept_id = dept.dept_id WARN : Hive-on-MR is deprecated in Hive 2 and may not be available in the future versions. Consider using a different execution engine (i.e. tez ) or using Hive 1.X releases.INFO : Query ID = root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc INFO : Total jobs = 1 INFO : Starting task [Stage-4:MAPREDLOCAL] in serial mode ERROR : Execution failed with exit status: 1 ERROR : Obtaining error information ERROR : Task failed! Task ID: Stage-4 Logs: ERROR : /tmp/root/hive.log ERROR : FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask INFO : Completed executing command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc); Time taken: 4.461 seconds Error: Error while compiling statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask (state=08S0 1,code=1) ``` I checked the log on the Hive server at /tmp/root/hive.log and found the following error information: ``` 2024-06-19T11:22:56,454 INFO [NotificationEventPoll 0] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: name=metast ore.batch.retrieve.max defaultValue=50 2024-06-19T11:23:01,656 INFO [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=scheduled_query_poll 2024-06-19T11:23:56,375 INFO [NotificationEventPoll 0] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: name=metast ore.batch.retrieve.max defaultValue=50 2024-06-19T11:24:01,946 INFO [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=scheduled_query_poll 2024-06-19T11:24:56,373 INFO [NotificationEventPoll 0] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: name=metast ore.batch.retrieve.max defaultValue=50 2024-06-19T11:25:02,197 INFO [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=scheduled_query_poll 2024-06-19T11:25:56,376 INFO [NotificationEventPoll 0] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: name=metast ore.batch.retrieve.max defaultValue=50 2024-06-19T11:26:02,390 INFO [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=scheduled_query_poll 2024-06-19T11:26:56,373 INFO [NotificationEventPoll 0] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value: name=metast ore.batch.retrieve.max defaultValue=50 2024-06-19T11:27:02,660 INFO [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=scheduled_query_poll 2024-06-19T11:27:48,645 INFO [00b77a5e-7cec-4e10-a0ae-f94450a56ab0 HiveServer2-Handler-Pool: Thread-54] session.HiveSessionImpl: executing SELEC T emp.emp_id, emp.emp_name, dept.dept_nameFROM emp JOIN dept ON emp.dept_id = dept.dept_id 2024-06-19T11:27:48,654 INFO [00b77a5e-7cec-4e10-a0ae-f94450a56ab0 HiveServer2-Handler-Pool: Thread-54] operation.OperationManager: Adding opera tion: OperationHandle [opType=EXECUTE_STATEMENT, getHandleIdentifier()=9c5817e6-131a-4e60-bfe3-faa066a61119] SessionHandle [00b77a5e-7cec-4e10-a0ae-f94450a56ab0]2024-06-19T11:27:48,654 INFO [00b77a5e-7cec-4e10-a0ae-f94450a56ab0 HiveServer2-Handler-Pool: Thread-54] common.LogUtils: Thread context registra tion is done.2024-06-19T11:27:48,654 INFO [00b77a5e-7cec-