[
https://issues.apache.org/jira/browse/LENS-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260003#comment-14260003
]
Hudson commented on LENS-162:
-----------------------------
FAILURE: Integrated in Lens-Commit #63 (See
[https://builds.apache.org/job/Lens-Commit/63/])
LENS-162 : Adds capability to tune cost to priority ranges (Rajat Khandelwal
via amareshwari) (amareshwari.sr: rev 9e5bbcf5b96bd6a44139fb2fc0589927f2c60ede)
* lens-driver-hive/src/main/java/org/apache/lens/driver/hive/HiveDriver.java
* lens-driver-hive/src/test/java/org/apache/lens/driver/hive/TestHiveDriver.java
*
lens-driver-hive/src/main/java/org/apache/lens/driver/hive/priority/DurationBasedQueryPriorityDecider.java
* lens-driver-hive/src/main/resources/hivedriver-default.xml
* src/site/apt/admin/hivedriver-config.apt
> Add capability to tune cost to priority ranges
> ----------------------------------------------
>
> Key: LENS-162
> URL: https://issues.apache.org/jira/browse/LENS-162
> Project: Apache Lens
> Issue Type: Improvement
> Components: driver-hive, server
> Affects Versions: 2.0
> Reporter: Rajat Khandelwal
> Assignee: Rajat Khandelwal
> Fix For: 2.0
>
> Attachments: rb29397.patch
>
>
> Right now it's hardcoded to
> {code}
> VERY_HIGH,7.0,HIGH,30.0,NORMAL,90,LOW
> {code}
> But we might need to tune this too. e.g. we never want VERY_HIGH queries. in
> that case we need a capability to tune this via configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)