[
https://issues.apache.org/jira/browse/HIVE-22726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016074#comment-17016074
]
Hive QA commented on HIVE-22726:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12990883/HIVE-22726.1.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 17876 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/20185/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20185/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20185/
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: 12990883 - PreCommit-HIVE-Build
> TopN Key optimizer should use array instead of priority queue
> -------------------------------------------------------------
>
> Key: HIVE-22726
> URL: https://issues.apache.org/jira/browse/HIVE-22726
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-22726.1.patch
>
>
> The TopN key optimizer currently uses a priority queue for keeping track of
> the largest/smallest rows. Its max size is the same as the user specified
> limit. This should be replaced a more cache line friendly array with a small
> (128) maximum size and see how much performance is gained.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
