[
https://issues.apache.org/jira/browse/HIVE-16590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999229#comment-15999229
]
Hive QA commented on HIVE-16590:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12866510/HIVE-16590.1.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 10653 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/5063/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/5063/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-5063/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12866510 - PreCommit-HIVE-Build
> Make initializing dag names in SparkWork thread safe for parallel compilation
> (HIVE-13512)
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-16590
> URL: https://issues.apache.org/jira/browse/HIVE-16590
> Project: Hive
> Issue Type: Bug
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Attachments: HIVE-16590.1.patch
>
>
> In HIVE-13512 some modifications to {{TezWork}} were made to avoid generating
> duplicate dag ids during parallel compilation. We should do the equivalent
> for {{SparkWork}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
