Re: Review Request 48842: LENS-1184 REST API for the Scheduler

2016-06-27 Thread Amareshwari Sriramadasu

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


Fix it, then Ship it!




API resources and the actions look fine.


lens-server/src/main/java/org/apache/lens/server/scheduler/store/SchedulerDAO.java
 (line 43)


Update with latest DAO class from master


- Amareshwari Sriramadasu


On June 25, 2016, 10:50 a.m., Ajay Yadava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48842/
> ---
> 
> (Updated June 25, 2016, 10:50 a.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1184
> https://issues.apache.org/jira/browse/LENS-1184
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> This patch adds REST API signatures and some other skeleton classes for 
> Scheduler.
> 
> scheduler/
> 
> jobs - POST - submits a new job.
> 
> jobs/stats - GET - get stats for all jobs
> 
> jobs/{jobHandle} - GET - get job definition
>  - DELETE - Delete job 
>  - POST - (based on query parameter it will - schedule / 
> expire / suspend / resume a job.
> 
> 
> jobs/{jobHandle}/stats - GET - get stats for a particular job.
> 
> jobs/{jobHandle}/instances - GET - get all instances for a given job.
> 
> instances/{instanceHandle}/ - GET - get details for a given instance.
> - POST - based upon "action" query parameter - 
> Kill or rerurn an instance
> 
> 
> Diffs
> -
> 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/scheduler/SchedulerService.java
>  b6ec093 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/LensScheduler.java 
> PRE-CREATION 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java
>  abc4621 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerServiceImpl.java
>  ce98601 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/store/SchedulerDAO.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/48842/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ajay Yadava
> 
>



[jira] [Commented] (LENS-1205) Fix ToXMLString class to serialise and deserialise Xjob

2016-06-27 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on LENS-1205:
-

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

> Fix ToXMLString class to serialise and deserialise Xjob
> ---
>
> Key: LENS-1205
> URL: https://issues.apache.org/jira/browse/LENS-1205
> Project: Apache Lens
>  Issue Type: Bug
>Reporter: Lavkesh Lahngir
>Assignee: Lavkesh Lahngir
> Attachments: fix-ToXMLString.patch
>
>
> Classes generated from xsd do not contain the @XMLRootElement. We need to 
> Pass a JAXBElement object while calling marshal() method. Also at the time 
> unmarshal(), it returns the JAXBElement. 



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


[jira] [Updated] (LENS-1205) Fix ToXMLString class to serialise and deserialise Xjob

2016-06-27 Thread Lavkesh Lahngir (JIRA)

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

Lavkesh Lahngir updated LENS-1205:
--
Description: Classes generated from xsd do not contain the @XMLRootElement. 
We need to Pass a JAXBElement object while calling marshal() method. Also at 
the time unmarshal(), it returns the JAXBElement. 

> Fix ToXMLString class to serialise and deserialise Xjob
> ---
>
> Key: LENS-1205
> URL: https://issues.apache.org/jira/browse/LENS-1205
> Project: Apache Lens
>  Issue Type: Bug
>Reporter: Lavkesh Lahngir
>Assignee: Lavkesh Lahngir
> Attachments: fix-ToXMLString.patch
>
>
> Classes generated from xsd do not contain the @XMLRootElement. We need to 
> Pass a JAXBElement object while calling marshal() method. Also at the time 
> unmarshal(), it returns the JAXBElement. 



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


Review Request 49275: [LENS-1205] Fix XMLToString

2016-06-27 Thread Lavkesh Lahngir

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

Review request for lens.


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


Repository: lens


Description
---

Classes generated from xsd do not contain the @XMLRootElement. We need to Pass 
a JAXBElement object while calling marshal() method. Also at the time 
unmarshal(), it returns the JAXBElement.


Diffs
-

  lens-api/src/main/java/org/apache/lens/api/ToXMLString.java fca56a8 
  
lens-api/src/test/resources/toString/org.apache.lens.api.query.SchedulerJobHandle.xml
 ef7d0c7 
  
lens-api/src/test/resources/toString/org.apache.lens.api.query.SchedulerJobHandle.yaml
 567d8cf 
  lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerDAO.java 
e866eb3 

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


Testing
---


Thanks,

Lavkesh Lahngir



[jira] [Updated] (LENS-1205) Fix ToXMLString class to serialise and deserialise Xjob

2016-06-27 Thread Lavkesh Lahngir (JIRA)

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

Lavkesh Lahngir updated LENS-1205:
--
Attachment: fix-ToXMLString.patch

> Fix ToXMLString class to serialise and deserialise Xjob
> ---
>
> Key: LENS-1205
> URL: https://issues.apache.org/jira/browse/LENS-1205
> Project: Apache Lens
>  Issue Type: Bug
>Reporter: Lavkesh Lahngir
>Assignee: Lavkesh Lahngir
> Attachments: fix-ToXMLString.patch
>
>




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


[jira] [Created] (LENS-1205) Fix ToXMLString class to serialise and deserialise Xjob

2016-06-27 Thread Lavkesh Lahngir (JIRA)
Lavkesh Lahngir created LENS-1205:
-

 Summary: Fix ToXMLString class to serialise and deserialise Xjob
 Key: LENS-1205
 URL: https://issues.apache.org/jira/browse/LENS-1205
 Project: Apache Lens
  Issue Type: Bug
Reporter: Lavkesh Lahngir
Assignee: Lavkesh Lahngir






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


[jira] [Commented] (LENS-988) [Server] StateStore for LensScheduler

2016-06-27 Thread Hudson (JIRA)

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

Hudson commented on LENS-988:
-

FAILURE: Integrated in Lens-Commit-Java8 #192 (See 
[https://builds.apache.org/job/Lens-Commit-Java8/192/])
LENS-988: StateStore for LensScheduler (rajatgupta59: rev 
600b9be4c3d32894472b9762bdc96a8df9683625)
* src/site/apt/admin/config.apt
* 
lens-server/src/main/java/org/apache/lens/server/scheduler/util/UtilityMethods.java
* 
lens-server-api/src/main/java/org/apache/lens/server/api/LensConfConstants.java
* lens-server/src/main/resources/lensserver-default.xml
* lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerDAO.java


> [Server] StateStore for LensScheduler
> -
>
> Key: LENS-988
> URL: https://issues.apache.org/jira/browse/LENS-988
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: server
>Reporter: Ajay Yadava
>Assignee: Lavkesh Lahngir
> Fix For: 2.6
>
> Attachments: scheduler-store.patch
>
>
> Dividing server side component into smaller tasks. This task is for creating 
> a persistent store for lens scheduler.



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


[jira] [Commented] (LENS-988) [Server] StateStore for LensScheduler

2016-06-27 Thread Hudson (JIRA)

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

Hudson commented on LENS-988:
-

UNSTABLE: Integrated in Lens-Commit #1281 (See 
[https://builds.apache.org/job/Lens-Commit/1281/])
LENS-988: StateStore for LensScheduler (rajatgupta59: rev 
600b9be4c3d32894472b9762bdc96a8df9683625)
* lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerDAO.java
* 
lens-server/src/main/java/org/apache/lens/server/scheduler/util/UtilityMethods.java
* src/site/apt/admin/config.apt
* lens-server/src/main/resources/lensserver-default.xml
* 
lens-server-api/src/main/java/org/apache/lens/server/api/LensConfConstants.java


> [Server] StateStore for LensScheduler
> -
>
> Key: LENS-988
> URL: https://issues.apache.org/jira/browse/LENS-988
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: server
>Reporter: Ajay Yadava
>Assignee: Lavkesh Lahngir
> Fix For: 2.6
>
> Attachments: scheduler-store.patch
>
>
> Dividing server side component into smaller tasks. This task is for creating 
> a persistent store for lens scheduler.



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


[jira] [Updated] (LENS-988) [Server] StateStore for LensScheduler

2016-06-27 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-988:
--
Fix Version/s: 2.6

> [Server] StateStore for LensScheduler
> -
>
> Key: LENS-988
> URL: https://issues.apache.org/jira/browse/LENS-988
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: server
>Reporter: Ajay Yadava
>Assignee: Lavkesh Lahngir
> Fix For: 2.6
>
> Attachments: scheduler-store.patch
>
>
> Dividing server side component into smaller tasks. This task is for creating 
> a persistent store for lens scheduler.



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


[jira] [Commented] (LENS-988) [Server] StateStore for LensScheduler

2016-06-27 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-988:
---

Committed. Thanks [~lavkesh]

> [Server] StateStore for LensScheduler
> -
>
> Key: LENS-988
> URL: https://issues.apache.org/jira/browse/LENS-988
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: server
>Reporter: Ajay Yadava
>Assignee: Lavkesh Lahngir
> Fix For: 2.6
>
> Attachments: scheduler-store.patch
>
>
> Dividing server side component into smaller tasks. This task is for creating 
> a persistent store for lens scheduler.



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


[jira] [Updated] (LENS-988) [Server] StateStore for LensScheduler

2016-06-27 Thread Rajat Khandelwal (JIRA)

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

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

> [Server] StateStore for LensScheduler
> -
>
> Key: LENS-988
> URL: https://issues.apache.org/jira/browse/LENS-988
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: server
>Reporter: Ajay Yadava
>Assignee: Lavkesh Lahngir
> Fix For: 2.6
>
> Attachments: scheduler-store.patch
>
>
> Dividing server side component into smaller tasks. This task is for creating 
> a persistent store for lens scheduler.



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


[jira] [Commented] (LENS-988) [Server] StateStore for LensScheduler

2016-06-27 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on LENS-988:


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

> [Server] StateStore for LensScheduler
> -
>
> Key: LENS-988
> URL: https://issues.apache.org/jira/browse/LENS-988
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: server
>Reporter: Ajay Yadava
>Assignee: Lavkesh Lahngir
> Attachments: scheduler-store.patch
>
>
> Dividing server side component into smaller tasks. This task is for creating 
> a persistent store for lens scheduler.



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


Re: Review Request 49154: LENS-1202: Add client side iterator for result in python client

2016-06-27 Thread Rajat Khandelwal

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

(Updated June 27, 2016, 5:59 p.m.)


Review request for lens.


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


Repository: lens


Description
---


Diffs (updated)
-

  contrib/clients/python/lens/client/main.py 
dc604979415160ae17c9fcdcef3f258d5e38af38 
  contrib/clients/python/lens/client/models.py 
7451fe92b29531f2bdb9219239c6f2b597fe7aac 
  contrib/clients/python/lens/client/query.py 
88ce719890e8bf1c08410284583db14bb23c568c 
  contrib/clients/python/lens/client/session.py PRE-CREATION 
  contrib/clients/python/test/test_lensclient.py 
d49c55bdca924eabd0b61f540372db4c3f3e695e 

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


Testing
---


Thanks,

Rajat Khandelwal



Re: Review Request 48842: LENS-1184 REST API for the Scheduler

2016-06-27 Thread Lavkesh Lahngir

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



Can we pick up the definition of the SchedulerDAO from here. 
https://reviews.apache.org/r/49096/diff/4#1

- Lavkesh Lahngir


On June 25, 2016, 10:50 a.m., Ajay Yadava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48842/
> ---
> 
> (Updated June 25, 2016, 10:50 a.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1184
> https://issues.apache.org/jira/browse/LENS-1184
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> This patch adds REST API signatures and some other skeleton classes for 
> Scheduler.
> 
> scheduler/
> 
> jobs - POST - submits a new job.
> 
> jobs/stats - GET - get stats for all jobs
> 
> jobs/{jobHandle} - GET - get job definition
>  - DELETE - Delete job 
>  - POST - (based on query parameter it will - schedule / 
> expire / suspend / resume a job.
> 
> 
> jobs/{jobHandle}/stats - GET - get stats for a particular job.
> 
> jobs/{jobHandle}/instances - GET - get all instances for a given job.
> 
> instances/{instanceHandle}/ - GET - get details for a given instance.
> - POST - based upon "action" query parameter - 
> Kill or rerurn an instance
> 
> 
> Diffs
> -
> 
>   
> lens-server-api/src/main/java/org/apache/lens/server/api/scheduler/SchedulerService.java
>  b6ec093 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/LensScheduler.java 
> PRE-CREATION 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java
>  abc4621 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerServiceImpl.java
>  ce98601 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/store/SchedulerDAO.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/48842/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ajay Yadava
> 
>



[jira] [Commented] (LENS-1200) M/R Job failures are not getting propagated to error message

2016-06-27 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on LENS-1200:
-

Applied patch: 
[LENS-1200.2016-06-23_12:52:11.patch|https://issues.apache.org/jira/secure/attachment/12812747/LENS-1200.2016-06-23_12%3A52%3A11.patch]
 and ran command: mvn clean install -fae. Result: Failure. Build Job: 
https://builds.apache.org/job/PreCommit-Lens-Build/634/

> M/R Job failures are not getting propagated to error message
> 
>
> Key: LENS-1200
> URL: https://issues.apache.org/jira/browse/LENS-1200
> Project: Apache Lens
>  Issue Type: Bug
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1200.2016-06-23_12:29:04.patch, 
> LENS-1200.2016-06-23_12:52:11.patch
>
>




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


[jira] [Created] (LENS-1204) Gatekeep call to delete all partitions of the fact table

2016-06-27 Thread Puneet Gupta (JIRA)
Puneet Gupta created LENS-1204:
--

 Summary: Gatekeep call to delete all partitions of the fact table
 Key: LENS-1204
 URL: https://issues.apache.org/jira/browse/LENS-1204
 Project: Apache Lens
  Issue Type: Improvement
Reporter: Puneet Gupta


We should make the "filter" parameter mandatory to prevent lens server from OOM 
incase a fact has too many partitions.

Also if possible, we should make this behavior configurable and should be 
disabled by default. Based on the production scenario, we can enable this 
option if required.



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


[jira] [Created] (LENS-1203) Gatekeep call to get all partitions of the fact table

2016-06-27 Thread Puneet Gupta (JIRA)
Puneet Gupta created LENS-1203:
--

 Summary: Gatekeep call to get all partitions of the fact table 
 Key: LENS-1203
 URL: https://issues.apache.org/jira/browse/LENS-1203
 Project: Apache Lens
  Issue Type: Bug
Reporter: Puneet Gupta
Assignee: Puneet Gupta


We should make the "filter" parameter mandatory to prevent lens server from OOM 
incase a fact has too many partitions . 

Also if possible, we should make this behavior configurable and should be 
disabled by default.  Based on the production scenario, we can enable this 
option if required. 



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


[jira] [Updated] (LENS-1203) Gatekeep call to get all partitions of the fact table

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-1203:
---
Issue Type: Improvement  (was: Bug)

> Gatekeep call to get all partitions of the fact table 
> --
>
> Key: LENS-1203
> URL: https://issues.apache.org/jira/browse/LENS-1203
> Project: Apache Lens
>  Issue Type: Improvement
>Reporter: Puneet Gupta
>Assignee: Puneet Gupta
>
> We should make the "filter" parameter mandatory to prevent lens server from 
> OOM incase a fact has too many partitions . 
> Also if possible, we should make this behavior configurable and should be 
> disabled by default.  Based on the production scenario, we can enable this 
> option if required. 



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


[jira] [Commented] (LENS-778) Killing JDBC Query is not closing the connection

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta commented on LENS-778:
---

[~archana.h] can we try reproducing it .  Also is the query kill happening 
cleanly (not exception in logs)  ?

> Killing JDBC Query is not closing the connection
> 
>
> Key: LENS-778
> URL: https://issues.apache.org/jira/browse/LENS-778
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Arshad Matin
>Assignee: Badrinath Kulkarni
> Fix For: 2.6
>
>
> Use Case
> ===
> Set max connection pool to 1.
> Ran a query and killed it.
> Ran another query and it failed throwing following exception
> {noformat}
> 18 Sep 2015 07:18:51 [15e7cb89-5f0c-4741-8da6-69384c94cd01] 
> [lens-driver-jdbc-2] ERROR org.apache.lens.driver.jdbc.JDBCDriver - Error 
> executing SQL query: 15e7cb89-5f0c-4741-8da6-69384c94cd01 reason: Streaming 
> result set com.mysql.jdbc.RowDataDynamic@4651e5c3 is still active. No 
> statements may be issued when any streaming result sets are open and in use 
> on a given connection. Ensure that you have called .close() on any active 
> streaming result sets before attempting more queries.
> java.sql.SQLException: Streaming result set 
> com.mysql.jdbc.RowDataDynamic@4651e5c3 is still active. No statements may be 
> issued when any streaming result sets are open and in use on a given 
> connection. Ensure that you have called .close() on any active streaming 
> result sets before attempting more queries.
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:914) 
> ~[mysql-connector-java-5.0.8-bin.jar:na]
>   at 
> com.mysql.jdbc.MysqlIO.checkForOutstandingStreamingData(MysqlIO.java:2181) 
> ~[mysql-connector-java-5.0.8-bin.jar:na]
>   at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1542) 
> ~[mysql-connector-java-5.0.8-bin.jar:na]
>   at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723) 
> ~[mysql-connector-java-5.0.8-bin.jar:na]
>   at com.mysql.jdbc.Connection.execSQL(Connection.java:3277) 
> ~[mysql-connector-java-5.0.8-bin.jar:na]
>   at com.mysql.jdbc.Connection.execSQL(Connection.java:3206) 
> ~[mysql-connector-java-5.0.8-bin.jar:na]
>   at com.mysql.jdbc.Statement.execute(Statement.java:727) 
> ~[mysql-connector-java-5.0.8-bin.jar:na]
>   at 
> com.mchange.v2.c3p0.impl.NewProxyStatement.execute(NewProxyStatement.java:223)
>  ~[c3p0-0.9.5.jar:0.9.5]
>   at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:327)
>  [lens-driver-jdbc-2.4.0-inm.jar:2.4.0-inm]
>   at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:282)
>  [lens-driver-jdbc-2.4.0-inm.jar:2.4.0-inm]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_40]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_40]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_40]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_40]
> {noformat}



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


