[jira] [Commented] (LENS-1300) Queries submissions are not getting rejected on sessions marked for close

[Hadoop QA (JIRA)]

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

Hadoop QA commented on LENS-1300:
-

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

> Queries submissions are not getting rejected on sessions marked for close
> -
>
> Key: LENS-1300
> URL: https://issues.apache.org/jira/browse/LENS-1300
> Project: Apache Lens
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1300.02.patch
>
>




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

[jira] [Commented] (LENS-1283) Map failure APIResult to Exception in Lens client

[Hadoop QA (JIRA)]

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

Hadoop QA commented on LENS-1283:
-

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

> Map failure APIResult to Exception in Lens client
> -
>
> Key: LENS-1283
> URL: https://issues.apache.org/jira/browse/LENS-1283
> Project: Apache Lens
>  Issue Type: Improvement
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1283.02.patch, LENS-1283.05.patch, 
> LENS-1283.06.patch, LENS-1283.07.patch, LENS-1283.08.patch, 
> LENS-1283.09.patch, LENS-1283.10.patch
>
>




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

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

[Archana H (JIRA)]

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

Archana H commented on LENS-778:


Not seeing this issue now.

> 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: Archana H
> 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] [Closed] (LENS-886) Queued JDBC queries are failing upon lens server restart

[Archana H (JIRA)]

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

Archana H closed LENS-886.
--

> Queued JDBC queries are failing upon lens server restart
> 
>
> Key: LENS-886
> URL: https://issues.apache.org/jira/browse/LENS-886
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Archana H
> Fix For: 2.6
>
>
> Queued queries are failing upon restart with connection timeout.
> {noformat}
> Caused by: com.mchange.v2.resourcepool.TimeoutException: A client timed out 
> while waiting to acquire a resource from 
> com.mchange.v2.resourcepool.BasicResourcePool@629a3da7 -- timeout at 
> awaitAvailable()
> at 
> com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1461)
>  ~[c3p0-0.9.5.jar:0.9.5]
> at 
> com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:639)
>  ~[c3p0-0.9.5.jar:0.9.5]
> at 
> com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:549)
>  ~[c3p0-0.9.5.jar:0.9.5]
> at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutAndMarkConnectionInUse(C3P0PooledConnectionPool.java:756)
>  ~[c3p0-0.9.5.jar:0.9.5]
> at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:683)
>  ~[c3p0-0.9.5.jar:0.9.5]
> ... 9 common frames omitted
> {noformat}



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

[jira] [Resolved] (LENS-886) Queued JDBC queries are failing upon lens server restart

[Archana H (JIRA)]

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

Archana H resolved LENS-886.

Resolution: Not A Problem

> Queued JDBC queries are failing upon lens server restart
> 
>
> Key: LENS-886
> URL: https://issues.apache.org/jira/browse/LENS-886
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Archana H
> Fix For: 2.6
>
>
> Queued queries are failing upon restart with connection timeout.
> {noformat}
> Caused by: com.mchange.v2.resourcepool.TimeoutException: A client timed out 
> while waiting to acquire a resource from 
> com.mchange.v2.resourcepool.BasicResourcePool@629a3da7 -- timeout at 
> awaitAvailable()
> at 
> com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1461)
>  ~[c3p0-0.9.5.jar:0.9.5]
> at 
> com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:639)
>  ~[c3p0-0.9.5.jar:0.9.5]
> at 
> com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:549)
>  ~[c3p0-0.9.5.jar:0.9.5]
> at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutAndMarkConnectionInUse(C3P0PooledConnectionPool.java:756)
>  ~[c3p0-0.9.5.jar:0.9.5]
> at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:683)
>  ~[c3p0-0.9.5.jar:0.9.5]
> ... 9 common frames omitted
> {noformat}



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

[jira] [Closed] (LENS-1040) cubesegmentation commands are conflicting with cube commands

[Archana H (JIRA)]

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

Archana H closed LENS-1040.
---

