[jira] [Closed] (LENS-1416) Union query order by should work on column alias

2017-08-18 Thread Divakar Tomar (JIRA)

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

Divakar Tomar closed LENS-1416.
---

verified

> Union query order by should work on column alias
> 
>
> Key: LENS-1416
> URL: https://issues.apache.org/jira/browse/LENS-1416
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Fix For: 2.7
>
> Attachments: LENS-1416_1.patch, LENS-1416_2.patch, LENS-1416.patch
>
>
> In union queries order by clause should have column alias instead of column.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (LENS-1462) Query with same dim attribute twice referring to join chain ending with putting that field only once

2017-08-18 Thread Divakar Tomar (JIRA)
Divakar Tomar created LENS-1462:
---

 Summary: Query with same dim attribute twice referring to join 
chain ending with putting that field only once
 Key: LENS-1462
 URL: https://issues.apache.org/jira/browse/LENS-1462
 Project: Apache Lens
  Issue Type: Bug
  Components: cube
Reporter: Divakar Tomar
Assignee: Sushil Mohanty


 When same column appears twice in the query , it comes only once in the 
rewritten query (when segmentation is the selected candidate).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (LENS-1420) Bug fixes in cube segmentation final rewritten query

2017-08-18 Thread Divakar Tomar (JIRA)

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

Divakar Tomar commented on LENS-1420:
-

case 3 still persists. When same column appears twice in the query , it comes 
only once in the rewritten query (when segmentation is the selected candidate).

> Bug fixes in cube segmentation final rewritten query 
> -
>
> Key: LENS-1420
> URL: https://issues.apache.org/jira/browse/LENS-1420
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Fix For: 2.7
>
> Attachments: LENS-1420_1.patch
>
>
> Found the below issues in fact-to-fact union and cube  segmentation rewritten 
> query.
> 1. Expressions used in having clause are not resolved in the final rewritten 
> query incase of picked candidate is a segmentation.
> 2. Alias is not being replaced in order by clause for segmentation queries.
> 3. Query with two dim attributes referring to same join chain ending with 
> wrong alias replacement.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (LENS-1461) Lens services state are not persisted correctly

2017-08-18 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1461:


bq. session timeout for lens and hive are 1 day and 3 days respectievely. For a 
session which is 2 days old session manager returns valid object for 
HiveSession but its no longer a instance of "LensSessionImpl" since lens 
session already expired. causing downcasting to initialize lens related member 
variable(LensSessionHandle, db, username, password etc) to null causing 
deserializer to fail for them.

Not sure what you mean by this here. By my understanding, when {{LensServices}} 
is {{init}}ed, {{CLIService}} and {{CLIService.SessionManager}} are also 
{{init}}ed. In the {{init}} phase of {{SessionManager}}, session impl class is 
decided. That is configured to be {{LensSessionImpl.class}} in all the restarts 
of the Lens Server. 

