[jira] [Commented] (LENS-952) Bump up enunciate version to work with java 8

2016-07-29 Thread Puneet Gupta (JIRA) 

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

Puneet Gupta commented on LENS-952:
---

Waiting for this to start merge for lens 2.6. 
[~deepak.barr] - Can you reply to the review comments and submit the patch if 
no more changes are required.


> Bump up enunciate version to work with java 8
> -
>
> Key: LENS-952
> URL: https://issues.apache.org/jira/browse/LENS-952
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: build
>Reporter: Amareshwari Sriramadasu
>Assignee: Deepak Barr
> Fix For: 2.6
>
>
> We are depending on 1.28 version of enunciate, which does not work on java 8. 
> We should move to latest version to work fine with java8.



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

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

2016-07-29 Thread Hudson (JIRA) 

[ 
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-1242) JDBCDriver cancel query is taking huge time

2016-07-29 Thread Hudson (JIRA) 

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

Hudson commented on LENS-1242:
--

UNSTABLE: Integrated in Lens-Commit #1310 (See 
[https://builds.apache.org/job/Lens-Commit/1310/])
LENS-1242 : Fix JDBCDriver cancel query to call statement.cancel (puneet.gupta: 
rev 9b402aee35e52fcf235974429cee760883b42271)
* lens-driver-jdbc/src/test/resources/drivers/jdbc/jdbc1/jdbcdriver-site.xml
* lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java
* src/site/apt/admin/jdbcdriver-config.apt
* lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java
* 
lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriverConfConstants.java
* lens-driver-jdbc/src/main/resources/jdbcdriver-default.xml


> JDBCDriver cancel query is taking huge time
> ---
>
> Key: LENS-1242
> URL: https://issues.apache.org/jira/browse/LENS-1242
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
> Fix For: 2.6
>
> Attachments: LENS-1242.patch
>
>
> We are seeing Cancel on JDBC is taking huge time in production.
> Here are few logs :
> {noformat}
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - CancelQuery: 
> session: standalone="yes"?>617e95ae-397f-46ea-9b20-f472e614d673761a20c0-80b8-4406-a614-b38e21fa5b34
>  query:18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.conf.HiveConf - Using 
> the default value passed in for log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.ql.session.SessionState 
> - Updating thread name to 617e95ae-397f-46ea-9b20-f472e614d673 
> grizzly-http-server-43
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Updating status for 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 05:54:56 [18a411f0-b62e-48e9-821c-f34da98fedbc] [StatusPoller] 
> INFO  org.apache.lens.server.query.QueryExecutionServiceImpl - Updating 
> status for 18a411f0-b62e-48e9-821c-f34da98fedbc
>  Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
>  to Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.driver.jdbc.JDBCDriver - jdbc/prod Cancelled query : 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Query 
> 18a411f0-b62e-48e9-821c-f34da98fedbc cancelled successfully
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.session.LensSessionImpl - Removing 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from active queries for session 
> 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.conf.HiveConf - Using the default value passed in for 
> log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.ql.session.SessionState - Resetting thread name to  
> grizzly-http-server-43
> {noformat}
> It took more than 10 minutes for cancelling from above logs.



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

[jira] [Commented] (LENS-1242) JDBCDriver cancel query is taking huge time

2016-07-29 Thread Hudson (JIRA) 

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

Hudson commented on LENS-1242:
--

FAILURE: Integrated in Lens-Commit-Java8 #222 (See 
[https://builds.apache.org/job/Lens-Commit-Java8/222/])
LENS-1242 : Fix JDBCDriver cancel query to call statement.cancel (puneet.gupta: 
rev 9b402aee35e52fcf235974429cee760883b42271)
* lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java
* lens-driver-jdbc/src/test/resources/drivers/jdbc/jdbc1/jdbcdriver-site.xml
* 
lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriverConfConstants.java
* src/site/apt/admin/jdbcdriver-config.apt
* lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java
* lens-driver-jdbc/src/main/resources/jdbcdriver-default.xml


> JDBCDriver cancel query is taking huge time
> ---
>
> Key: LENS-1242
> URL: https://issues.apache.org/jira/browse/LENS-1242
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
> Fix For: 2.6
>
> Attachments: LENS-1242.patch
>
>
> We are seeing Cancel on JDBC is taking huge time in production.
> Here are few logs :
> {noformat}
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - CancelQuery: 
> session: standalone="yes"?>617e95ae-397f-46ea-9b20-f472e614d673761a20c0-80b8-4406-a614-b38e21fa5b34
>  query:18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.conf.HiveConf - Using 
> the default value passed in for log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.ql.session.SessionState 
> - Updating thread name to 617e95ae-397f-46ea-9b20-f472e614d673 
> grizzly-http-server-43
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Updating status for 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 05:54:56 [18a411f0-b62e-48e9-821c-f34da98fedbc] [StatusPoller] 
> INFO  org.apache.lens.server.query.QueryExecutionServiceImpl - Updating 
> status for 18a411f0-b62e-48e9-821c-f34da98fedbc
>  Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
>  to Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.driver.jdbc.JDBCDriver - jdbc/prod Cancelled query : 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Query 
> 18a411f0-b62e-48e9-821c-f34da98fedbc cancelled successfully
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.session.LensSessionImpl - Removing 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from active queries for session 
> 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.conf.HiveConf - Using the default value passed in for 
> log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.ql.session.SessionState - Resetting thread name to  
> grizzly-http-server-43
> {noformat}
> It took more than 10 minutes for cancelling from above logs.



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

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

2016-07-29 Thread Hudson (JIRA) 

[ 
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

2016-07-29 Thread Hadoop QA (JIRA) 

[ 
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

2016-07-29 Thread Hadoop QA (JIRA) 

[ 
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] [Updated] (LENS-798) Pre commit job failures

2016-07-29 Thread Amareshwari Sriramadasu (JIRA) 

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

Amareshwari Sriramadasu updated LENS-798:
-
Fix Version/s: 2.6

> Pre commit job failures
> ---
>
> Key: LENS-798
> URL: https://issues.apache.org/jira/browse/LENS-798
> Project: Apache Lens
>  Issue Type: Task
>  Components: build, test
>Reporter: Rajat Khandelwal
> Fix For: 2.6
>
>




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

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

2016-07-29 Thread Puneet Gupta (JIRA) 

[ 
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] [Updated] (LENS-892) Log lens Session details in Query Logs

2016-07-29 Thread Puneet Gupta (JIRA) 

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

Puneet Gupta updated LENS-892:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> 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] [Updated] (LENS-1242) JDBCDriver cancel query is taking huge time

2016-07-29 Thread Puneet Gupta (JIRA) 

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

Puneet Gupta updated LENS-1242:
---
Fix Version/s: 2.6

> JDBCDriver cancel query is taking huge time
> ---
>
> Key: LENS-1242
> URL: https://issues.apache.org/jira/browse/LENS-1242
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
> Fix For: 2.6
>
> Attachments: LENS-1242.patch
>
>
> We are seeing Cancel on JDBC is taking huge time in production.
> Here are few logs :
> {noformat}
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - CancelQuery: 
> session: standalone="yes"?>617e95ae-397f-46ea-9b20-f472e614d673761a20c0-80b8-4406-a614-b38e21fa5b34
>  query:18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.conf.HiveConf - Using 
> the default value passed in for log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.ql.session.SessionState 
> - Updating thread name to 617e95ae-397f-46ea-9b20-f472e614d673 
> grizzly-http-server-43
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Updating status for 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 05:54:56 [18a411f0-b62e-48e9-821c-f34da98fedbc] [StatusPoller] 
> INFO  org.apache.lens.server.query.QueryExecutionServiceImpl - Updating 
> status for 18a411f0-b62e-48e9-821c-f34da98fedbc
>  Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
>  to Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.driver.jdbc.JDBCDriver - jdbc/prod Cancelled query : 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Query 
> 18a411f0-b62e-48e9-821c-f34da98fedbc cancelled successfully
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.session.LensSessionImpl - Removing 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from active queries for session 
> 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.conf.HiveConf - Using the default value passed in for 
> log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.ql.session.SessionState - Resetting thread name to  
> grizzly-http-server-43
> {noformat}
> It took more than 10 minutes for cancelling from above logs.



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

[jira] [Commented] (LENS-1242) JDBCDriver cancel query is taking huge time

2016-07-29 Thread Puneet Gupta (JIRA) 

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

Puneet Gupta commented on LENS-1242:


Committed. Thanks [~amareshwari]

> JDBCDriver cancel query is taking huge time
> ---
>
> Key: LENS-1242
> URL: https://issues.apache.org/jira/browse/LENS-1242
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
> Fix For: 2.6
>
> Attachments: LENS-1242.patch
>
>
> We are seeing Cancel on JDBC is taking huge time in production.
> Here are few logs :
> {noformat}
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - CancelQuery: 
> session: standalone="yes"?>617e95ae-397f-46ea-9b20-f472e614d673761a20c0-80b8-4406-a614-b38e21fa5b34
>  query:18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.conf.HiveConf - Using 
> the default value passed in for log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.ql.session.SessionState 
> - Updating thread name to 617e95ae-397f-46ea-9b20-f472e614d673 
> grizzly-http-server-43
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Updating status for 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 05:54:56 [18a411f0-b62e-48e9-821c-f34da98fedbc] [StatusPoller] 
> INFO  org.apache.lens.server.query.QueryExecutionServiceImpl - Updating 
> status for 18a411f0-b62e-48e9-821c-f34da98fedbc
>  Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
>  to Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.driver.jdbc.JDBCDriver - jdbc/prod Cancelled query : 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Query 
> 18a411f0-b62e-48e9-821c-f34da98fedbc cancelled successfully
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.session.LensSessionImpl - Removing 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from active queries for session 
> 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.conf.HiveConf - Using the default value passed in for 
> log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.ql.session.SessionState - Resetting thread name to  
> grizzly-http-server-43
> {noformat}
> It took more than 10 minutes for cancelling from above logs.



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

[jira] [Updated] (LENS-1242) JDBCDriver cancel query is taking huge time

2016-07-29 Thread Puneet Gupta (JIRA) 

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

Puneet Gupta updated LENS-1242:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> JDBCDriver cancel query is taking huge time
> ---
>
> Key: LENS-1242
> URL: https://issues.apache.org/jira/browse/LENS-1242
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
> Fix For: 2.6
>
> Attachments: LENS-1242.patch
>
>
> We are seeing Cancel on JDBC is taking huge time in production.
> Here are few logs :
> {noformat}
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - CancelQuery: 
> session: standalone="yes"?>617e95ae-397f-46ea-9b20-f472e614d673761a20c0-80b8-4406-a614-b38e21fa5b34
>  query:18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.conf.HiveConf - Using 
> the default value passed in for log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.ql.session.SessionState 
> - Updating thread name to 617e95ae-397f-46ea-9b20-f472e614d673 
> grizzly-http-server-43
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Updating status for 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 05:54:56 [18a411f0-b62e-48e9-821c-f34da98fedbc] [StatusPoller] 
> INFO  org.apache.lens.server.query.QueryExecutionServiceImpl - Updating 
> status for 18a411f0-b62e-48e9-821c-f34da98fedbc
>  Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
>  to Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.driver.jdbc.JDBCDriver - jdbc/prod Cancelled query : 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Query 
> 18a411f0-b62e-48e9-821c-f34da98fedbc cancelled successfully
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.session.LensSessionImpl - Removing 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from active queries for session 
> 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.conf.HiveConf - Using the default value passed in for 
> log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.ql.session.SessionState - Resetting thread name to  
> grizzly-http-server-43
> {noformat}
> It took more than 10 minutes for cancelling from above logs.



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

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

2016-07-29 Thread Puneet Gupta (JIRA) 

[ 
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-1242) JDBCDriver cancel query is taking huge time

2016-07-29 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on LENS-1242:
-

Applied patch: 
[LENS-1242.patch|https://issues.apache.org/jira/secure/attachment/12820936/LENS-1242.patch]
 and ran command: mvn clean install -fae. Result: Success. Build Job: 
https://builds.apache.org/job/PreCommit-Lens-Build/761/

> JDBCDriver cancel query is taking huge time
> ---
>
> Key: LENS-1242
> URL: https://issues.apache.org/jira/browse/LENS-1242
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
> Attachments: LENS-1242.patch
>
>
> We are seeing Cancel on JDBC is taking huge time in production.
> Here are few logs :
> {noformat}
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - CancelQuery: 
> session: standalone="yes"?>617e95ae-397f-46ea-9b20-f472e614d673761a20c0-80b8-4406-a614-b38e21fa5b34
>  query:18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.conf.HiveConf - Using 
> the default value passed in for log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.ql.session.SessionState 
> - Updating thread name to 617e95ae-397f-46ea-9b20-f472e614d673 
> grizzly-http-server-43
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Updating status for 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 05:54:56 [18a411f0-b62e-48e9-821c-f34da98fedbc] [StatusPoller] 
> INFO  org.apache.lens.server.query.QueryExecutionServiceImpl - Updating 
> status for 18a411f0-b62e-48e9-821c-f34da98fedbc
>  Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
>  to Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.driver.jdbc.JDBCDriver - jdbc/prod Cancelled query : 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Query 
> 18a411f0-b62e-48e9-821c-f34da98fedbc cancelled successfully
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.session.LensSessionImpl - Removing 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from active queries for session 
> 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.conf.HiveConf - Using the default value passed in for 
> log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.ql.session.SessionState - Resetting thread name to  
> grizzly-http-server-43
> {noformat}
> It took more than 10 minutes for cancelling from above logs.



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

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

2016-07-29 Thread Hadoop QA (JIRA) 

[ 
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)

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

2016-07-29 Thread Amareshwari Sriramadasu (JIRA) 

 [ 
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)

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

2016-07-29 Thread Amareshwari Sriramadasu (JIRA) 

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

Amareshwari Sriramadasu updated LENS-892:
-
Attachment: LENS-892.patch

Straight forward patch.

> 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: Puneet Gupta
>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)

Re: Review Request 50603: LENS-1242 : Fix JDBCDriver cancel query to call statement.cancel

2016-07-29 Thread Puneet Gupta 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50603/#review144083
---


Ship it!




Ship It!

- Puneet Gupta


On July 29, 2016, 11:26 a.m., Amareshwari Sriramadasu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50603/
> ---
> 
> (Updated July 29, 2016, 11:26 a.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1242
> https://issues.apache.org/jira/browse/LENS-1242
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> - Updated JDBCDriver cancel to call statement.cancel
> - At JDBCDriver level we can configure if statement.cancel is supported or 
> not. If set to false, it wont be called.
> - Extened cancel test actually run a long running query and cancel it.
> 
> 
> Diffs
> -
> 
>   lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java 
> 8047302 
>   
> lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriverConfConstants.java
>  ac0682d 
>   lens-driver-jdbc/src/main/resources/jdbcdriver-default.xml 66645b9 
>   
> lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java
>  491aa69 
>   lens-driver-jdbc/src/test/resources/drivers/jdbc/jdbc1/jdbcdriver-site.xml 
> 1202074 
>   src/site/apt/admin/jdbcdriver-config.apt 96c98ad 
> 
> Diff: https://reviews.apache.org/r/50603/diff/
> 
> 
> Testing
> ---
> 
> Here are the test times in millis:
> testCancelQuery(true) org.apache.lens.driver.jdbc.TestJdbcDriver  185
> testCancelQuery(false)org.apache.lens.driver.jdbc.TestJdbcDriver  
> 52
> 
> 
> Thanks,
> 
> Amareshwari Sriramadasu
> 
>

[jira] [Updated] (LENS-1242) JDBCDriver cancel query is taking huge time

2016-07-29 Thread Amareshwari Sriramadasu (JIRA) 

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

Amareshwari Sriramadasu updated LENS-1242:
--
Status: Patch Available  (was: Open)

> JDBCDriver cancel query is taking huge time
> ---
>
> Key: LENS-1242
> URL: https://issues.apache.org/jira/browse/LENS-1242
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
> Attachments: LENS-1242.patch
>
>
> We are seeing Cancel on JDBC is taking huge time in production.
> Here are few logs :
> {noformat}
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - CancelQuery: 
> session: standalone="yes"?>617e95ae-397f-46ea-9b20-f472e614d673761a20c0-80b8-4406-a614-b38e21fa5b34
>  query:18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.conf.HiveConf - Using 
> the default value passed in for log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 05:54:19 [1113a9e8-86cd-43eb-b5bb-ad718a7e87cd] 
> [grizzly-http-server-43] INFO  org.apache.hadoop.hive.ql.session.SessionState 
> - Updating thread name to 617e95ae-397f-46ea-9b20-f472e614d673 
> grizzly-http-server-43
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Updating status for 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 05:54:19 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 05:54:56 [18a411f0-b62e-48e9-821c-f34da98fedbc] [StatusPoller] 
> INFO  org.apache.lens.server.query.QueryExecutionServiceImpl - Updating 
> status for 18a411f0-b62e-48e9-821c-f34da98fedbc
>  Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
>  to Progress: 0.0
> Status: RUNNING
> Status Message: 18a411f0-b62e-48e9-821c-f34da98fedbc is running
> Is Result Set Available: false
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.driver.jdbc.JDBCDriver - jdbc/prod Cancelled query : 
> 18a411f0-b62e-48e9-821c-f34da98fedbc
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.query.QueryExecutionServiceImpl - Query 
> 18a411f0-b62e-48e9-821c-f34da98fedbc cancelled successfully
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.api.query.QueryContext - Updating status of 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from Progress: 0.0
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.lens.server.session.LensSessionImpl - Removing 
> 18a411f0-b62e-48e9-821c-f34da98fedbc from active queries for session 
> 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.conf.HiveConf - Using the default value passed in for 
> log id: 617e95ae-397f-46ea-9b20-f472e614d673
> 28 Jul 2016 06:14:38 [18a411f0-b62e-48e9-821c-f34da98fedbc] 
> [617e95ae-397f-46ea-9b20-f472e614d673 grizzly-http-server-43] INFO  
> org.apache.hadoop.hive.ql.session.SessionState - Resetting thread name to  
> grizzly-http-server-43
> {noformat}
> It took more than 10 minutes for cancelling from above logs.



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

Re: Review Request 50603: LENS-1242 : Fix JDBCDriver cancel query to call statement.cancel

2016-07-29 Thread Amareshwari Sriramadasu 


> On July 29, 2016, 11:13 a.m., Puneet Gupta wrote:
> > lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java, 
> > line 511
> > 
> >
> > Do we need this configurable ? We can try either way and log the output 
> > if its not supported (SQLFeatureNotSupportedException)

I was not sure if all driver also throw SQLFeatureNotSupportedException as 
documented. So, added a configuration to play with it on production setup, if 
required.
During tests noticed that HSQL DB is actually calling close on cancel - which 
its not terminating the query immediately.


- Amareshwari


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50603/#review144079
---


On July 29, 2016, 10:48 a.m., Amareshwari Sriramadasu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50603/
> ---
> 
> (Updated July 29, 2016, 10:48 a.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1242
> https://issues.apache.org/jira/browse/LENS-1242
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> - Updated JDBCDriver cancel to call statement.cancel
> - At JDBCDriver level we can configure if statement.cancel is supported or 
> not. If set to false, it wont be called.
> - Extened cancel test actually run a long running query and cancel it.
> 
> 
> Diffs
> -
> 
>   lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java 
> 8047302 
>   
> lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriverConfConstants.java
>  ac0682d 
>   lens-driver-jdbc/src/main/resources/jdbcdriver-default.xml 66645b9 
>   
> lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java
>  491aa69 
>   lens-driver-jdbc/src/test/resources/drivers/jdbc/jdbc1/jdbcdriver-site.xml 
> 1202074 
>   src/site/apt/admin/jdbcdriver-config.apt 96c98ad 
> 
> Diff: https://reviews.apache.org/r/50603/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Amareshwari Sriramadasu
> 
>

Re: Review Request 50603: LENS-1242 : Fix JDBCDriver cancel query to call statement.cancel

2016-07-29 Thread Puneet Gupta 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50603/#review144079
---




lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java 
(line 511)


Do we need this configurable ? We can try either way and log the output if 
its not supported (SQLFeatureNotSupportedException)


- Puneet Gupta


On July 29, 2016, 10:48 a.m., Amareshwari Sriramadasu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50603/
> ---
> 
> (Updated July 29, 2016, 10:48 a.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1242
> https://issues.apache.org/jira/browse/LENS-1242
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> - Updated JDBCDriver cancel to call statement.cancel
> - At JDBCDriver level we can configure if statement.cancel is supported or 
> not. If set to false, it wont be called.
> - Extened cancel test actually run a long running query and cancel it.
> 
> 
> Diffs
> -
> 
>   lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java 
> 8047302 
>   
> lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriverConfConstants.java
>  ac0682d 
>   lens-driver-jdbc/src/main/resources/jdbcdriver-default.xml 66645b9 
>   
> lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java
>  491aa69 
>   lens-driver-jdbc/src/test/resources/drivers/jdbc/jdbc1/jdbcdriver-site.xml 
> 1202074 
>   src/site/apt/admin/jdbcdriver-config.apt 96c98ad 
> 
> Diff: https://reviews.apache.org/r/50603/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Amareshwari Sriramadasu
> 
>

Review Request 50603: LENS-1242 : Fix JDBCDriver cancel query to call statement.cancel

2016-07-29 Thread Amareshwari Sriramadasu 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50603/
---

Review request for lens.


Bugs: LENS-1242
https://issues.apache.org/jira/browse/LENS-1242


Repository: lens


Description
---

- Updated JDBCDriver cancel to call statement.cancel
- At JDBCDriver level we can configure if statement.cancel is supported or not. 
If set to false, it wont be called.
- Extened cancel test actually run a long running query and cancel it.


Diffs
-

  lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java 
8047302 
  
lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriverConfConstants.java
 ac0682d 
  lens-driver-jdbc/src/main/resources/jdbcdriver-default.xml 66645b9 
  
lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java 
491aa69 
  lens-driver-jdbc/src/test/resources/drivers/jdbc/jdbc1/jdbcdriver-site.xml 
1202074 
  src/site/apt/admin/jdbcdriver-config.apt 96c98ad 

Diff: https://reviews.apache.org/r/50603/diff/


Testing
---


Thanks,

Amareshwari Sriramadasu

Re: Review Request 50600: LENS-1243: Support Asynchronous status updates from drivers

2016-07-29 Thread Puneet Gupta 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50600/#review144069
---




lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java 
(lines 316 - 319)


Do we need to syncronize this on query context to make sure that cancel 
call and this code is thread safe.



lens-server-api/src/main/java/org/apache/lens/server/api/driver/AbstractLensDriver.java
 (line 110)






lens-server-api/src/main/java/org/apache/lens/server/api/driver/StatusUpdateMethod.java
 (line 21)


Feel that PULL (sync)  model is more relaible . Is there a way to have the 
best of both worlds :-) ? 
Relaibility of PULL(sync) model and swiftness of PUSH(Asyn) model.



lens-server-api/src/main/java/org/apache/lens/server/api/driver/StatusUpdateMethod.java
 (line 26)


Should we chnage to PULL, PUSH ?



lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java
 (line 794)


We can miss adding this listerer if the query execution finishes very fast.


- Puneet Gupta


On July 29, 2016, 8:23 a.m., Rajat Khandelwal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50600/
> ---
> 
> (Updated July 29, 2016, 8:23 a.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1243
> https://issues.apache.org/jira/browse/LENS-1243
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> 
> Diffs
> -
> 
>   lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java 
> 8047302d880a99fc04dac82b58a67d968e242dd1 
>   
> lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java
>  491aa6976d6e73ddfb45494823cae7d6a3429887 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/AbstractLensDriver.java
>  f1d844a1987d7f7990b2e10f03d2e3af8e0294e0 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/DriverQueryStatus.java
>  2374c1e4b2737a0d1ea7123232800413baa9a560 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/LensDriver.java
>  95ea3608e612aff44ec78eee003c05ccd3068ffb 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/QueryDriverStatusUpdateListener.java
>  PRE-CREATION 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/StatusUpdateMethod.java
>  PRE-CREATION 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/query/AbstractQueryContext.java
>  e160f58bfb45cffb05b9f6be19db3bc7605dde57 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/query/QueryContext.java
>  2641b606faa20943a5f3b9de9b729380a35e8c25 
>   
> lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java
>  fddd3e490ade5eb4a6dce74ba17269c052390367 
> 
> Diff: https://reviews.apache.org/r/50600/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Rajat Khandelwal
> 
>

[jira] [Commented] (LENS-996) Improvements in filters of query list api

2016-07-29 Thread Hudson (JIRA) 

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

Hudson commented on LENS-996:
-

UNSTABLE: Integrated in Lens-Commit-Java8 #221 (See 
[https://builds.apache.org/job/Lens-Commit-Java8/221/])
LENS-996: Improvements in filters of query list api (rajatgupta59: rev 
f4da1f0b1fead1fc91694acb3280f79b5050820d)
* lens-server/src/test/java/org/apache/lens/server/query/TestLensDAO.java
* lens-cli/src/main/java/org/apache/lens/cli/commands/LensQueryCommands.java
* lens-client/src/main/java/org/apache/lens/client/LensClient.java
* lens-server/src/main/java/org/apache/lens/server/query/LensServerDAO.java
* lens-cli/src/test/java/org/apache/lens/cli/TestLensQueryCommands.java
* lens-cube/src/test/java/org/apache/lens/cube/parse/TestTimeRangeWriter.java
* lens-cube/src/main/java/org/apache/lens/cube/metadata/DateUtil.java
* lens-server/src/test/java/org/apache/lens/server/query/TestQueryService.java
* 
lens-server/src/main/java/org/apache/lens/server/query/QueryServiceResource.java
* lens-client/src/main/java/org/apache/lens/client/LensStatement.java
* 
lens-server-api/src/main/java/org/apache/lens/server/api/query/QueryExecutionService.java
* 
lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java
* lens-server/src/main/java/org/apache/lens/server/util/UtilityMethods.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/BetweenTimeRangeWriter.java
* lens-cube/src/test/java/org/apache/lens/cube/metadata/TestDateUtil.java


> Improvements in filters of query list api
> -
>
> Key: LENS-996
> URL: https://issues.apache.org/jira/browse/LENS-996
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-996.04.patch, LENS-996.06.patch, LENS-996.07.patch, 
> LENS-996.08.patch, LENS-996.09.patch, LENS-996.10.patch, LENS-996.12.patch, 
> rb50133.patch
>
>
> 1. fromDate and endDate should also take human readable dates. 
> DateUtil.resolveDate can be used. 
> 2. the status filter should be case-insensitive. 
> 3. (maybe) the user filter and status filter can take multiple comma 
> separated values and return the union in the result. 



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

Re: Review Request 50600: LENS-1243: Support Asynchronous status updates from drivers

2016-07-29 Thread Amareshwari Sriramadasu 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50600/#review144070
---



We already have registerForCompletionNotification in driver api. Should we use 
that updates from JDBC and other drivers - instead of adding another 
StatusUpdateMethod and etc. ?

- Amareshwari Sriramadasu


On July 29, 2016, 8:23 a.m., Rajat Khandelwal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50600/
> ---
> 
> (Updated July 29, 2016, 8:23 a.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1243
> https://issues.apache.org/jira/browse/LENS-1243
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> 
> Diffs
> -
> 
>   lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java 
> 8047302d880a99fc04dac82b58a67d968e242dd1 
>   
> lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java
>  491aa6976d6e73ddfb45494823cae7d6a3429887 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/AbstractLensDriver.java
>  f1d844a1987d7f7990b2e10f03d2e3af8e0294e0 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/DriverQueryStatus.java
>  2374c1e4b2737a0d1ea7123232800413baa9a560 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/LensDriver.java
>  95ea3608e612aff44ec78eee003c05ccd3068ffb 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/QueryDriverStatusUpdateListener.java
>  PRE-CREATION 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/driver/StatusUpdateMethod.java
>  PRE-CREATION 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/query/AbstractQueryContext.java
>  e160f58bfb45cffb05b9f6be19db3bc7605dde57 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/query/QueryContext.java
>  2641b606faa20943a5f3b9de9b729380a35e8c25 
>   
> lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java
>  fddd3e490ade5eb4a6dce74ba17269c052390367 
> 
> Diff: https://reviews.apache.org/r/50600/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Rajat Khandelwal
> 
>

[jira] [Commented] (LENS-996) Improvements in filters of query list api

2016-07-29 Thread Hudson (JIRA) 

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

Hudson commented on LENS-996:
-

FAILURE: Integrated in Lens-Commit #1309 (See 
[https://builds.apache.org/job/Lens-Commit/1309/])
LENS-996: Improvements in filters of query list api (rajatgupta59: rev 
f4da1f0b1fead1fc91694acb3280f79b5050820d)
* lens-server/src/test/java/org/apache/lens/server/query/TestQueryService.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/BetweenTimeRangeWriter.java
* lens-cube/src/test/java/org/apache/lens/cube/parse/TestTimeRangeWriter.java
* lens-cli/src/main/java/org/apache/lens/cli/commands/LensQueryCommands.java
* lens-client/src/main/java/org/apache/lens/client/LensStatement.java
* lens-client/src/main/java/org/apache/lens/client/LensClient.java
* lens-cli/src/test/java/org/apache/lens/cli/TestLensQueryCommands.java
* 
lens-server/src/main/java/org/apache/lens/server/query/QueryServiceResource.java
* lens-cube/src/test/java/org/apache/lens/cube/metadata/TestDateUtil.java
* lens-server/src/main/java/org/apache/lens/server/util/UtilityMethods.java
* lens-cube/src/main/java/org/apache/lens/cube/metadata/DateUtil.java
* lens-server/src/test/java/org/apache/lens/server/query/TestLensDAO.java
* 
lens-server-api/src/main/java/org/apache/lens/server/api/query/QueryExecutionService.java
* lens-server/src/main/java/org/apache/lens/server/query/LensServerDAO.java
* 
lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java


> Improvements in filters of query list api
> -
>
> Key: LENS-996
> URL: https://issues.apache.org/jira/browse/LENS-996
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-996.04.patch, LENS-996.06.patch, LENS-996.07.patch, 
> LENS-996.08.patch, LENS-996.09.patch, LENS-996.10.patch, LENS-996.12.patch, 
> rb50133.patch
>
>
> 1. fromDate and endDate should also take human readable dates. 
> DateUtil.resolveDate can be used. 
> 2. the status filter should be case-insensitive. 
> 3. (maybe) the user filter and status filter can take multiple comma 
> separated values and return the union in the result. 



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

[jira] [Updated] (LENS-996) Improvements in filters of query list api

2016-07-29 Thread Rajat Khandelwal (JIRA) 

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

Rajat Khandelwal updated LENS-996:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Improvements in filters of query list api
> -
>
> Key: LENS-996
> URL: https://issues.apache.org/jira/browse/LENS-996
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-996.04.patch, LENS-996.06.patch, LENS-996.07.patch, 
> LENS-996.08.patch, LENS-996.09.patch, LENS-996.10.patch, LENS-996.12.patch, 
> rb50133.patch
>
>
> 1. fromDate and endDate should also take human readable dates. 
> DateUtil.resolveDate can be used. 
> 2. the status filter should be case-insensitive. 
> 3. (maybe) the user filter and status filter can take multiple comma 
> separated values and return the union in the result. 



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

[jira] [Commented] (LENS-996) Improvements in filters of query list api

2016-07-29 Thread Rajat Khandelwal (JIRA) 

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

Rajat Khandelwal commented on LENS-996:
---

Committed myself.

> Improvements in filters of query list api
> -
>
> Key: LENS-996
> URL: https://issues.apache.org/jira/browse/LENS-996
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-996.04.patch, LENS-996.06.patch, LENS-996.07.patch, 
> LENS-996.08.patch, LENS-996.09.patch, LENS-996.10.patch, LENS-996.12.patch, 
> rb50133.patch
>
>
> 1. fromDate and endDate should also take human readable dates. 
> DateUtil.resolveDate can be used. 
> 2. the status filter should be case-insensitive. 
> 3. (maybe) the user filter and status filter can take multiple comma 
> separated values and return the union in the result. 



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

[jira] [Commented] (LENS-996) Improvements in filters of query list api

2016-07-29 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on LENS-996:


Applied patch: 
[LENS-996.12.patch|https://issues.apache.org/jira/secure/attachment/12820912/LENS-996.12.patch]
 and ran command: mvn clean install -fae. Result: Success. Build Job: 
https://builds.apache.org/job/PreCommit-Lens-Build/760/

> Improvements in filters of query list api
> -
>
> Key: LENS-996
> URL: https://issues.apache.org/jira/browse/LENS-996
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-996.04.patch, LENS-996.06.patch, LENS-996.07.patch, 
> LENS-996.08.patch, LENS-996.09.patch, LENS-996.10.patch, LENS-996.12.patch, 
> rb50133.patch
>
>
> 1. fromDate and endDate should also take human readable dates. 
> DateUtil.resolveDate can be used. 
> 2. the status filter should be case-insensitive. 
> 3. (maybe) the user filter and status filter can take multiple comma 
> separated values and return the union in the result. 



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

[jira] [Commented] (LENS-1243) Support Asynchronous status updates from drivers

2016-07-29 Thread Rajat Khandelwal (JIRA) 

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

Rajat Khandelwal commented on LENS-1243:


Created https://reviews.apache.org/r/50600/

> Support Asynchronous status updates from drivers
> 
>
> Key: LENS-1243
> URL: https://issues.apache.org/jira/browse/LENS-1243
> Project: Apache Lens
>  Issue Type: Improvement
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>




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

Review Request 50600: LENS-1243: Support Asynchronous status updates from drivers

2016-07-29 Thread Rajat Khandelwal 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50600/
---

Review request for lens.


Bugs: LENS-1243
https://issues.apache.org/jira/browse/LENS-1243


Repository: lens


Description
---


Diffs
-

  lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java 
8047302d880a99fc04dac82b58a67d968e242dd1 
  
lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java 
491aa6976d6e73ddfb45494823cae7d6a3429887 
  
lens-server-api/src/main/java/org/apache/lens/server/api/driver/AbstractLensDriver.java
 f1d844a1987d7f7990b2e10f03d2e3af8e0294e0 
  
lens-server-api/src/main/java/org/apache/lens/server/api/driver/DriverQueryStatus.java
 2374c1e4b2737a0d1ea7123232800413baa9a560 
  
lens-server-api/src/main/java/org/apache/lens/server/api/driver/LensDriver.java 
95ea3608e612aff44ec78eee003c05ccd3068ffb 
  
lens-server-api/src/main/java/org/apache/lens/server/api/driver/QueryDriverStatusUpdateListener.java
 PRE-CREATION 
  
lens-server-api/src/main/java/org/apache/lens/server/api/driver/StatusUpdateMethod.java
 PRE-CREATION 
  
lens-server-api/src/main/java/org/apache/lens/server/api/query/AbstractQueryContext.java
 e160f58bfb45cffb05b9f6be19db3bc7605dde57 
  
lens-server-api/src/main/java/org/apache/lens/server/api/query/QueryContext.java
 2641b606faa20943a5f3b9de9b729380a35e8c25 
  
lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java
 fddd3e490ade5eb4a6dce74ba17269c052390367 

Diff: https://reviews.apache.org/r/50600/diff/


Testing
---


Thanks,

Rajat Khandelwal

Re: Review Request 50133: LENS-996: Improvements in filters of query list api

2016-07-29 Thread Rajat Khandelwal 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50133/
---

(Updated July 29, 2016, 1:36 p.m.)


Review request for lens.


Bugs: LENS-996
https://issues.apache.org/jira/browse/LENS-996


Repository: lens


Description
---

1. fromDate and endDate should also take human readable dates. 
DateUtil.resolveDate can be used. 
2. the status filter should be case-insensitive. 
3. (maybe) the user filter and status filter can take multiple comma separated 
values and return the union in the result.


Diffs (updated)
-

  lens-cli/src/main/java/org/apache/lens/cli/commands/LensQueryCommands.java 
af05951393e5e433fd644f20a9c23f7ba3507947 
  lens-cli/src/test/java/org/apache/lens/cli/TestLensQueryCommands.java 
0bf2a6687537b36b7987be27ad7be80d1b289f13 
  lens-client/src/main/java/org/apache/lens/client/LensClient.java 
d3ec97d6e8ac506952d1aa5e29ad0fb2c8f8f917 
  lens-client/src/main/java/org/apache/lens/client/LensStatement.java 
3cae7175229503bb90abadb7a3048b353b82e36d 
  lens-cube/src/main/java/org/apache/lens/cube/metadata/DateUtil.java 
b82cd95b5633b91e03cf1df8ac2602cb7798099a 
  
lens-cube/src/main/java/org/apache/lens/cube/parse/BetweenTimeRangeWriter.java 
bd19d4ccb68390c1f11341579fbc4e18e15390ab 
  lens-cube/src/test/java/org/apache/lens/cube/metadata/TestDateUtil.java 
7e239f33dccd237c9bee3732931309bb8ea62753 
  lens-cube/src/test/java/org/apache/lens/cube/parse/TestTimeRangeWriter.java 
87e128ffb8a17bf42f53a89cc7ccedbdf1ad59c2 
  
lens-server-api/src/main/java/org/apache/lens/server/api/query/QueryExecutionService.java
 4f4d4aa60923ab0a50a478347d26238571b692c1 
  lens-server/src/main/java/org/apache/lens/server/query/LensServerDAO.java 
1d6125c4eebb99ab3d2e392de69768deaf3b8e44 
  
lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java
 fddd3e490ade5eb4a6dce74ba17269c052390367 
  
lens-server/src/main/java/org/apache/lens/server/query/QueryServiceResource.java
 803bbe3db982dc74ba2a1bdba94fc68879dcd351 
  lens-server/src/main/java/org/apache/lens/server/util/UtilityMethods.java 
42d9fe0b5470318ae60dc3137113774ad383e743 
  lens-server/src/test/java/org/apache/lens/server/query/TestLensDAO.java 
7679a068161f2d072b1f6e96d0e96109e3bd6bc9 
  lens-server/src/test/java/org/apache/lens/server/query/TestQueryService.java 
e8aa223b76b96d402ea27fd6cc2f43e52ff8199c 

Diff: https://reviews.apache.org/r/50133/diff/


Testing
---


Thanks,

Rajat Khandelwal

[jira] [Commented] (LENS-996) Improvements in filters of query list api

2016-07-29 Thread Rajat Khandelwal (JIRA) 

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

Rajat Khandelwal commented on LENS-996:
---

Taking patch from reviewboard and attaching

> Improvements in filters of query list api
> -
>
> Key: LENS-996
> URL: https://issues.apache.org/jira/browse/LENS-996
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-996.04.patch, LENS-996.06.patch, LENS-996.07.patch, 
> LENS-996.08.patch, LENS-996.09.patch, LENS-996.10.patch, LENS-996.12.patch, 
> rb50133.patch
>
>
> 1. fromDate and endDate should also take human readable dates. 
> DateUtil.resolveDate can be used. 
> 2. the status filter should be case-insensitive. 
> 3. (maybe) the user filter and status filter can take multiple comma 
> separated values and return the union in the result. 



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

[jira] [Updated] (LENS-996) Improvements in filters of query list api

2016-07-29 Thread Rajat Khandelwal (JIRA) 

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

Rajat Khandelwal updated LENS-996:
--
Attachment: LENS-996.12.patch

> Improvements in filters of query list api
> -
>
> Key: LENS-996
> URL: https://issues.apache.org/jira/browse/LENS-996
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-996.04.patch, LENS-996.06.patch, LENS-996.07.patch, 
> LENS-996.08.patch, LENS-996.09.patch, LENS-996.10.patch, LENS-996.12.patch, 
> rb50133.patch
>
>
> 1. fromDate and endDate should also take human readable dates. 
> DateUtil.resolveDate can be used. 
> 2. the status filter should be case-insensitive. 
> 3. (maybe) the user filter and status filter can take multiple comma 
> separated values and return the union in the result. 



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

[jira] [Work started] (LENS-1243) Support Asynchronous status updates from drivers

2016-07-29 Thread Rajat Khandelwal (JIRA) 

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

Work on LENS-1243 started by Rajat Khandelwal.
--
> Support Asynchronous status updates from drivers
> 
>
> Key: LENS-1243
> URL: https://issues.apache.org/jira/browse/LENS-1243
> Project: Apache Lens
>  Issue Type: Improvement
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>




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

[jira] [Created] (LENS-1243) Support Asynchronous status updates from drivers

2016-07-29 Thread Rajat Khandelwal (JIRA) 
Rajat Khandelwal created LENS-1243:
--

 Summary: Support Asynchronous status updates from drivers
 Key: LENS-1243
 URL: https://issues.apache.org/jira/browse/LENS-1243
 Project: Apache Lens
  Issue Type: Improvement
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal






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

[jira] [Commented] (LENS-996) Improvements in filters of query list api

2016-07-29 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on LENS-996:


Applied patch: 
[rb50133.patch|https://issues.apache.org/jira/secure/attachment/12820869/rb50133.patch]
 and ran command: mvn clean install -fae. Result: Failure. Build Job: 
https://builds.apache.org/job/PreCommit-Lens-Build/759/

> Improvements in filters of query list api
> -
>
> Key: LENS-996
> URL: https://issues.apache.org/jira/browse/LENS-996
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-996.04.patch, LENS-996.06.patch, LENS-996.07.patch, 
> LENS-996.08.patch, LENS-996.09.patch, LENS-996.10.patch, rb50133.patch
>
>
> 1. fromDate and endDate should also take human readable dates. 
> DateUtil.resolveDate can be used. 
> 2. the status filter should be case-insensitive. 
> 3. (maybe) the user filter and status filter can take multiple comma 
> separated values and return the union in the result. 



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

[jira] [Commented] (LENS-996) Improvements in filters of query list api

2016-07-29 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on LENS-996:


Applied patch: 
[rb50133.patch|https://issues.apache.org/jira/secure/attachment/12820869/rb50133.patch]
 and ran command: mvn clean install -fae. Result: Failure. Build Job: 
https://builds.apache.org/job/PreCommit-Lens-Build/758/

> Improvements in filters of query list api
> -
>
> Key: LENS-996
> URL: https://issues.apache.org/jira/browse/LENS-996
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-996.04.patch, LENS-996.06.patch, LENS-996.07.patch, 
> LENS-996.08.patch, LENS-996.09.patch, LENS-996.10.patch, rb50133.patch
>
>
> 1. fromDate and endDate should also take human readable dates. 
> DateUtil.resolveDate can be used. 
> 2. the status filter should be case-insensitive. 
> 3. (maybe) the user filter and status filter can take multiple comma 
> separated values and return the union in the result. 



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