> cubesegmentation commands are conflicting with cube commands
> 
>
> Key: LENS-1040
> URL: https://issues.apache.org/jira/browse/LENS-1040
> Project: Apache Lens
>  Issue Type: Bug
>  Components: client
>Affects Versions: 2.6
>Reporter: Amareshwari Sriramadasu
>Assignee: Sushil Mohanty
> Fix For: 2.6
>
> Attachments: LENS-1040-1.patch
>
>
> Since cubesegmentation commands have prefix as cube, the auto completion and 
> help for cube commands is not working.
> We need to change the command word from cubesegmentation to something else.
> Shall we change to just segmentation ?



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

[jira] [Closed] (LENS-1207) Lens UI enhancements

[Archana H (JIRA)]

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

Archana H closed LENS-1207.
---

> Lens UI enhancements
> 
>
> Key: LENS-1207
> URL: https://issues.apache.org/jira/browse/LENS-1207
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: UI
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.6
>
> Attachments: LENS-1207.01.patch, LENS-1207.03.patch, 
> LENS-1207.07.patch, LENS-1207.2016-06-29_17:22:51.patch
>
>
> Following changes are done :
> * Make password optional in login
> * Add db as login parameter, just like java/python clients
> * By default only show base cubes. Can be configured to show all.
> * Modified start/stop scripts so that start is npm start and stop is npm stop
> * Lens server url and ui port is configurable by .npmrc now.
> * URLs changed. Now db is not part of the url, it's a session property, and 
> is also cached in the client state
> * Reduced width of sidebar and increased width of main content
> * Corrected content in cube schema view. Now it shows joinchains and 
> expressions too. Also, changed columns being displayed in measure and 
> dimtable list.
> * Some bugfixes in error json parsing.



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

[jira] [Closed] (LENS-918) Query Priority is not getting logged in query logs

[Archana H (JIRA)]

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

Archana H closed LENS-918.
--

> Query Priority is not getting logged in query logs
> --
>
> Key: LENS-918
> URL: https://issues.apache.org/jira/browse/LENS-918
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Puneet Gupta
>Assignee: Ajay Yadava
>Priority: Minor
> Fix For: 2.6
>
> Attachments: LENS-918-v1.patch, LENS-918.patch
>
>
> Logs pertaining to query priority missing from Query Logs.  Its logged in 
> server logs only (but query handle is not logged)



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

Re: Review Request 51548: LENS-1304 Log Driver query in lens finished_queries

[Raghavendra Singh]

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

(Updated Aug. 31, 2016, 11:50 a.m.)


Review request for lens.


Changes
---

changed name of selectedDriverQuery to driverQuery


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


Repository: lens


Description
---

Make driver query available in the finished_queries stats for deeper analytics


Diffs (updated)
-

  
lens-server-api/src/main/java/org/apache/lens/server/api/query/FinishedLensQuery.java
 1d56757 
  lens-server/src/main/java/org/apache/lens/server/query/LensServerDAO.java 
47159b5 
  lens-server/src/test/java/org/apache/lens/server/query/TestLensDAO.java 
74d9a1f 

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


Testing
---

Test added in TestLensDAO.java

