[
https://issues.apache.org/jira/browse/LENS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651422#comment-14651422
]
Amareshwari Sriramadasu commented on LENS-124:
----------------------------------------------
bq. Pre-requisite is that the queries are already saved and prepared in Lens
and can be executed later. Not sure if bind arg support is available
Want to understand more on why we want to use prepared queries for scheduling
queries. Prepared queries are actually prepared on underlying driver also, if
drivers implement prepare.
bq. Parameterization of queries to allow fixed, moving time windows
We allow timerange to be specified as now.day - 2days (to start from say 2 days
back) and now.day (till today). We can look at the spec for relative time in
timerange spec. and see if that does not suffice for scheduling queries. - See
http://lens.incubator.apache.org/user/olap-cube.html#How_to_pass_timerange_in_cubeQL
for more details.
> Add scheduler service on lens
> -----------------------------
>
> Key: LENS-124
> URL: https://issues.apache.org/jira/browse/LENS-124
> Project: Apache Lens
> Issue Type: New Feature
> Components: server
> Reporter: Amareshwari Sriramadasu
> Labels: Hackathon-July
> Attachments: Lens Scheduler API.pdf
>
>
> Query scheduler service should provide following services
> * Schedule a query
> ** Periodically
> ** On data availability, for ex: whenever a day's data is available
> * Look at status of scheduled query
> ** Mostly the current run status
> * Look at the output of scheduled query - through email?
> * Update scheduled query
> ** Update the query
> ** Update the frequency
> ** Update the configuration
> * Look at stats of scheduled query
> ** number of failures
> ** number of reruns
> ** Get handles for completed queries
> * Cancel a scheduled query
> * Pause and resume a scheduled query
> * Look at all scheduled queries
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
