[ 
https://issues.apache.org/jira/browse/HIVE-22770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025505#comment-17025505
 ] 

Hive QA commented on HIVE-22770:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12992064/HIVE-22770.06.patch

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

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

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/20390/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20390/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20390/

Messages:
{noformat}
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
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12992064 - PreCommit-HIVE-Build

> Skip interning of MapWork fields during deserialization
> -------------------------------------------------------
>
>                 Key: HIVE-22770
>                 URL: https://issues.apache.org/jira/browse/HIVE-22770
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Major
>         Attachments: HIVE-22770.01.patch, HIVE-22770.01.patch, 
> HIVE-22770.02.patch, HIVE-22770.02.patch, HIVE-22770.03.patch, 
> HIVE-22770.04.patch, HIVE-22770.05.patch, HIVE-22770.06.patch
>
>
> HIVE-19937 introduced some interning logic into mapwork deserialization 
> process, but it's only related to spark, maybe we should skip this for tez, 
> reducing the cpu pressure in tez tasks.
> UPDATE: Hive on spark is not supported anymore, the  MapWorkSerializer can be 
> completely removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to