[INFO] Reactor Summary:
[INFO] 
[INFO] Lens Checkstyle Rules .. SUCCESS [ 12.621 s]
[INFO] Lens ... SUCCESS [ 14.930 s]
[INFO] Lens API ... SUCCESS [ 44.131 s]
[INFO] Lens API for server and extensions . SUCCESS [ 46.240 s]
[INFO] Lens Cube .. SUCCESS [21:11 min]
[INFO] Lens DB storage  SUCCESS [ 32.606 s]
[INFO] Lens Query Library . SUCCESS [ 28.387 s]
[INFO] Lens Hive Driver ... SUCCESS [02:47 min]
[INFO] Lens Driver for JDBC ... SUCCESS [ 56.947 s]
[INFO] Lens Elastic Search Driver . SUCCESS [ 33.325 s]
[INFO] Lens Server  SUCCESS [22:44 min]
[INFO] Lens client  SUCCESS [02:10 min]
[INFO] Lens CLI ... SUCCESS [02:07 min]
[INFO] Lens Examples .. SUCCESS [ 16.364 s]
[INFO] Lens Ship Jars to Distributed Cache  SUCCESS [  2.979 s]
[INFO] Lens Distribution .. SUCCESS [ 38.824 s]
[INFO] Lens ML Lib  SUCCESS [02:40 min]
[INFO] Lens ML Ext Distribution ... SUCCESS [ 22.394 s]
[INFO] Lens Regression  SUCCESS [ 26.432 s]
[INFO] Lens UI  SUCCESS [ 21.591 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 01:00 h
[INFO] Finished at: 2016-08-30T19:25:13+05:30
[INFO] Final Memory: 199M/1058M
[INFO] 


Thanks,

Raghavendra Singh

[jira] [Closed] (LENS-730) Issues with column aliases in multifact query

[Archana H (JIRA)]

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

Archana H closed LENS-730.
--

> Issues with column aliases in multifact query
> -
>
> Key: LENS-730
> URL: https://issues.apache.org/jira/browse/LENS-730
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
> Fix For: 2.6
>
> Attachments: LENS-730.2.patch
>
>
> We saw couple of issues with aliases in multi fact queries.
> * cube select func1(col1), func2(col1), m1,m2 from cube where 
> time_range_in(dt, now.day - 2days, now) writes the query as follows :
> select COALESCE(mq1.col1, mq2.col1) col1, COALESCE(mq1.col1, mq2.col1) col1, 
> mq1.m1, mq2.m2 from
> (select func1(col1) col1, func2(col1) col1, m1 from fact1 where ...) mq1
> full outer join
> (select func1(col1) col1, func2(col1) col1, m2 from fact2 where ...) mq2
> on 
> mq1.col1 <=> mq2.col1 and mq1.col1 <=>mq2.col1
> * Another was the case of the alias of the column is same as the field 
> selected.



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

[jira] [Closed] (LENS-39) Add tags to cube column

[Archana H (JIRA)]

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

Archana H closed LENS-39.
-

> Add tags to cube column
> ---
>
> Key: LENS-39
> URL: https://issues.apache.org/jira/browse/LENS-39
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Amareshwari Sriramadasu
>Assignee: Sushil Mohanty
>  Labels: newbie
> Fix For: 2.6
>
> Attachments: LENS-39-1.patch
>
>
> This is to add a key, value holder for keeping tags associated with a cube 
> column.
> We can add Map as one more class level field in CubeColumn and 
> expose it through jaxb as well.



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

[jira] [Closed] (LENS-529) Add Developer documentation for adding new errors to code

[Archana H (JIRA)]

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

Archana H closed LENS-529.
--

> Add Developer documentation for adding new errors to code
> -
>
> Key: LENS-529
> URL: https://issues.apache.org/jira/browse/LENS-529
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Himanshu Gahlaut
>Assignee: Ajay Yadava
> Fix For: 2.6
>
> Attachments: LENS-529-v0.patch
>
>




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

[jira] [Closed] (LENS-1199) NPE while closing session

[Archana H (JIRA)]

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

Archana H closed LENS-1199.
---

> NPE while closing session
> -
>
> Key: LENS-1199
> URL: https://issues.apache.org/jira/browse/LENS-1199
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Affects Versions: 2.6
>Reporter: Amareshwari Sriramadasu
>Assignee: Raju Bairishetti
> Fix For: 2.6
>
> Attachments: LENS-1199.patch
>
>
> Close session fails with 500.
> Seeing the following in server logs :
> {noformat}
> 23 Jun 2016 05:55:01 [9217270f-8cf1-43dd-add4-64d604bebb65] 
> [e319efea-fd05-401a-91c9-c94ee8409dcf grizzly-http-server-1] INFO  
> org.apache.lens.server.BaseLensService - Closed session  encoding="UTF-8" 
> standalone="yes"?>e319efea-fd05-401a-91c9-c94ee8409dcf76942b08-b549-430f-834b-ae39514c6a91
>  for anonymous user
> 23 Jun 2016 05:55:01 [9217270f-8cf1-43dd-add4-64d604bebb65] 
> [e319efea-fd05-401a-91c9-c94ee8409dcf grizzly-http-server-1] ERROR 
> org.apache.lens.server.LensRequestListener - Encountered HTTP exception
> org.glassfish.jersey.server.internal.process.MappableException: 
> java.lang.NullPointerException
> at 
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.mapTargetToRuntimeEx(AbstractJavaResourceMethodDispatcher.java:179)
>  ~[jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.access$200(AbstractJavaResourceMethodDispatcher.java:72)
>  ~[jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:149)
>  ~[jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
>  ~[jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)
>  ~[jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
>  ~[jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
>  ~[jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
>  ~[jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
>  ~[jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) 
> ~[jersey-server-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) 
> [jersey-common-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) 
> [jersey-common-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315) 
> [jersey-common-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297) 
> [jersey-common-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267) 
> [jersey-common-2.22.1.jar:na]
> at 
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
>  [jersey-common-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) 
> [jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
>  [jersey-server-2.22.1.jar:na]
> at 
> org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service(GrizzlyHttpContainer.java:384)
>  [jersey-container-grizzly2-http-2.22.1.jar:na]
> at 
> org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:224) 
> [grizzly-http-server-2.3.23.jar:2.3.23]
> at 
> org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:591)
>  [grizzly-framework-2.3.23.jar:2.3.23]
> at 
> org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:571)
>  [grizzly-framework-2.3.23.jar:2.3.23]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]
> Caused by: java.lang.NullPointerException: null
> at 
> org.apache.lens.server.BaseLensService.decrementSessionCountForUser(BaseLensService.java:329)
>  ~[classes/:na]
> at 
> org.apache.lens.server.BaseLensService.closeSession(BaseLensService.java:307) 
> ~[classes/:na]
> at 
> 

[jira] [Closed] (LENS-893) Query Service should not mark queries failed in case driver is not responding in a timely manner

[Archana H (JIRA)]

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

Archana H closed LENS-893.
--

> Query Service should not mark queries failed in case driver is not responding 
> in a timely manner
> 
>
> Key: LENS-893
> URL: https://issues.apache.org/jira/browse/LENS-893
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Amareshwari Sriramadasu
> Fix For: 2.6
>
> Attachments: LENS-893.4.patch, LENS-893.5.patch
>
>
> Exponential backoff can be done in update status. 



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

[jira] [Closed] (LENS-1208) Missing join condition for multi fact query for expression attributes

[Archana H (JIRA)]

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

Archana H closed LENS-1208.
---

> Missing join condition for multi fact query for expression attributes
> -
>
> Key: LENS-1208
> URL: https://issues.apache.org/jira/browse/LENS-1208
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Amareshwari Sriramadasu
>Assignee: Amareshwari Sriramadasu
>Priority: Critical
> Fix For: 2.6
>
> Attachments: LENS-1208.2.patch, LENS-1208.patch
>
>
> We noticed that the join condition is missing for full outer join queries for 
> multi fact queries when one of the field chosen is an expression attribute. 



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

Re: Review Request 51552: LENS-1303: list of queries on ui should use time filters

[Rajat Khandelwal]

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

(Updated Aug. 31, 2016, 12:44 p.m.)


Review request for lens.


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


Repository: lens


Description
---


Diffs (updated)
-

  lens-ui/app/actions/AdhocQueryActions.js 
38f2794a443c7814a20a9662efb06c9b431e764b 
  lens-ui/app/adapters/AdhocQueryAdapter.js 
a54274fbf1e83d06ca7175eb9c3905662731067a 
  lens-ui/app/components/CubeSchemaComponent.js 
9c23b9fd3cd8a6ae87802ce9a07f2267ef76f8f7 
  lens-ui/app/components/QueryOperationsComponent.js 
e4cc1e7304092ea6fcce28d6ed3d895f5061d982 
  lens-ui/app/components/QueryPreviewComponent.js 
a29f2d8ad71c59cbc7ba22ac7e95512399acc16f 
  lens-ui/app/components/QueryResultsComponent.js 
01f0e30415bd2f2a7d2acfdddf51c388fc683ed8 
  lens-ui/app/constants/AdhocQueryConstants.js 
7eceb6fec6ca64497bbc78973ecb818e2bd89190 
  lens-ui/app/stores/AdhocQueryStore.js 
d8891c26e5003b09c512db9352841a654fdde27a 

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


Testing
---


Thanks,

Rajat Khandelwal

[jira] [Commented] (LENS-1303) list of queries on ui should use time filters

[Rajat Khandelwal (JIRA)]

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

Rajat Khandelwal commented on LENS-1303:


The idea is to show last 2 days' data by default in successful/failed/all 
views. for running/queued views it's fine to show all running or all queued 
queries. There are two boxes in the view with which start and end ranges can be 
provided. 

There is a fundamental change in the fetching of queries. Now, query handles 
are fetched, and query details are cached. So when you see all successful 
queries of last 10 days, it will fetch handles first, and then details of all 
those queries. But when you interact and ask for successful queries of last 5 
days, only handles will be fetched, details will be picked from cache. 



> list of queries on ui should use time filters
> -
>
> Key: LENS-1303
> URL: https://issues.apache.org/jira/browse/LENS-1303
> 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-1303) list of queries on ui should use time filters

[Rajat Khandelwal (JIRA)]

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

Rajat Khandelwal commented on LENS-1303:


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

> list of queries on ui should use time filters
> -
>
> Key: LENS-1303
> URL: https://issues.apache.org/jira/browse/LENS-1303
> 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 51552: LENS-1303: list of queries on ui should use time filters

[Rajat Khandelwal]

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

Review request for lens.


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


Repository: lens


Description
---


Diffs
-

  lens-api/src/main/java/org/apache/lens/api/query/QueryHandle.java 
81ca0e8902ff30d2b9857d44189cf4d9ea8161c6 
  lens-server/src/test/java/org/apache/lens/server/query/TestQueryService.java 
45a753d86be6e2479329b7de365ed0a88d9928ba 
  lens-ui/app/actions/AdhocQueryActions.js 
38f2794a443c7814a20a9662efb06c9b431e764b 
  lens-ui/app/adapters/AdhocQueryAdapter.js 
a54274fbf1e83d06ca7175eb9c3905662731067a 
  lens-ui/app/components/QueryOperationsComponent.js 
e4cc1e7304092ea6fcce28d6ed3d895f5061d982 
  lens-ui/app/components/QueryPreviewComponent.js 
a29f2d8ad71c59cbc7ba22ac7e95512399acc16f 
  lens-ui/app/components/QueryResultsComponent.js 
01f0e30415bd2f2a7d2acfdddf51c388fc683ed8 
  lens-ui/app/constants/AdhocQueryConstants.js 
7eceb6fec6ca64497bbc78973ecb818e2bd89190 
  lens-ui/app/stores/AdhocQueryStore.js 
d8891c26e5003b09c512db9352841a654fdde27a 

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


Testing
---


Thanks,

Rajat Khandelwal

[jira] [Commented] (LENS-1300) Queries submissions are not getting rejected on sessions marked for close

[Hadoop QA (JIRA)]

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

Hadoop QA commented on LENS-1300:
-

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

> Queries submissions are not getting rejected on sessions marked for close
> -
>
> Key: LENS-1300
> URL: https://issues.apache.org/jira/browse/LENS-1300
> Project: Apache Lens
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1300.02.patch
>
>




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