[jira] [Updated] (LENS-1156) TestUnionQueries.testDimAttrExpressionQuery failed in commit build

2016-06-27 Thread Amareshwari Sriramadasu (JIRA)

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

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

> TestUnionQueries.testDimAttrExpressionQuery failed in commit build
> --
>
> Key: LENS-1156
> URL: https://issues.apache.org/jira/browse/LENS-1156
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Affects Versions: 2.6
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
>Priority: Minor
> Fix For: 2.6
>
>
> https://builds.apache.org/job/Lens-Commit/org.apache.lens$lens-cube/1256/testReport/junit/org.apache.lens.cube.parse/TestUnionQueries/testDimAttrExpressionQuery/
>  has failed.
> Looking at the failure - it seems join strings and comparison is not working 
> for union queries.



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


[jira] [Updated] (LENS-586) lens query containing multiple cube queries fails rewriting if query metering is enabled.

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-586:
--
Fix Version/s: (was: 2.6)
   2.7

> lens query containing multiple cube queries fails rewriting if query metering 
> is enabled.
> -
>
> Key: LENS-586
> URL: https://issues.apache.org/jira/browse/LENS-586
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Affects Versions: 2.1
>Reporter: Rajat Khandelwal
>Assignee: Amareshwari Sriramadasu
> Fix For: 2.7
>
>




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


