You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lens.apache.org by "Puneet Gupta (JIRA)" <ji...@apache.org> on 2015/12/08 12:32:10 UTC

[jira] [Assigned] (LENS-892) Log lens Session details in Query Logs

     [ https://issues.apache.org/jira/browse/LENS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Puneet Gupta reassigned LENS-892:
---------------------------------

    Assignee: Puneet Gupta

> Log  lens Session details in Query Logs
> ---------------------------------------
>
>                 Key: LENS-892
>                 URL: https://issues.apache.org/jira/browse/LENS-892
>             Project: Apache Lens
>          Issue Type: Improvement
>            Reporter: Puneet Gupta
>            Assignee: Puneet Gupta
>            Priority: Trivial
>              Labels: newbie
>
> As of now its not easy to map Lens Queries to Lens Sessions . 
> It can be made trivial if the session details are logged in query logs .
> This can be required in many scenarios. 
> One such scenario : attribute a lens session close (say a user issued a query via CLI and then exited the CLI before query was scheduled for a run on lens server)  as a reason for  failure/cancellation of queries triggered via that session . 



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