What I am worried about though, is why the function 
{{org.apache.lens.server.api.session.SessionService#restoreSession}} has no 
usages in the project. 

bq. 2. downcasting is done in getsession() method in *LensSessionImpl* and 
referenced at lot of places. That might be causing other bugs apart from 
mentioned above. 

I assume you are talking about 
{{org.apache.lens.server.BaseLensService#getSession}}. {{getSession}} has 
another problem, it is throwing Jersey client exception. That exception is fine 
if it ends up to user facing api classes. But it's wrong if it is being thrown 
inside init/start phases. The two kind of usages' need to be served by two 
different functions. 


> Lens services state are not persisted correctly
> ---
>
> Key: LENS-1461
> URL: https://issues.apache.org/jira/browse/LENS-1461
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Ankit Kailaswar
>Assignee: Ankit Kailaswar
>
> Lens services state are not persisted correctly causing lens  to fail at 
> startup.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (LENS-1408) Fix test cases after LENS-1399

2017-08-18 Thread Sushil Mohanty (JIRA)

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

Sushil Mohanty closed LENS-1408.


> Fix test cases after LENS-1399
> --
>
> Key: LENS-1408
> URL: https://issues.apache.org/jira/browse/LENS-1408
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Fix For: 2.7
>
>
> As LENS-1397 is done, we need to fix the dependent test cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (LENS-1432) Map Join tuning broken for this query leading to Map timeouts

2017-08-18 Thread Divakar Tomar (JIRA)

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

Divakar Tomar closed LENS-1432.
---

verified


> Map Join tuning broken for this query leading to Map timeouts
> -
>
> Key: LENS-1432
> URL: https://issues.apache.org/jira/browse/LENS-1432
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Fix For: 2.7
>
> Attachments: LENS-1432_2.patch, LENS-1432_3.patch
>
>
> CubeQueryContext.getDimsToQuery() is empty, causing the problem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (LENS-1334) Full outer join queries join conditions not rewritten correctly when more than two table involved

2017-08-18 Thread Divakar Tomar (JIRA)

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

Divakar Tomar closed LENS-1334.
---

This feature is not supported after fact-to-fact join as queries are written 
using union construct.

> Full outer join queries join conditions not rewritten correctly when more 
> than two table involved
> -
>
> Key: LENS-1334
> URL: https://issues.apache.org/jira/browse/LENS-1334
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Fix For: 2.7
>
> Attachments: LENS-1334-1.patch
>
>
> Currently full outer join queries are written like below
> {CODE}
> ...from A full outer join B full outer join C on A.col = B.col and A.col = 
> C.col
> {CODE}
> instead it should be rewritten as 
> {CODE}
> ...from A full outer join B  on a.col = b.col full outer join C on b.col = 
> c.col
> {CODE}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (LENS-1435) Cube xml files are missing in lens-example

2017-08-18 Thread Divakar Tomar (JIRA)

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

Divakar Tomar closed LENS-1435.
---

verified
all files are present.

> Cube xml files are missing in lens-example
> --
>
> Key: LENS-1435
> URL: https://issues.apache.org/jira/browse/LENS-1435
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Fix For: 2.7
>
> Attachments: LENS-1435.patch
>
>
> cube11, cube22 and cube33  schema are missing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (LENS-1355) Lens unable to parse "date" in queries

2017-08-18 Thread Divakar Tomar (JIRA)

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

Divakar Tomar closed LENS-1355.
---

verified

> Lens unable to parse "date" in queries
> --
>
> Key: LENS-1355
> URL: https://issues.apache.org/jira/browse/LENS-1355
> Project: Apache Lens
>  Issue Type: Bug
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1355.01.patch, LENS-1355.02.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (LENS-1287) Create command in cli to create schema taking parent directory where schema is stored

2017-08-18 Thread Divakar Tomar (JIRA)

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

Divakar Tomar closed LENS-1287.
---

verified

> Create command in cli to create schema taking parent directory where schema 
> is stored
> -
>
> Key: LENS-1287
> URL: https://issues.apache.org/jira/browse/LENS-1287
> Project: Apache Lens
>  Issue Type: New Feature
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1287.07.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Comment Edited] (LENS-1461) Lens services state are not persisted correctly

2017-08-18 Thread Ankit Kailaswar (JIRA)

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

Ankit Kailaswar edited comment on LENS-1461 at 8/18/17 9:49 AM:


There were few issues found while persisting service states and using it to 
start lens server.

1. Session service is not getting persisted properly on few occasions. session 
service try to serialize few sessions which are invalid using its session 
handles throwing an exception uncaught at service level. Other services are 
getting persisted successfully.
{panel:title=lens server log 
|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
14 Aug 2017 20:13:49 6daca8db-deb9-4ab0-ba2d-3f5e474ad545 
Lens-server-snapshotter-Thread-1 WARN  org.apache.lens.server.BaseLensService - 
 {color:red} *Session cbc183be-8f05-4356-bb56-6ba43217518b not found* {color}
org.apache.hive.service.cli.HiveSQLException: Invalid SessionHandle: 
SessionHandle cbc183be-8f05-4356-bb56-6ba43217518b
at 
org.apache.hive.service.cli.session.SessionManager.getSession(SessionManager.java:389)
 ~hive-service-2.1.3-inm.jar:2.1.3-inm
at 
org.apache.lens.server.BaseLensService.getSession(BaseLensService.java:366) 
~classes/:na
at 
org.apache.lens.server.session.HiveSessionService.writeExternal(HiveSessionService.java:425)
 classes/:na
at 
org.apache.lens.server.LensServices.persistState(LensServices.java:369) 
classes/:na
at 
org.apache.lens.server.LensServices.persistLensServiceState(LensServices.java:354)
 classes/:na
at org.apache.lens.server.LensServices.access$100(LensServices.java:63) 
classes/:na
at org.apache.lens.server.LensServices$1.run(LensServices.java:305) 
classes/:na
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
na:1.8.0_72
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
na:1.8.0_72
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 na:1.8.0_72
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 na:1.8.0_72
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
na:1.8.0_72
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
na:1.8.0_72
at java.lang.Thread.run(Thread.java:745) na:1.8.0_72
14 Aug 2017 20:13:49 ba8c2672-53a0-44ad-9d50-fc53e2286143 
grizzly-http-server-12 INFO  hive.metastore - Closed a connection to metastore, 
current connections: 282
14 Aug 2017 20:13:49 ba8c2672-53a0-44ad-9d50-fc53e2286143 
grizzly-http-server-12 INFO  org.apache.lens.server.BaseLensService - Closed 
session cbc183be-8f05-4356-bb56-6ba43217518b33a980a2-206c-4dbc-b3d9-ffa3a6b6de87
 for yoda-admin user
14 Aug 2017 20:13:49 6daca8db-deb9-4ab0-ba2d-3f5e474ad545 
Lens-server-snapshotter-Thread-1 {color:red} *ERROR 
org.apache.lens.server.LensServices - Error while persisting state for service 
session* {color}
javax.ws.rs.ClientErrorException: Session cbc183be-8f05-4356-bb56-6ba43217518b 
is invalid cbc183be-8f05-4356-bb56-6ba43217518b33a980a2-206c-4dbc-b3d9-ffa3a6b6de87
at 
org.apache.lens.server.BaseLensService.getSession(BaseLensService.java:370) 
~classes/:na
at 
org.apache.lens.server.session.HiveSessionService.writeExternal(HiveSessionService.java:425)
 ~classes/:na
at 
org.apache.lens.server.LensServices.persistState(LensServices.java:369) 
classes/:na
at 
org.apache.lens.server.LensServices.persistLensServiceState(LensServices.java:354)
 classes/:na
at org.apache.lens.server.LensServices.access$100(LensServices.java:63) 
classes/:na
at org.apache.lens.server.LensServices$1.run(LensServices.java:305) 
classes/:na
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
na:1.8.0_72
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
na:1.8.0_72
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 na:1.8.0_72
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 na:1.8.0_72
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
na:1.8.0_72
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
na:1.8.0_72
at java.lang.Thread.run(Thread.java:745) na:1.8.0_72
Caused by: org.apache.hive.service.cli.HiveSQLException: Invalid SessionHandle: 
SessionHandle cbc183be-8f05-4356-bb56-6ba43217518b
at 
org.apache.hive.service.cli.session.SessionManager.getSession(SessionManager.java:389)
 ~hive-service-2.1.3-inm.jar:2.1.3-inm
at 

[jira] [Commented] (LENS-1461) Lens services state are not persisted correctly

2017-08-18 Thread Ankit Kailaswar (JIRA)

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

Ankit Kailaswar commented on LENS-1461:
---


There were few issues found while persisting service states and using it to 
start lens server.

1. Session service is not getting persisted properly on few occasions. session 
service try to serialize few sessions which are invalid using its session 
handles throwing an exception uncaught at service level. Other services are 
getting persisted successfully.
{panel:title=lens server log 
|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
14 Aug 2017 20:13:49 6daca8db-deb9-4ab0-ba2d-3f5e474ad545 
Lens-server-snapshotter-Thread-1 WARN  org.apache.lens.server.BaseLensService - 
 {color:red} *Session cbc183be-8f05-4356-bb56-6ba43217518b not found* {color}
org.apache.hive.service.cli.HiveSQLException: Invalid SessionHandle: 
SessionHandle cbc183be-8f05-4356-bb56-6ba43217518b
at 
org.apache.hive.service.cli.session.SessionManager.getSession(SessionManager.java:389)
 ~hive-service-2.1.3-inm.jar:2.1.3-inm
at 
org.apache.lens.server.BaseLensService.getSession(BaseLensService.java:366) 
~classes/:na
at 
org.apache.lens.server.session.HiveSessionService.writeExternal(HiveSessionService.java:425)
 classes/:na
at 
org.apache.lens.server.LensServices.persistState(LensServices.java:369) 
classes/:na
at 
org.apache.lens.server.LensServices.persistLensServiceState(LensServices.java:354)
 classes/:na
at org.apache.lens.server.LensServices.access$100(LensServices.java:63) 
classes/:na
at org.apache.lens.server.LensServices$1.run(LensServices.java:305) 
classes/:na
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
na:1.8.0_72
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
na:1.8.0_72
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 na:1.8.0_72
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 na:1.8.0_72
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
na:1.8.0_72
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
na:1.8.0_72
at java.lang.Thread.run(Thread.java:745) na:1.8.0_72
14 Aug 2017 20:13:49 ba8c2672-53a0-44ad-9d50-fc53e2286143 
grizzly-http-server-12 INFO  hive.metastore - Closed a connection to metastore, 
current connections: 282
14 Aug 2017 20:13:49 ba8c2672-53a0-44ad-9d50-fc53e2286143 
grizzly-http-server-12 INFO  org.apache.lens.server.BaseLensService - Closed 
session cbc183be-8f05-4356-bb56-6ba43217518b33a980a2-206c-4dbc-b3d9-ffa3a6b6de87
 for yoda-admin user
14 Aug 2017 20:13:49 6daca8db-deb9-4ab0-ba2d-3f5e474ad545 
Lens-server-snapshotter-Thread-1 ERROR org.apache.lens.server.LensServices - 
Error while persisting state for service session
javax.ws.rs.ClientErrorException: Session cbc183be-8f05-4356-bb56-6ba43217518b 
is invalid cbc183be-8f05-4356-bb56-6ba43217518b33a980a2-206c-4dbc-b3d9-ffa3a6b6de87
at 
org.apache.lens.server.BaseLensService.getSession(BaseLensService.java:370) 
~classes/:na
at 
org.apache.lens.server.session.HiveSessionService.writeExternal(HiveSessionService.java:425)
 ~classes/:na
at 
org.apache.lens.server.LensServices.persistState(LensServices.java:369) 
classes/:na
at 
org.apache.lens.server.LensServices.persistLensServiceState(LensServices.java:354)
 classes/:na
at org.apache.lens.server.LensServices.access$100(LensServices.java:63) 
classes/:na
at org.apache.lens.server.LensServices$1.run(LensServices.java:305) 
classes/:na
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
na:1.8.0_72
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
na:1.8.0_72
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 na:1.8.0_72
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 na:1.8.0_72
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
na:1.8.0_72
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
na:1.8.0_72
at java.lang.Thread.run(Thread.java:745) na:1.8.0_72
Caused by: org.apache.hive.service.cli.HiveSQLException: Invalid SessionHandle: 
SessionHandle cbc183be-8f05-4356-bb56-6ba43217518b
at 
org.apache.hive.service.cli.session.SessionManager.getSession(SessionManager.java:389)
 ~hive-service-2.1.3-inm.jar:2.1.3-inm
at 
org.apache.lens.server.BaseLensService.getSession(BaseLensService.java:366) 
~classes/:na

[jira] [Created] (LENS-1461) Lens services state are not persisted correctly

2017-08-18 Thread Ankit Kailaswar (JIRA)
Ankit Kailaswar created LENS-1461:
-

 Summary: Lens services state are not persisted correctly
 Key: LENS-1461
 URL: https://issues.apache.org/jira/browse/LENS-1461
 Project: Apache Lens
  Issue Type: Bug
  Components: server
Reporter: Ankit Kailaswar
Assignee: Ankit Kailaswar


Lens services state are not persisted correctly causing lens  to fail at 
startup.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)