[jira] [Updated] (LENS-713) Describe of non-existing entities should give 404, not 500

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-713:
--
Fix Version/s: (was: 2.6)
   2.7

> Describe of non-existing entities should give 404, not 500
> --
>
> Key: LENS-713
> URL: https://issues.apache.org/jira/browse/LENS-713
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Ajay Yadava
> Fix For: 2.7
>
>




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


[jira] [Updated] (LENS-1156) TestUnionQueries.testDimAttrExpressionQuery failed in commit build

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-1156:
---
Fix Version/s: (was: 2.6)

> TestUnionQueries.testDimAttrExpressionQuery failed in commit build
> --
>
> Key: LENS-1156
> URL: https://issues.apache.org/jira/browse/LENS-1156
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Affects Versions: 2.6
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
>Priority: Minor
>
> https://builds.apache.org/job/Lens-Commit/org.apache.lens$lens-cube/1256/testReport/junit/org.apache.lens.cube.parse/TestUnionQueries/testDimAttrExpressionQuery/
>  has failed.
> Looking at the failure - it seems join strings and comparison is not working 
> for union queries.



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


[jira] [Updated] (LENS-337) Add regression for docker and ml lib

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-337:
--
Fix Version/s: (was: 2.6)

> Add regression for docker and ml lib
> 
>
> Key: LENS-337
> URL: https://issues.apache.org/jira/browse/LENS-337
> Project: Apache Lens
>  Issue Type: Task
>  Components: regression
>Reporter: Arshad Matin
>Assignee: Arshad Matin
>




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


