You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2016/07/29 11:53:20 UTC
[jira] [Updated] (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 ]
Amareshwari Sriramadasu updated LENS-892:
-----------------------------------------
Assignee: Amareshwari Sriramadasu (was: Puneet Gupta)
Fix Version/s: 2.6
Status: Patch Available (was: Open)
> 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
> Components: server
> Reporter: Puneet Gupta
> Assignee: Amareshwari Sriramadasu
> Priority: Trivial
> Labels: newbie
> Fix For: 2.6
>
> Attachments: LENS-892.patch
>
>
> 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)