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/02/24 10:56:04 UTC

[jira] [Comment Edited] (LENS-283) Add latency metering for each resolver in cube query rewriter

    [ https://issues.apache.org/jira/browse/LENS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334705#comment-14334705 ] 

Himanshu Gahlaut edited comment on LENS-283 at 2/24/15 9:55 AM:
----------------------------------------------------------------

Have we explored @Timed, @Metered and @ExceptionMetered annotations ? Are there any challenges / disadvantages of using them in our context ?

Have a look at this for the implementations of annotations interfaces:
https://github.corp.inmobi.com/inmobi-commons/metrics-collector


was (Author: himanshu.gahlaut):
Have we explored @Timed, @Metered and @ExceptionMetered annotations ? Are there any challenges / disadvantages of using them in our context ?

> Add latency metering for each resolver in cube query rewriter
> -------------------------------------------------------------
>
>                 Key: LENS-283
>                 URL: https://issues.apache.org/jira/browse/LENS-283
>             Project: Apache Lens
>          Issue Type: Improvement
>          Components: cube
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 2.1
>
>
> Since cube query rewriter go through many resolvers sequentially, we want to find how much time is taken by each resolver in each phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)