[jira] [Commented] (LENS-1190) Support Query End Notifictaion to a HTTP end point.

2016-08-05 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on LENS-1190:
-

Applied patch: 
[lens-1190.patch|https://issues.apache.org/jira/secure/attachment/12822242/lens-1190.patch]
 and ran command: mvn clean install -fae. Result: Success. Build Job: 
https://builds.apache.org/job/PreCommit-Lens-Build/779/

> Support Query End Notifictaion to a HTTP end point.
> ---
>
> Key: LENS-1190
> URL: https://issues.apache.org/jira/browse/LENS-1190
> Project: Apache Lens
>  Issue Type: New Feature
>  Components: server
>Reporter: Puneet Gupta
>Assignee: Puneet Gupta
> Attachments: lens-1190.patch
>
>
> As of now query end notification is supported via email. 
> On similar lines we can also notify a HTTP end point and the app submitting 
> queries on Lens Server can take appropriate action when such a end 
> notification is received by it.



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

[jira] [Commented] (LENS-197) Allow start and end times for columns in fact tables

2016-08-05 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on LENS-197:


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

> Allow start and end times for columns in fact tables
> 
>
> Key: LENS-197
> URL: https://issues.apache.org/jira/browse/LENS-197
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: cube
>Reporter: Amareshwari Sriramadasu
>Assignee: Sushil Mohanty
> Attachments: LENS-197-2.patch
>
>
> We can have columns being promoted/demoted from one aggregate fact to other, 
> with usage of columns in reports.
> We need this for the following use cases:
> # If field is moved to a lower cost fact: Since the fact is having lower cost 
> it will be picked up for processing, but if the life of column queried does 
> not fit in the range queried, a higher level fact should be picked up. If 
> lower level fact is picked, it would lead to wrong results.
> # If field is moved to a higher cost fact, i.e. its life ending in a lower 
> cost fact. Again, depending on the range queried, either lower or higher 
> level fact should be picked up. It will be more like optimization for this 
> case. 



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

[jira] [Commented] (LENS-1264) Group by promotion not happening with aggregate dim attributes

2016-08-05 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on LENS-1264:
-

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

> Group by promotion not happening with aggregate dim attributes 
> ---
>
> Key: LENS-1264
> URL: https://issues.apache.org/jira/browse/LENS-1264
> Project: Apache Lens
>  Issue Type: Bug
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Attachments: LENS-1264.patch
>
>
> {CODE}
> 
> 
> 
> cube query : 
> query execute cube select country,distinct_users from testcube where 
> time_range_in(time_col,'2016-07-31-00','2016-07-31-01')
> rewritten query :
> SELECT distinct (testcube.country), count(distinct (testcube.user)) FROM 
> db.fact_table testcube WHERE (((testcube.dt) in ('2016-07-31-00')))
> {CODE}
> Query  fails with the following:
> Error Message: Line 1:226 Not yet supported place for UDAF 'count'
> Column testcube.country should be part of group by as there is already 
> aggregate column used in select.



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

Re: Review Request 50814: Various Bug fixes and log messages.

2016-08-05 Thread Lavkesh Lahngir 


On Aug. 5, 2016, 5:51 a.m., Lavkesh Lahngir wrote:
> > No tests are updated or added. Can we add tests?
> 
> Lavkesh Lahngir wrote:
> There are no addiotional functionalities in this change.

I think we can add tests for session conf.


- Lavkesh


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


On Aug. 4, 2016, 6:10 p.m., Lavkesh Lahngir wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50814/
> ---
> 
> (Updated Aug. 4, 2016, 6:10 p.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1265
> https://issues.apache.org/jira/browse/LENS-1265
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> 1. Scheduler's submit job is not setting db and session config passed
> 2. Scheduler's getJobDefinition api is giving response status 500
> 3. Instance run result path is set NULL in job_instance_run_table
> 4. Delete on scheduler job is failing with NPE
> 
> 
> Diffs
> -
> 
>   lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInfo.java 
> b19248f 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceInfo.java
>  52b56ca 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceRun.java
>  e6c1571 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceState.java
>  93d3d7e 
>   lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobState.java 
> ffaae6c 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/AlarmService.java 
> 217879f 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java
>  8603edf 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerDAO.java 
> 7a2b06a 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerEventListener.java
>  7323add 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerQueryEventListener.java
>  5b12720 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerServiceImpl.java
>  14ca32d 
> 
> Diff: https://reviews.apache.org/r/50814/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Lavkesh Lahngir
> 
>

Re: Review Request 50814: Various Bug fixes and log messages.

2016-08-05 Thread Lavkesh Lahngir 


> On Aug. 5, 2016, 9:30 a.m., Rajat Khandelwal wrote:
> > lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerEventListener.java,
> >  line 88
> > 
> >
> > This would require changes in specs. 
> > 
> > ``` > maxOccurs="unbounded">
> > 
> > 
> > Path for resources like jars etc. e.g. 
> > /path/to/my/jar
> > 
> > 
> > 
> > ```
> > 
> > Followed by changes in test cases, regression tests and clients using 
> > the REST API. 
> > 
> > So either let's make those changes right now to minimize trickle down 
> > effect, or let's decide that we'll infer type from the file's extension.

Yeah. It's easy to do right now.


> On Aug. 5, 2016, 9:30 a.m., Rajat Khandelwal wrote:
> > lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java,
> >  lines 216-218
> > 
> >
> > Shouldn't be needed. `GenericExceptionMapper` will take care to ruturn 
> > the correct `APIResult`. Can you verify through test cases?

I am thinking to fix all the API things in separate JIRA. Lots of message 
formatting has to be done.


> On Aug. 5, 2016, 9:30 a.m., Rajat Khandelwal wrote:
> > lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java,
> >  lines 156-183
> > 
> >
> > Can we add documentations for all these functions so that they can be 
> > reflected in http://lens.apache.org/resource_ScheduleResource.html

Yes. We will do. Just after bug fixes.


- Lavkesh


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


On Aug. 4, 2016, 6:10 p.m., Lavkesh Lahngir wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50814/
> ---
> 
> (Updated Aug. 4, 2016, 6:10 p.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1265
> https://issues.apache.org/jira/browse/LENS-1265
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> 1. Scheduler's submit job is not setting db and session config passed
> 2. Scheduler's getJobDefinition api is giving response status 500
> 3. Instance run result path is set NULL in job_instance_run_table
> 4. Delete on scheduler job is failing with NPE
> 
> 
> Diffs
> -
> 
>   lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInfo.java 
> b19248f 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceInfo.java
>  52b56ca 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceRun.java
>  e6c1571 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceState.java
>  93d3d7e 
>   lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobState.java 
> ffaae6c 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/AlarmService.java 
> 217879f 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java
>  8603edf 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerDAO.java 
> 7a2b06a 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerEventListener.java
>  7323add 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerQueryEventListener.java
>  5b12720 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerServiceImpl.java
>  14ca32d 
> 
> Diff: https://reviews.apache.org/r/50814/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Lavkesh Lahngir
> 
>

Re: Review Request 50814: Various Bug fixes and log messages.

2016-08-05 Thread Lavkesh Lahngir 


> On Aug. 5, 2016, 5:51 a.m., Amareshwari Sriramadasu wrote:
> > lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerEventListener.java,
> >  line 71
> > 
> >
> > we should call sessionService.openSession instead of 
> > queryService.openSession

Okay. That makes sense.


On Aug. 5, 2016, 5:51 a.m., Lavkesh Lahngir wrote:
> > No tests are updated or added. Can we add tests?

There are no addiotional functionalities in this change.


- Lavkesh


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


On Aug. 4, 2016, 6:10 p.m., Lavkesh Lahngir wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50814/
> ---
> 
> (Updated Aug. 4, 2016, 6:10 p.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1265
> https://issues.apache.org/jira/browse/LENS-1265
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> 1. Scheduler's submit job is not setting db and session config passed
> 2. Scheduler's getJobDefinition api is giving response status 500
> 3. Instance run result path is set NULL in job_instance_run_table
> 4. Delete on scheduler job is failing with NPE
> 
> 
> Diffs
> -
> 
>   lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInfo.java 
> b19248f 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceInfo.java
>  52b56ca 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceRun.java
>  e6c1571 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceState.java
>  93d3d7e 
>   lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobState.java 
> ffaae6c 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/AlarmService.java 
> 217879f 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java
>  8603edf 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerDAO.java 
> 7a2b06a 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerEventListener.java
>  7323add 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerQueryEventListener.java
>  5b12720 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerServiceImpl.java
>  14ca32d 
> 
> Diff: https://reviews.apache.org/r/50814/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Lavkesh Lahngir
> 
>

Re: Review Request 50814: Various Bug fixes and log messages.

2016-08-05 Thread Rajat Khandelwal 

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




lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java
 (lines 156 - 183)


Can we add documentations for all these functions so that they can be 
reflected in http://lens.apache.org/resource_ScheduleResource.html



lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java
 (lines 214 - 216)


Shouldn't be needed. `GenericExceptionMapper` will take care to ruturn the 
correct `APIResult`. Can you verify through test cases?



lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerEventListener.java
 (line 88)


This would require changes in specs. 

```


Path for resources like jars etc. e.g. 
/path/to/my/jar



```

Followed by changes in test cases, regression tests and clients using the 
REST API. 

So either let's make those changes right now to minimize trickle down 
effect, or let's decide that we'll infer type from the file's extension.



lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerEventListener.java
 (line 118)


Let's use log statements like this: `log.info("Expiring job with handle 
{}", jobHandle);`



lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerEventListener.java
 (lines 194 - 195)


Let's close the session through SessionService interface. Seeing as it'll 
be needed at multiple places, let's keep a class-level variable initialized at 
construction. 

`SessionService sessionService = 
LensServices.get().getService(SessionService.NAME);`


- Rajat Khandelwal


On Aug. 4, 2016, 11:40 p.m., Lavkesh Lahngir wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50814/
> ---
> 
> (Updated Aug. 4, 2016, 11:40 p.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-1265
> https://issues.apache.org/jira/browse/LENS-1265
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> 1. Scheduler's submit job is not setting db and session config passed
> 2. Scheduler's getJobDefinition api is giving response status 500
> 3. Instance run result path is set NULL in job_instance_run_table
> 4. Delete on scheduler job is failing with NPE
> 
> 
> Diffs
> -
> 
>   lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInfo.java 
> b19248f 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceInfo.java
>  52b56ca 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceRun.java
>  e6c1571 
>   
> lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobInstanceState.java
>  93d3d7e 
>   lens-api/src/main/java/org/apache/lens/api/scheduler/SchedulerJobState.java 
> ffaae6c 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/AlarmService.java 
> 217879f 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java
>  8603edf 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerDAO.java 
> 7a2b06a 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerEventListener.java
>  7323add 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerQueryEventListener.java
>  5b12720 
>   
> lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerServiceImpl.java
>  14ca32d 
> 
> Diff: https://reviews.apache.org/r/50814/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Lavkesh Lahngir
> 
>

[jira] [Updated] (LENS-197) Allow start and end times for columns in fact tables

2016-08-05 Thread Sushil Mohanty (JIRA) 

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

Sushil Mohanty updated LENS-197:

Status: Patch Available  (was: Open)

> Allow start and end times for columns in fact tables
> 
>
> Key: LENS-197
> URL: https://issues.apache.org/jira/browse/LENS-197
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: cube
>Reporter: Amareshwari Sriramadasu
>Assignee: Sushil Mohanty
> Attachments: LENS-197-2.patch
>
>
> We can have columns being promoted/demoted from one aggregate fact to other, 
> with usage of columns in reports.
> We need this for the following use cases:
> # If field is moved to a lower cost fact: Since the fact is having lower cost 
> it will be picked up for processing, but if the life of column queried does 
> not fit in the range queried, a higher level fact should be picked up. If 
> lower level fact is picked, it would lead to wrong results.
> # If field is moved to a higher cost fact, i.e. its life ending in a lower 
> cost fact. Again, depending on the range queried, either lower or higher 
> level fact should be picked up. It will be more like optimization for this 
> case. 



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

[jira] [Updated] (LENS-197) Allow start and end times for columns in fact tables

2016-08-05 Thread Sushil Mohanty (JIRA) 

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

Sushil Mohanty updated LENS-197:

Attachment: LENS-197-2.patch

> Allow start and end times for columns in fact tables
> 
>
> Key: LENS-197
> URL: https://issues.apache.org/jira/browse/LENS-197
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: cube
>Reporter: Amareshwari Sriramadasu
>Assignee: Sushil Mohanty
> Attachments: LENS-197-2.patch
>
>
> We can have columns being promoted/demoted from one aggregate fact to other, 
> with usage of columns in reports.
> We need this for the following use cases:
> # If field is moved to a lower cost fact: Since the fact is having lower cost 
> it will be picked up for processing, but if the life of column queried does 
> not fit in the range queried, a higher level fact should be picked up. If 
> lower level fact is picked, it would lead to wrong results.
> # If field is moved to a higher cost fact, i.e. its life ending in a lower 
> cost fact. Again, depending on the range queried, either lower or higher 
> level fact should be picked up. It will be more like optimization for this 
> case. 



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

Re: Review Request 50714: LENS-197 : Allow start and end times for columns in fact tables

2016-08-05 Thread Sushil Mohanty 

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

(Updated Aug. 5, 2016, 8:53 a.m.)


Review request for lens.


Changes
---

Addressed review comment.


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


Repository: lens


Description
---

With this change user can specify start and end time of a fact column. Based on 
the range  of the input query, fact tables will be pruned or considered to 
answer.


Diffs (updated)
-

  lens-api/src/main/resources/cube-0.1.xsd d6c6bd2 
  lens-cube/src/main/java/org/apache/lens/cube/metadata/MetastoreConstants.java 
61675bc 
  
lens-cube/src/main/java/org/apache/lens/cube/parse/CandidateTableResolver.java 
12d6e3a 
  lens-cube/src/main/java/org/apache/lens/cube/parse/CubeQueryRewriter.java 
c1fd0a5 
  lens-cube/src/main/java/org/apache/lens/cube/parse/TimeRangeChecker.java 
PRE-CREATION 
  lens-cube/src/main/java/org/apache/lens/cube/parse/TimerangeResolver.java 
06ba148 
  lens-cube/src/test/java/org/apache/lens/cube/parse/CubeTestSetup.java 48652f2 
  lens-cube/src/test/java/org/apache/lens/cube/parse/TestBaseCubeQueries.java 
d42d494 
  lens-cube/src/test/java/org/apache/lens/cube/parse/TestCubeRewriter.java 
4dfd754 
  lens-cube/src/test/java/org/apache/lens/cube/parse/TestQueryMetrics.java 
857bc90 
  lens-examples/src/main/resources/fact1.xml effdfac 
  lens-examples/src/test/resources/yaml/fact1.yaml 4252e33 
  
lens-server/src/main/java/org/apache/lens/server/metastore/CubeMetastoreServiceImpl.java
 c1f9a02 
  lens-server/src/main/java/org/apache/lens/server/metastore/JAXBUtils.java 
1b6b819 
  
lens-server/src/test/java/org/apache/lens/server/metastore/TestMetastoreService.java
 61bc133 

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


Testing
---

mvn clean install : 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Lens Checkstyle Rules . SUCCESS [2.002s]
[INFO] Lens .. SUCCESS [3.318s]
[INFO] Lens API .. SUCCESS [21.138s]
[INFO] Lens API for server and extensions  SUCCESS [17.260s]
[INFO] Lens Cube . SUCCESS [15:00.074s]
[INFO] Lens DB storage ... SUCCESS [16.701s]
[INFO] Lens Query Library  SUCCESS [13.182s]
[INFO] Lens Hive Driver .. SUCCESS [1:22.717s]
[INFO] Lens Driver for JDBC .. SUCCESS [36.557s]
[INFO] Lens Elastic Search Driver  SUCCESS [20.234s]
[INFO] Lens Server ... SUCCESS [13:07.795s]
[INFO] Lens client ... SUCCESS [1:30.234s]
[INFO] Lens CLI .. SUCCESS [1:18.126s]
[INFO] Lens Examples . SUCCESS [8.328s]
[INFO] Lens Ship Jars to Distributed Cache ... SUCCESS [0.753s]
[INFO] Lens Distribution . SUCCESS [9.091s]
[INFO] Lens ML Lib ... SUCCESS [1:08.829s]
[INFO] Lens ML Ext Distribution .. SUCCESS [1.958s]
[INFO] Lens Regression ... SUCCESS [12.572s]
[INFO] Lens UI ... SUCCESS [27.022s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 36:38.799s
[INFO] Finished at: Tue Aug 02 18:39:14 UTC 2016
[INFO] Final Memory: 189M/2043M
[INFO] 


Thanks,

Sushil Mohanty

[jira] [Updated] (LENS-1267) Instances which are in waiting state while restart are not getting resumed

2016-08-05 Thread Lavkesh Lahngir (JIRA) 

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

Lavkesh Lahngir updated LENS-1267:
--
Description: The Scheduler can not recover from restarting when it was in 
the middle of launching a query.   (was: Scheduler can not recover from 
restarting when it was in the middle of launching a query. )

> Instances which are in waiting state while restart are not getting resumed
> --
>
> Key: LENS-1267
> URL: https://issues.apache.org/jira/browse/LENS-1267
> Project: Apache Lens
>  Issue Type: Bug
>Reporter: Archana H
>Assignee: Lavkesh Lahngir
>
> The Scheduler can not recover from restarting when it was in the middle of 
> launching a query. 



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

[jira] [Updated] (LENS-1267) Instances which are in waiting state while restart are not getting resumed

2016-08-05 Thread Lavkesh Lahngir (JIRA) 

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

Lavkesh Lahngir updated LENS-1267:
--
Description: Scheduler can not recover from restarting when it was in the 
middle of launching a query. 

> Instances which are in waiting state while restart are not getting resumed
> --
>
> Key: LENS-1267
> URL: https://issues.apache.org/jira/browse/LENS-1267
> Project: Apache Lens
>  Issue Type: Bug
>Reporter: Archana H
>Assignee: Lavkesh Lahngir
>
> Scheduler can not recover from restarting when it was in the middle of 
> launching a query. 



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

Re: Review Request 50714: LENS-197 : Allow start and end times for columns in fact tables

2016-08-05 Thread Rajat Khandelwal 

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


Fix it, then Ship it!





lens-cube/src/main/java/org/apache/lens/cube/parse/CandidateTableResolver.java 
(lines 188 - 190)


Looking at the usage, it seems like the end time value passed to this 
function would be the end time taken from a `TimeRange` object. And a TimeRange 
Object itself is a half open range. So even if the column end time equals the 
time range end time, that fact is still a candidate for this column. 

My suggestion on the previous version was misguided. Let's revert it to 
include equals check here.


- Rajat Khandelwal


On Aug. 4, 2016, 11:16 p.m., Sushil Mohanty wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50714/
> ---
> 
> (Updated Aug. 4, 2016, 11:16 p.m.)
> 
> 
> Review request for lens.
> 
> 
> Bugs: LENS-197
> https://issues.apache.org/jira/browse/LENS-197
> 
> 
> Repository: lens
> 
> 
> Description
> ---
> 
> With this change user can specify start and end time of a fact column. Based 
> on the range  of the input query, fact tables will be pruned or considered to 
> answer.
> 
> 
> Diffs
> -
> 
>   lens-api/src/main/resources/cube-0.1.xsd d6c6bd2 
>   
> lens-cube/src/main/java/org/apache/lens/cube/metadata/MetastoreConstants.java 
> 61675bc 
>   
> lens-cube/src/main/java/org/apache/lens/cube/parse/CandidateTableResolver.java
>  12d6e3a 
>   lens-cube/src/main/java/org/apache/lens/cube/parse/CubeQueryRewriter.java 
> c1fd0a5 
>   lens-cube/src/main/java/org/apache/lens/cube/parse/TimeRangeChecker.java 
> PRE-CREATION 
>   lens-cube/src/main/java/org/apache/lens/cube/parse/TimerangeResolver.java 
> 06ba148 
>   lens-cube/src/test/java/org/apache/lens/cube/parse/CubeTestSetup.java 
> 48652f2 
>   lens-cube/src/test/java/org/apache/lens/cube/parse/TestBaseCubeQueries.java 
> d42d494 
>   lens-cube/src/test/java/org/apache/lens/cube/parse/TestCubeRewriter.java 
> 4dfd754 
>   lens-cube/src/test/java/org/apache/lens/cube/parse/TestQueryMetrics.java 
> 857bc90 
>   lens-examples/src/main/resources/fact1.xml effdfac 
>   lens-examples/src/test/resources/yaml/fact1.yaml 4252e33 
>   
> lens-server/src/main/java/org/apache/lens/server/metastore/CubeMetastoreServiceImpl.java
>  c1f9a02 
>   lens-server/src/main/java/org/apache/lens/server/metastore/JAXBUtils.java 
> 1b6b819 
>   
> lens-server/src/test/java/org/apache/lens/server/metastore/TestMetastoreService.java
>  61bc133 
> 
> Diff: https://reviews.apache.org/r/50714/diff/
> 
> 
> Testing
> ---
> 
> mvn clean install : 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Lens Checkstyle Rules . SUCCESS [2.002s]
> [INFO] Lens .. SUCCESS [3.318s]
> [INFO] Lens API .. SUCCESS [21.138s]
> [INFO] Lens API for server and extensions  SUCCESS [17.260s]
> [INFO] Lens Cube . SUCCESS 
> [15:00.074s]
> [INFO] Lens DB storage ... SUCCESS [16.701s]
> [INFO] Lens Query Library  SUCCESS [13.182s]
> [INFO] Lens Hive Driver .. SUCCESS [1:22.717s]
> [INFO] Lens Driver for JDBC .. SUCCESS [36.557s]
> [INFO] Lens Elastic Search Driver  SUCCESS [20.234s]
> [INFO] Lens Server ... SUCCESS 
> [13:07.795s]
> [INFO] Lens client ... SUCCESS [1:30.234s]
> [INFO] Lens CLI .. SUCCESS [1:18.126s]
> [INFO] Lens Examples . SUCCESS [8.328s]
> [INFO] Lens Ship Jars to Distributed Cache ... SUCCESS [0.753s]
> [INFO] Lens Distribution . SUCCESS [9.091s]
> [INFO] Lens ML Lib ... SUCCESS [1:08.829s]
> [INFO] Lens ML Ext Distribution .. SUCCESS [1.958s]
> [INFO] Lens Regression ... SUCCESS [12.572s]
> [INFO] Lens UI ... SUCCESS [27.022s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 36:38.799s
> [INFO] Finished at: Tue Aug 02 18:39:14 UTC 2016
> [INFO] Final Memory: 189M/2043M
> [INFO] 
> ---

[jira] [Created] (LENS-1267) Instances which are in waiting state while restart are not getting resumed

2016-08-05 Thread Archana H (JIRA) 
Archana H created LENS-1267:
---

 Summary: Instances which are in waiting state while restart are 
not getting resumed
 Key: LENS-1267
 URL: https://issues.apache.org/jira/browse/LENS-1267
 Project: Apache Lens
  Issue Type: Bug
Reporter: Archana H
Assignee: Lavkesh Lahngir






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

[jira] [Commented] (LENS-1190) Support Query End Notifictaion to a HTTP end point.

2016-08-05 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on LENS-1190:
-

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

> Support Query End Notifictaion to a HTTP end point.
> ---
>
> Key: LENS-1190
> URL: https://issues.apache.org/jira/browse/LENS-1190
> Project: Apache Lens
>  Issue Type: New Feature
>  Components: server
>Reporter: Puneet Gupta
>Assignee: Puneet Gupta
> Attachments: lens-1190.patch
>
>
> As of now query end notification is supported via email. 
> On similar lines we can also notify a HTTP end point and the app submitting 
> queries on Lens Server can take appropriate action when such a end 
> notification is received by it.



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

[jira] [Commented] (LENS-1264) Group by promotion not happening with aggregate dim attributes

2016-08-05 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on LENS-1264:
-

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

> Group by promotion not happening with aggregate dim attributes 
> ---
>
> Key: LENS-1264
> URL: https://issues.apache.org/jira/browse/LENS-1264
> Project: Apache Lens
>  Issue Type: Bug
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Attachments: LENS-1264.patch
>
>
> {CODE}
> 
> 
> 
> cube query : 
> query execute cube select country,distinct_users from testcube where 
> time_range_in(time_col,'2016-07-31-00','2016-07-31-01')
> rewritten query :
> SELECT distinct (testcube.country), count(distinct (testcube.user)) FROM 
> db.fact_table testcube WHERE (((testcube.dt) in ('2016-07-31-00')))
> {CODE}
> Query  fails with the following:
> Error Message: Line 1:226 Not yet supported place for UDAF 'count'
> Column testcube.country should be part of group by as there is already 
> aggregate column used in select.



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