hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-23447) Avoid sending configs to tasks and AM which are only relevant for HS2
Date Tue, 12 May 2020 07:04:00 GMT


Hive QA commented on HIVE-23447:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 17265 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 13002666 - PreCommit-HIVE-Build

> Avoid sending configs to tasks and AM which are only relevant for HS2
> ---------------------------------------------------------------------
>                 Key: HIVE-23447
>                 URL:
>             Project: Hive
>          Issue Type: Task
>          Components: Configuration
>            Reporter: Ashutosh Chauhan
>            Assignee: Ashutosh Chauhan
>            Priority: Major
>         Attachments: HIVE-23447.patch
> There are many configs which are only relevant for HS2. Longer term fix for this is to
split HiveConf in multiple config classes relevant only for HS2, HMS, AM and tasks. And use
only the objects in process where its relevant. In the interim, we can avoid configs with
large value strings to send across.

This message was sent by Atlassian Jira

View raw message