[jira] [Updated] (LENS-535) Add unit tests for lens-regression framework

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-535:
--
Fix Version/s: (was: 2.6)

> Add unit tests for lens-regression framework
> 
>
> Key: LENS-535
> URL: https://issues.apache.org/jira/browse/LENS-535
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: regression
>Reporter: Arshad Matin
>Assignee: Arshad Matin
>




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


[jira] [Updated] (LENS-759) Setup regression for lens examples in jenkins

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-759:
--
Fix Version/s: (was: 2.6)

> Setup regression for lens examples in jenkins
> -
>
> Key: LENS-759
> URL: https://issues.apache.org/jira/browse/LENS-759
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: build, regression
>Reporter: Amareshwari Sriramadasu
>Assignee: Arshad Matin
>
> We should setup jenkins to run nightly for running examples on master branch.



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


[jira] [Updated] (LENS-620) Add profile for code coverage report

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-620:
--
Fix Version/s: (was: 2.6)

> Add profile for code coverage report
> 
>
> Key: LENS-620
> URL: https://issues.apache.org/jira/browse/LENS-620
> Project: Apache Lens
>  Issue Type: Task
>  Components: build, test
>Reporter: Arshad Matin
>Assignee: Arshad Matin
>




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


[jira] [Updated] (LENS-640) Create table query for finished_queries table does not work with MySQL 5.6

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-640:
--
Fix Version/s: (was: 2.6)

> Create table query for finished_queries table does not work with MySQL 5.6
> --
>
> Key: LENS-640
> URL: https://issues.apache.org/jira/browse/LENS-640
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Deepak Barr
>Assignee: Deepak Barr
>Priority: Minor
>
> The create query in LensServerDAO class works fine on MySQL 5.1 but throws 
> the following error on MySQL 5.6 -
> java.sql.SQLException: Column length too big for column 'metadata' (max = 
> 21845); use BLOB or TEXT instead Query: CREATE TABLE if not exists 
> finished_queries (handle varchar(255) not null unique,userquery 
> varchar(1) not null,submitter varchar(255) not null,starttime bigint, 
> endtime bigint,result varchar(255),status varchar(255), metadata 
> varchar(10), rows int, errormessage varchar(1), driverstarttime 
> bigint, driverendtime bigint, metadataclass varchar(1),queryname 
> varchar(255),submissiontime bigint) Parameters: []
> at 
> org.apache.commons.dbutils.AbstractQueryRunner.rethrow(AbstractQueryRunner.java:363)
> at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:490)
> at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:420)
> at 
> org.apache.lens.server.query.LensServerDAO.createTable(LensServerDAO.java:75)
> at 
> org.apache.lens.server.query.LensServerDAO.createFinishedQueriesTable(LensServerDAO.java:103)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.initalizeFinishedQueryStore(QueryExecutionServiceImpl.java:890)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.init(QueryExecutionServiceImpl.java:877)
> at 
> org.apache.hive.service.CompositeService.init(CompositeService.java:59)
> at org.apache.lens.server.LensServices.init(LensServices.java:206)
> at 
> org.apache.lens.server.LensServer.startServices(LensServer.java:137)
> at org.apache.lens.server.LensServer.(LensServer.java:89)
> at 
> org.apache.lens.server.LensServer.createLensServer(LensServer.java:78)
> at org.apache.lens.server.LensServer.main(LensServer.java:190)
> I figured changing the big "VARCHAR" fields to "TEXT" fields will fix the 
> error. 



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


