[jira] [Commented] (LENS-892) Log lens Session details in Query Logs
[ https://issues.apache.org/jira/browse/LENS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399365#comment-15399365 ] Hudson commented on LENS-892: - UNSTABLE: Integrated in Lens-Commit #1310 (See [https://builds.apache.org/job/Lens-Commit/1310/]) LENS-892: Log lens Session details in Query Logs (puneet.gupta: rev c326de77c0185ceb0c20895e33f75452549ff72c) * lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java > 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)
[jira] [Commented] (LENS-892) Log lens Session details in Query Logs
[ https://issues.apache.org/jira/browse/LENS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399334#comment-15399334 ] Hudson commented on LENS-892: - FAILURE: Integrated in Lens-Commit-Java8 #222 (See [https://builds.apache.org/job/Lens-Commit-Java8/222/]) LENS-892: Log lens Session details in Query Logs (puneet.gupta: rev c326de77c0185ceb0c20895e33f75452549ff72c) * lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java > 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)
[jira] [Commented] (LENS-892) Log lens Session details in Query Logs
[ https://issues.apache.org/jira/browse/LENS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399321#comment-15399321 ] Hadoop QA commented on LENS-892: Applied patch: [LENS-892.patch|https://issues.apache.org/jira/secure/attachment/12820941/LENS-892.patch] and ran command: mvn clean install -fae. Result: Failure. Build Job: https://builds.apache.org/job/PreCommit-Lens-Build/764/ > 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)
[jira] [Commented] (LENS-892) Log lens Session details in Query Logs
[ https://issues.apache.org/jira/browse/LENS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399302#comment-15399302 ] Hadoop QA commented on LENS-892: Applied patch: [LENS-892.patch|https://issues.apache.org/jira/secure/attachment/12820941/LENS-892.patch] and ran command: mvn clean install -fae. Result: Failure. Build Job: https://builds.apache.org/job/PreCommit-Lens-Build/762/ > 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)
[jira] [Commented] (LENS-892) Log lens Session details in Query Logs
[ https://issues.apache.org/jira/browse/LENS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399271#comment-15399271 ] Puneet Gupta commented on LENS-892: --- Committed. Thanks [~amareshwari] > 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)
[jira] [Commented] (LENS-892) Log lens Session details in Query Logs
[ https://issues.apache.org/jira/browse/LENS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399266#comment-15399266 ] Puneet Gupta commented on LENS-892: --- +1 > 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)
[jira] [Commented] (LENS-892) Log lens Session details in Query Logs
[ https://issues.apache.org/jira/browse/LENS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399203#comment-15399203 ] Hadoop QA commented on LENS-892: Applied patch: [LENS-892.patch|https://issues.apache.org/jira/secure/attachment/12820941/LENS-892.patch] and ran command: mvn clean install -fae. Result: Failure. Build Job: https://builds.apache.org/job/PreCommit-Lens-Build/763/ > 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)
