[
https://issues.apache.org/jira/browse/HIVE-20535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616632#comment-16616632
]
Hive QA commented on HIVE-20535:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12939842/HIVE-20535.3.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 14941 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/13825/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/13825/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-13825/
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: 12939842 - PreCommit-HIVE-Build
> Add new configuration to set the size of the global compile lock
> ----------------------------------------------------------------
>
> Key: HIVE-20535
> URL: https://issues.apache.org/jira/browse/HIVE-20535
> Project: Hive
> Issue Type: Task
> Components: HiveServer2
> Reporter: denys kuzmenko
> Assignee: denys kuzmenko
> Priority: Major
> Attachments: HIVE-20535.1.patch, HIVE-20535.2.patch,
> HIVE-20535.3.patch
>
>
> When removing the compile lock, it is quite risky to remove it entirely.
> It would be good to provide a pool size for the concurrent compilation, so
> the administrator can limit the load
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