[jira] [Updated] (LENS-384) Provide an API to list all the open session

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-384:
--
Fix Version/s: (was: 2.6)

> Provide an API to list all the open session
> ---
>
> Key: LENS-384
> URL: https://issues.apache.org/jira/browse/LENS-384
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Arshad Matin
>Assignee: Badrinath Kulkarni
>  Labels: newbie
> Attachments: LENS-384.patch
>
>




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


[jira] [Updated] (LENS-317) Server side calls for updating database jars

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-317:
--
Fix Version/s: (was: 2.6)

> Server side calls for updating database jars
> 
>
> Key: LENS-317
> URL: https://issues.apache.org/jira/browse/LENS-317
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: cube, server
>Reporter: Jaideep Dhok
>Assignee: Badrinath Kulkarni
>




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


[jira] [Updated] (LENS-855) Column headers are always comma-separated in the output file

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-855:
--
Fix Version/s: (was: 2.6)

> Column headers are always comma-separated in the output file
> 
>
> Key: LENS-855
> URL: https://issues.apache.org/jira/browse/LENS-855
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Deepak Barr
>Assignee: Deepak Barr
>
> An example scenario -
> If
> lens.query.output.write.header = true
> and
> lens.query.result.output.dir.format = ROW FORMAT DELIMITED FIELDS TERMINATED 
> BY '\t'
> then, the final output file (after resultset formatting) contains headers in 
> comma-separated format and result rows in tab-separated format.



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


[jira] [Updated] (LENS-540) Skip deploying source archive and lens-server.war

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-540:
--
Fix Version/s: (was: 2.6)

> Skip deploying source archive and lens-server.war  
> ---
>
> Key: LENS-540
> URL: https://issues.apache.org/jira/browse/LENS-540
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: build
>Reporter: Amareshwari Sriramadasu
>Assignee: Jaideep Dhok
>Priority: Critical
>
> During 2.1 release deploy, i noticed we are deploying source-release.zip and 
> lens-server war to maven repository.
> https://repository.apache.org/content/repositories/releases/org/apache/lens/apache-lens/2.1.0-beta-incubating/
> https://repository.apache.org/content/repositories/releases/org/apache/lens/lens-server/2.1.0-beta-incubating/
> Those should be skipped as their size is huge , and we are providing them 
> separate downloadable release artifacts through mirrors.



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


[jira] [Updated] (LENS-266) Resultset not honouring index and size params

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-266:
--
Fix Version/s: (was: 2.6)

> Resultset not honouring index and size params
> -
>
> Key: LENS-266
> URL: https://issues.apache.org/jira/browse/LENS-266
> Project: Apache Lens
>  Issue Type: Bug
>  Components: client, server
>Reporter: Arshad Matin
>Assignee: Puneet Gupta
>
> While fetching resultset for a query with say index = 1 and size = 1 , still 
> lens server will fetch the whole resultset



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


[jira] [Updated] (LENS-409) Fix usage of new HiveConf() and Hive.get() in ml lib

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-409:
--
Fix Version/s: (was: 2.6)

> Fix usage of new HiveConf() and Hive.get() in ml lib
> 
>
> Key: LENS-409
> URL: https://issues.apache.org/jira/browse/LENS-409
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: ml
>Reporter: Amareshwari Sriramadasu
>Assignee: Jaideep Dhok
>
> We saw new HiveConf() call is costlier : See LENS-408. The following 
> occurrences in ml-lib needs to be looked into to see if they are required.
> {noformat}
> lens-ml-lib amareshwari.sr$ git grep 'new HiveConf(' src/main/java/
> src/main/java/org/apache/lens/ml/MLUtils.java:HIVE_CONF = new HiveConf();
> src/main/java/org/apache/lens/ml/ModelLoader.java:  FileSystem fs = 
> modelPath.getFileSystem(new HiveConf());
> src/main/java/org/apache/lens/ml/spark/algos/BaseSparkAlgo.java:HiveConf 
> hiveConf = new HiveConf();
> src/main/java/org/apache/lens/ml/spark/algos/KMeansAlgo.java:HiveConf 
> hiveConf = new HiveConf();
> src/main/java/org/apache/lens/rdd/LensRDDClient.java:  protected static final 
> HiveConf HIVE_CONF = new HiveConf();
> src/main/java/org/apache/lens/server/ml/MLServiceResource.java:HIVE_CONF 
> = new HiveConf();
> {noformat}



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


[jira] [Updated] (LENS-238) DockerFile should not hardcode project version

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-238:
--
Fix Version/s: (was: 2.6)

> DockerFile should not hardcode project version
> --
>
> Key: LENS-238
> URL: https://issues.apache.org/jira/browse/LENS-238
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 2.0
>Reporter: Amareshwari Sriramadasu
>Assignee: Neerja Bhatnagar
>Priority: Minor
>
> In lens-docker/lens-test/Dockerfile,
> LENS_VERSION hardcoded. Instead it should take from ${project.version}



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


[jira] [Updated] (LENS-571) Support parallel builds for the project

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-571:
--
Fix Version/s: (was: 2.6)

> Support parallel builds for the project
> ---
>
> Key: LENS-571
> URL: https://issues.apache.org/jira/browse/LENS-571
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 2.0
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> We need to fix if any test is using a fixed path, not related to the build - 
> this is done through LENS-721.
> Another issue to fix is not to use fixed ports in any test, as they would 
> conflict with other build running and test will fail with port binding errors.



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


[jira] [Updated] (LENS-597) Lens server logs flooded with SQLException

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-597:
--
Fix Version/s: (was: 2.6)

