You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Himanshu Gahlaut (JIRA)" <ji...@apache.org> on 2015/06/23 16:06:01 UTC
[jira] [Updated] (LENS-619) Applying Query Running Constraint
before allowing a query to run
[ https://issues.apache.org/jira/browse/LENS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Himanshu Gahlaut updated LENS-619:
----------------------------------
Summary: Applying Query Running Constraint before allowing a query to run (was: Fair Usage Policy for using Lens)
> Applying Query Running Constraint before allowing a query to run
> ----------------------------------------------------------------
>
> Key: LENS-619
> URL: https://issues.apache.org/jira/browse/LENS-619
> Project: Apache Lens
> Issue Type: New Feature
> Reporter: Himanshu Gahlaut
> Assignee: Himanshu Gahlaut
>
> Fair Usage Policy for using Lens
> After a user has used the lens system beyond fair usage policy, he will get lens features in degraded mode.
> One of the forms of fair usage policy could be that at any point in time only N queries can be present in RUNNING state for a user.
> If N queries of a user are in RUNNING state, then a new query submitted by same user will stay in QUEUED state until one of the N queries in RUNNING state have moved to SUCCESSFUL, FAILED, OR CANCELLED state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)