[
https://issues.apache.org/jira/browse/PHOENIX-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825005#comment-16825005
]
Hudson commented on PHOENIX-5252:
---------------------------------
ABORTED: Integrated in Jenkins build PreCommit-PHOENIX-Build #2528 (See
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/2528/])
PHOENIX-5252 Add job priority option to UpdateStatisticsTool (chinmayskulkarni:
rev a3fbbb8fa098ae1420823bc03e5f9b5203a22962)
* (edit)
phoenix-core/src/test/java/org/apache/phoenix/schema/stats/UpdateStatisticsToolTest.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/schema/stats/UpdateStatisticsTool.java
> Add job priority option to UpdateStatisticsTool
> -----------------------------------------------
>
> Key: PHOENIX-5252
> URL: https://issues.apache.org/jira/browse/PHOENIX-5252
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Xinyi Yan
> Assignee: Xinyi Yan
> Priority: Major
> Labels: stats, statsCollection
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-5252-4.x-HBase-1.4.patch,
> PHOENIX-5252-master.patch, PHOENIX-5252.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This Jira adds a new command line option that allows users to specify the job
> priority to the tool.
> The current implementation doesn't support the MR job priority, and it might
> limit the usecase. For instance, we have 10 running jobs in a queue, and we
> get a new urgent MR job. Instead of deleting all currently running jobs,
> inserting a high priority job could solve this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