> Lens server logs flooded with SQLException
> --
>
> Key: LENS-597
> URL: https://issues.apache.org/jira/browse/LENS-597
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Angad Singh
>Assignee: Rajat Khandelwal
>
> {noformat}
> 10 Jun 2015 06:40:47,016 [QueryPurger] WARN  
> org.apache.lens.server.query.QueryExecutionServiceImpl  - Exception while 
> purging query 
> java.sql.SQLException: Table 'lens.finished_queries' doesn't exist Query: 
> insert into finished_queries (handle, 
> userquery,submitter,starttime,endtime,result,status,metadata,rows,errormessage,driverstarttime,driverendtime,
>  metadataclass, queryname, submissiontime) values 
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) Parameters: 
> [f9fa2af5-d8d4-4aef-b106-718f444cb914, cube select apps_owned from user j 
> where source = 'raf', anonymous, 0, 1433134606782, null, FAILED, null, 0,  
> Driver :org.apache.lens.driver.hive.HiveDriver Cause :Could not find the 
> table containing column: source, 0, 0, null, , 1433134605618]
>   at 
> org.apache.commons.dbutils.AbstractQueryRunner.rethrow(AbstractQueryRunner.java:363)
>   at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:490)
>   at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:456)
>   at 
> org.apache.lens.server.query.LensServerDAO.insertFinishedQuery(LensServerDAO.java:126)
>   at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$QueryPurger.run(QueryExecutionServiceImpl.java:787)
>   at java.lang.Thread.run(Thread.java:745)
> 10 Jun 2015 06:40:47,017 [QueryPurger] WARN  
> org.apache.lens.server.query.QueryExecutionServiceImpl  - Exception while 
> purging query 
> java.sql.SQLException: Table 'lens.finished_queries' doesn't exist Query: 
> insert into finished_queries (handle, 
> userquery,submitter,starttime,endtime,result,status,metadata,rows,errormessage,driverstarttime,driverendtime,
>  metadataclass, queryname, submissiontime) values 
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) Parameters: 
> [f9fa2af5-d8d4-4aef-b106-718f444cb914, cube select apps_owned from user j 
> where source = 'raf', anonymous, 0, 1433134606782, null, FAILED, null, 0,  
> Driver :org.apache.lens.driver.hive.HiveDriver Cause :Could not find the 
> table containing column: source, 0, 0, null, , 1433134605618]
>   at 
> org.apache.commons.dbutils.AbstractQueryRunner.rethrow(AbstractQueryRunner.java:363)
>   at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:490)
>   at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:456)
>   at 
> org.apache.lens.server.query.LensServerDAO.insertFinishedQuery(LensServerDAO.java:126)
>   at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$QueryPurger.run(QueryExecutionServiceImpl.java:787)
>   at java.lang.Thread.run(Thread.java:745)
> 10 Jun 2015 06:40:47,018 [QueryPurger] WARN  
> org.apache.lens.server.query.QueryExecutionServiceImpl  - Exception while 
> purging query 
> java.sql.SQLException: Table 'lens.finished_queries' doesn't exist Query: 
> insert into finished_queries (handle, 
> userquery,submitter,starttime,endtime,result,status,metadata,rows,errormessage,driverstarttime,driverendtime,
>  metadataclass, queryname, submissiontime) values 
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) Parameters: 
> [f9fa2af5-d8d4-4aef-b106-718f444cb914, cube select apps_owned from user j 
> where source = 'raf', anonymous, 0, 1433134606782, null, FAILED, null, 0,  
> Driver :org.apache.lens.driver.hive.HiveDriver Cause :Could not find the 
> table containing column: source, 0, 0, null, , 1433134605618]
>   at 
> org.apache.commons.dbutils.AbstractQueryRunner.rethrow(AbstractQueryRunner.java:363)
>   at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:490)
>   at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:456)
>   at 
> org.apache.lens.server.query.LensServerDAO.insertFinishedQuery(LensServerDAO.java:126)
>   at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$QueryPurger.run(QueryExecutionServiceImpl.java:787)
>   at java.lang.Thread.run(Thread.java:745)
> 10 Jun 2015 06:40:47,018 [QueryPurger] WARN  
> org.apache.lens.server.query.QueryExecutionServiceImpl  - Exception while 
> purging query 
> java.sql.SQLException: Table 'lens.finished_queries' doesn't exist Query: 
> insert into finished_queries (handle, 
> userquery,submitter,starttime,endtime,result,status,metadata,rows,errormessage,driverstarttime,driverendtime,
>  metadataclass, queryname, submissiontime) values 
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) Parameters: 
> [f9fa2af5-d8d4-4aef-b106-718f444cb914, 

[jira] [Updated] (LENS-395) Lens Rest API response improvements

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-395:
--
Fix Version/s: (was: 2.6)

> Lens Rest API response improvements
> ---
>
> Key: LENS-395
> URL: https://issues.apache.org/jira/browse/LENS-395
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: client, server
>Reporter: Himanshu Gahlaut
>Assignee: Sushil Mohanty
>
> Details available in the document given below:
> https://docs.google.com/spreadsheets/d/1Q-ElKmyFr54MFDIueteDJSIdg-qWc176Tu0yUIJHbhI



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


[jira] [Updated] (LENS-837) Lens request log to capture remote host name for all REST operations

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-837:
--
Fix Version/s: (was: 2.6)

> Lens request log to capture remote host name for all REST operations
> 
>
> Key: LENS-837
> URL: https://issues.apache.org/jira/browse/LENS-837
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 2.4
>Reporter: Srikanth Sundarrajan
>Assignee: Srikanth Sundarrajan
>  Labels: REST_API
>
> Lens logs doesn't contain any information on the host from where the REST 
> operations originate. This is in general useful and particularly needed to 
> debug potential session leak issues.



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


[jira] [Updated] (LENS-812) Simplify the asserts for CandidateTablePruneCause in TestDenormalizaerResolver test

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-812:
--
Fix Version/s: (was: 2.6)

> Simplify the asserts for CandidateTablePruneCause in 
> TestDenormalizaerResolver test
> ---
>
> Key: LENS-812
> URL: https://issues.apache.org/jira/browse/LENS-812
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: cube
>Reporter: Raju Bairishetti
>Assignee: Raju Bairishetti
>
> Right now, we are checking for all kinds of possibilities of CandidateTable 
> Prunecause details in TestDenormalizerResolver. We are checking for all 
> possible combinations because  iterator on set in java8 is coming different 
> order every time.
> {code}
>Arrays.asList(CandidateTablePruneCause.columnNotFound("msr2", "msr3")))
>   || 
> entry.getValue().equals(Arrays.asList(CandidateTablePruneCause.columnNotFound("msr3",
>  "msr2";
> {code}
> It would be easier for writing the new tests if we fix this from src side 
> instead of checking for each combination in test.



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


[jira] [Commented] (LENS-973) On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta commented on LENS-973:
---

The current workaround is to save all the driver specific config via 
AbstractQueryContext#updateConf in DriverQueryHook#postDriverSelection

> On Server restart not able to launch new queries on hive if queue constraint 
> driver.max.concurrent.launched.queries.per.queue is enabled
> 
>
> Key: LENS-973
> URL: https://issues.apache.org/jira/browse/LENS-973
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Puneet Gupta
>Assignee: Sushil Mohanty
>
> {noformat}
> org.apache.lens.server.query.QueryExecutionServiceImpl - Error launching 
> query: 94487ed0-b  881-4949-9421-5344dcd3baf4
> 12041 java.lang.NullPointerException: null
> 12042 at 
> org.apache.lens.server.api.query.constraint.MaxConcurrentDriverQueriesConstraint.canLaunchWithQueueConstraint(MaxConcurrentDriverQueriesConstraint.java:64)
>  ~[lens  -server-api-2.5.3-inm.jar:2.5.3-inm]
> 12043 at 
> org.apache.lens.server.api.query.constraint.MaxConcurrentDriverQueriesConstraint.allowsLaunchOf(MaxConcurrentDriverQueriesConstraint.j
> {noformat}



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


[jira] [Updated] (LENS-609) Add more error codes in REST APIs and improve existing error messages

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-609:
--
Fix Version/s: (was: 2.6)

> Add more error codes in REST APIs and improve existing error messages
> -
>
> Key: LENS-609
> URL: https://issues.apache.org/jira/browse/LENS-609
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: server
>Reporter: Himanshu Gahlaut
>
> Read for reference on how to do this: 
> https://issues.apache.org/jira/browse/LENS-187



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


[jira] [Updated] (LENS-973) On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-973:
--
Priority: Major  (was: Critical)

> On Server restart not able to launch new queries on hive if queue constraint 
> driver.max.concurrent.launched.queries.per.queue is enabled
> 
>
> Key: LENS-973
> URL: https://issues.apache.org/jira/browse/LENS-973
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Puneet Gupta
>Assignee: Sushil Mohanty
>
> {noformat}
> org.apache.lens.server.query.QueryExecutionServiceImpl - Error launching 
> query: 94487ed0-b  881-4949-9421-5344dcd3baf4
> 12041 java.lang.NullPointerException: null
> 12042 at 
> org.apache.lens.server.api.query.constraint.MaxConcurrentDriverQueriesConstraint.canLaunchWithQueueConstraint(MaxConcurrentDriverQueriesConstraint.java:64)
>  ~[lens  -server-api-2.5.3-inm.jar:2.5.3-inm]
> 12043 at 
> org.apache.lens.server.api.query.constraint.MaxConcurrentDriverQueriesConstraint.allowsLaunchOf(MaxConcurrentDriverQueriesConstraint.j
> {noformat}



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


[jira] [Updated] (LENS-561) Adding a Rewriter at HiveDriver Level

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-561:
--
Fix Version/s: (was: 2.6)

> Adding a Rewriter at HiveDriver Level
> -
>
> Key: LENS-561
> URL: https://issues.apache.org/jira/browse/LENS-561
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: driver-hive
>Reporter: vikas singh
>Assignee: vikas singh
>
> Adding a rewriter at Hive Driver level for doing rewrites specific to Hive 
> Driver.



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


[jira] [Updated] (LENS-495) CubeColumn startTime and endTime are getting formatted according to local time zone of the machine on which code is run

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-495:
--
Fix Version/s: (was: 2.6)

> CubeColumn startTime and endTime are getting formatted according to local 
> time zone of the machine on which code is run
> ---
>
> Key: LENS-495
> URL: https://issues.apache.org/jira/browse/LENS-495
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Himanshu Gahlaut
>Assignee: Yash Sharma
>  Labels: newbie
>
> Using simple date format "-MM-dd-HH-mm", startTime 01-01-2015 will get 
> formatted to 2015-01-01-00-00 on a server / developer machine running with 
> UTC time zone where as the same will be formatted to 2015-01-01-05-30 on a 
> server / developer machine running in IST. 
> A test case which is expecting 2015-01-01-00-00 as a result of formatting 
> will run fine in UTC time zone and will fail when the same is run on a 
> machine in some other time zone. Test case can be made more generic by 
> creating expected formatted string in local time zone but thats just adding 
> un-required complexity to test case. 
> Also changing displayed time strings based on client time zone can be a 
> requirement but changing the same based on the time zone of the machine 
> (server) on which code is run seems to be an undesired behavior.
> One of the ways to fix this is to create SimpleDateFormat instance with time 
> zone as UTC and consistently use UTC everywhere to keep things simple:
> SimpleDateFormat sdf = new SimpleDateFormat("-MM-dd-HH");
> sdf.setTimeZone(TimeZone.getTimeZone("UTC"));



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


[jira] [Updated] (LENS-691) Loading DB Resource jars is not working for native tables

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-691:
--
Fix Version/s: (was: 2.6)

> Loading DB Resource jars is not working for native tables
> -
>
> Key: LENS-691
> URL: https://issues.apache.org/jira/browse/LENS-691
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Matin
>




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


[jira] [Updated] (LENS-773) Wrong Cost Calculation in case of HIVE Dimension Query

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-773:
--
Fix Version/s: (was: 2.6)

> Wrong Cost Calculation in case of HIVE Dimension Query
> --
>
> Key: LENS-773
> URL: https://issues.apache.org/jira/browse/LENS-773
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Matin
>
> Query : cube select id,name from sample_dim2 where name != 'first'
> This should be answerable from hive and hence its cost should be non-zero.
> But getting the cost as zero.
> {noformat}
> 580cf6df-35b3-4f73-9013-c304418a3904 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:type="queryCostTO">0.0LOW
> {noformat}



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


[jira] [Updated] (LENS-345) Enable javadoc check on checkstyle

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-345:
--
Fix Version/s: (was: 2.6)

> Enable javadoc check on checkstyle
> --
>
> Key: LENS-345
> URL: https://issues.apache.org/jira/browse/LENS-345
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: docs
>Reporter: Amareshwari Sriramadasu
>  Labels: newbie
>
> We should have javadoc for all public classes and methods. Let us enable 
> javadoc check in checkstyle checks.



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


[jira] [Updated] (LENS-458) Code quality improvements

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-458:
--
Fix Version/s: (was: 2.6)

> Code quality improvements
> -
>
> Key: LENS-458
> URL: https://issues.apache.org/jira/browse/LENS-458
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: build
>Reporter: Jaideep Dhok
>
> Umbrella JIRA for code quality improvements



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


[jira] [Updated] (LENS-411) Avoid parsing of the query multiple times

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-411:
--
Fix Version/s: (was: 2.6)

> Avoid parsing of the query multiple times
> -
>
> Key: LENS-411
> URL: https://issues.apache.org/jira/browse/LENS-411
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: cube, driver-hive, driver-jdbc, server
>Reporter: Amareshwari Sriramadasu
>
> JDBCDriver parses query more than once. This can be avoided to improve 
> performance.
> As part of this issue we will ensure the query is not parsed unnecessarily 
> any time in overall estimate flow as well.



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


[jira] [Updated] (LENS-103) CSVSerde doesn't differentiate between {1:"one",2:"two",3:"three"} and {1:"one",2:"two, 3:three"}.

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-103:
--
Fix Version/s: (was: 2.6)

> CSVSerde doesn't differentiate between {1:"one",2:"two",3:"three"} and 
> {1:"one",2:"two, 3:three"}. 
> ---
>
> Key: LENS-103
> URL: https://issues.apache.org/jira/browse/LENS-103
> Project: Apache Lens
>  Issue Type: Bug
>  Components: query-lib
>Affects Versions: 2.1
>Reporter: Rajat Khandelwal
>Priority: Minor
>




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


[jira] [Commented] (LENS-868) Should not bundle node & node_modules (generated files) in source-release archive file

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta commented on LENS-868:
---

[~raju.bairishetti] do we need to fix anything here ?

> Should not bundle node & node_modules (generated files) in source-release 
> archive file
> --
>
> Key: LENS-868
> URL: https://issues.apache.org/jira/browse/LENS-868
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: UI
>Reporter: Raju Bairishetti
>Assignee: Deepak Barr
> Fix For: 2.6
>
>
> We have seen the node & node_modules files from lens-ui are presented in the 
> source-release archive. We should not bundle node & node_modules in the 
> release archive.



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


[jira] [Commented] (LENS-991) Seeing multiple close calls and failures of connection after LENS-853

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta commented on LENS-991:
---

[~raju.bairishetti] can we resolve this in 2.6 ?

> Seeing multiple close calls and failures of connection after LENS-853
> -
>
> Key: LENS-991
> URL: https://issues.apache.org/jira/browse/LENS-991
> Project: Apache Lens
>  Issue Type: Bug
>  Components: client
>Affects Versions: 2.6
>Reporter: Amareshwari Sriramadasu
>Assignee: Raju Bairishetti
> Fix For: 2.6
>
>
> Seeing the following whenever we exit lens-cli :
> {noformat}
> Exception in thread "Thread-4" Exception in thread "Thread-10" 
> java.lang.IllegalStateException: Unable to close lens connection with params 
> LensConnectionParams{dbName='default', baseUrl='http://0.0.0.0:/lensapi', 
> user=anonymous, lensConfs={}, lensVars={}, sessionVars={}}
>   at org.apache.lens.client.LensConnection.close(LensConnection.java:206)
>   at 
> org.apache.lens.client.LensClient.closeConnection(LensClient.java:326)
>   at 
> org.apache.lens.cli.commands.BaseLensCommand.closeClientConnection(BaseLensCommand.java:92)
>   at 
> org.apache.lens.cli.commands.BaseLensCommand$2.run(BaseLensCommand.java:81)
> java.lang.IllegalStateException: Unable to close lens connection with params 
> LensConnectionParams{dbName='default', baseUrl='http://0.0.0.0:/lensapi', 
> user=anonymous, lensConfs={}, lensVars={}, sessionVars={}}
>   at org.apache.lens.client.LensConnection.close(LensConnection.java:206)
>   at 
> org.apache.lens.client.LensClient.closeConnection(LensClient.java:326)
>   at 
> org.apache.lens.cli.commands.BaseLensCommand.closeClientConnection(BaseLensCommand.java:92)
>   at 
> org.apache.lens.cli.commands.BaseLensCommand$2.run(BaseLensCommand.java:81)
> {noformat}



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


[jira] [Updated] (LENS-313) User friendly errors from Lens

2016-06-27 Thread Puneet Gupta (JIRA)

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

Puneet Gupta updated LENS-313:
--
Fix Version/s: (was: 2.6)

> User friendly errors from Lens
> --
>
> Key: LENS-313
> URL: https://issues.apache.org/jira/browse/LENS-313
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: api, client, cube, server
>Reporter: Amareshwari Sriramadasu
>Assignee: Sushil Mohanty
>
> The errors given out for query failures are more developer friendly than end 
> user friendly, right now.
> This request is to improve the error messages to more user friendly, we can 
> come up with a way to give both user friendly message for end user and 
> developer friendly message and details for developer to debug more. 



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