[jira] [Closed] (LENS-1398) Python client not raising exception in some cases

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1398.
--

> Python client not raising exception in some cases
> -
>
> Key: LENS-1398
> URL: https://issues.apache.org/jira/browse/LENS-1398
> Project: Apache Lens
>  Issue Type: Bug
>  Components: python-client
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1398.01.patch, LENS-1398.04.patch, 
> LENS-1398.04.patch, LENS-1398.05.patch
>
>
> If lens api gives error, then the lensAPIResult object in response is 
> ignored. 



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


[jira] [Closed] (LENS-1323) TestRemoteHiveDriver#testMultiThreadClient failing in pre-commit builds

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1323.
--

> TestRemoteHiveDriver#testMultiThreadClient failing in pre-commit builds
> ---
>
> Key: LENS-1323
> URL: https://issues.apache.org/jira/browse/LENS-1323
> Project: Apache Lens
>  Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1323.01.patch, LENS-1323.02.patch
>
>
> The issue originated after LENS-1243. Apparently querying the status twice 
> from Hive server is resulting in an error. 



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


[jira] [Created] (LENS-1460) Partition Registration shouldn't say FAILED in case 0 partitions get registered

2017-08-17 Thread Rajat Khandelwal (JIRA)
Rajat Khandelwal created LENS-1460:
--

 Summary: Partition Registration shouldn't say FAILED in case 0 
partitions get registered
 Key: LENS-1460
 URL: https://issues.apache.org/jira/browse/LENS-1460
 Project: Apache Lens
  Issue Type: Improvement
  Components: cube
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal


in add partitions API, the user supplies a list of partitions to be added. 
Among them, if some partitions are already registered, they are not 
re-registered. In case all partitions are pre-existing, it returns FAILED 
APIResult. It should not return FAILED. It should, however, still return FAILED 
if there is some genuine error. 



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


[jira] [Closed] (LENS-1396) Checkstyle failing with java8 syntax

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1396.
--

> Checkstyle failing with java8 syntax
> 
>
> Key: LENS-1396
> URL: https://issues.apache.org/jira/browse/LENS-1396
> Project: Apache Lens
>  Issue Type: Bug
>  Components: 2.7
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1396.01.patch
>
>
> checkstyle is failing with lambda functions



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


[jira] [Closed] (LENS-1400) Convert CubeTestSetup to setup using xml files instead of code

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1400.
--

> Convert CubeTestSetup to setup using xml files instead of code
> --
>
> Key: LENS-1400
> URL: https://issues.apache.org/jira/browse/LENS-1400
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1400.05.patch
>
>
> To add more tests in cube module, one would need to create more schema 
> objects. Creating them in java is too difficult and hard to read for other 
> people. So I'll be converting them to xml based schema creation. 



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


[jira] [Closed] (LENS-1415) Make ResultRow implement Serializable

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1415.
--

> Make ResultRow implement Serializable
> -
>
> Key: LENS-1415
> URL: https://issues.apache.org/jira/browse/LENS-1415
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: api
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1415.01.patch, LENS-1415.2017-04-28_17:45:20.patch
>
>
> This will help in people analyzing InMemoryResult. Analyzing the result can 
> be done via spark and spark expects its dataset objects to be Serializable. 



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


[jira] [Closed] (LENS-1438) Testcase failure after LENS-1432

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1438.
--

> Testcase failure after LENS-1432
> 
>
> Key: LENS-1438
> URL: https://issues.apache.org/jira/browse/LENS-1438
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1438.2017-06-13_15:01:36.patch
>
>
> Test failing: org.apache.lens.server.rewrite.TestRewriting#testCubeQuery



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


[jira] [Closed] (LENS-1387) Move Lens to java 8

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1387.
--

> Move Lens to java 8
> ---
>
> Key: LENS-1387
> URL: https://issues.apache.org/jira/browse/LENS-1387
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: 2.7, build
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1387.01.patch, LENS-1387.02.patch
>
>
> Deprecating java7 and restricting lens to only compile with java 8 + 



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


[jira] [Closed] (LENS-1348) Make pre-commit build run with -fae option

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1348.
--

> Make pre-commit build run with -fae option
> --
>
> Key: LENS-1348
> URL: https://issues.apache.org/jira/browse/LENS-1348
> Project: Apache Lens
>  Issue Type: Improvement
>  Components: build
>Reporter: Amareshwari Sriramadasu
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
>
> We see precommit build fails if one of the test fail in any module, we should 
> run it with option -fae sothat all modules get tested.



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


[jira] [Closed] (LENS-1389) Back Merge with master and fix lens-cube tests

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1389.
--

> Back Merge with master and fix lens-cube tests
> --
>
> Key: LENS-1389
> URL: https://issues.apache.org/jira/browse/LENS-1389
> Project: Apache Lens
>  Issue Type: Sub-task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1389.09.patch, LENS-1389.10.patch
>
>
> This is causing test failure in lens-1381 branch. 



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


[jira] [Closed] (LENS-1394) Create DOAP file

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1394.
--

> Create DOAP file
> 
>
> Key: LENS-1394
> URL: https://issues.apache.org/jira/browse/LENS-1394
> Project: Apache Lens
>  Issue Type: Task
>  Components: docs
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1394.01.patch
>
>
> Create doap file for project to appear in projects.apache.org



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


[jira] [Closed] (LENS-1374) Add logs in FieldValidator

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1374.
--

> Add logs in FieldValidator
> --
>
> Key: LENS-1374
> URL: https://issues.apache.org/jira/browse/LENS-1374
> Project: Apache Lens
>  Issue Type: Task
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1374.2016-11-09_17:58:38.patch
>
>
> Exceptions of fieldValidator don't provide any info in logs and it's 
> difficult to debug why fields are not queryable together. 



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


[jira] [Closed] (LENS-1336) lens/contrib is not included in modules

2017-08-17 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal closed LENS-1336.
--

> lens/contrib is not included in modules 
> 
>
> Key: LENS-1336
> URL: https://issues.apache.org/jira/browse/LENS-1336
> Project: Apache Lens
>  Issue Type: Bug
>  Components: build
>Affects Versions: 2.6
>Reporter: Puneet Gupta
>Assignee: Rajat Khandelwal
>Priority: Blocker
> Fix For: 2.6, 2.7
>
> Attachments: LENS-1336.01.patch, LENS-1336.02.patch, 
> LENS-1336.2016-09-26_19:31:24.patch, LENS-1336.patch, LENS-1336.patch
>
>




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


[jira] [Updated] (LENS-1459) Time union candidate creation phase is creating a combination with redundant candidates

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

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

> Time union candidate creation phase is creating a combination with redundant 
> candidates
> ---
>
> Key: LENS-1459
> URL: https://issues.apache.org/jira/browse/LENS-1459
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1459.2017-08-16_16:28:29.patch
>
>
> After the optimization in LENS-1452, Combinations as mentioned in the jira 
> summary can get created. Say the time range queried is {{\[f, t)}}, Candidate 
> {{a}} and {{b}} can cover {{\[f, m)}} and candidate {{c}} can cover {{\[m, 
> t)}}. Say a Union candidate is represented as {{U(cand1, cand2,...)}}. Then 
> the code creates {{U(a,b,c), U(a,c) and U(b,c)}}. If {{U(a,b,c)}} is picked 
> as final candidate, then one of {{a}} or {{b}} doesn't resolve partitions and 
> {{time_range_in}} clause is left as it is for that. 



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


[jira] [Commented] (LENS-1459) Time union candidate creation phase is creating a combination with redundant candidates

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1459:


Committed myself.

> Time union candidate creation phase is creating a combination with redundant 
> candidates
> ---
>
> Key: LENS-1459
> URL: https://issues.apache.org/jira/browse/LENS-1459
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1459.2017-08-16_16:28:29.patch
>
>
> After the optimization in LENS-1452, Combinations as mentioned in the jira 
> summary can get created. Say the time range queried is {{\[f, t)}}, Candidate 
> {{a}} and {{b}} can cover {{\[f, m)}} and candidate {{c}} can cover {{\[m, 
> t)}}. Say a Union candidate is represented as {{U(cand1, cand2,...)}}. Then 
> the code creates {{U(a,b,c), U(a,c) and U(b,c)}}. If {{U(a,b,c)}} is picked 
> as final candidate, then one of {{a}} or {{b}} doesn't resolve partitions and 
> {{time_range_in}} clause is left as it is for that. 



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


[jira] [Updated] (LENS-1459) Time union candidate creation phase is creating a combination with redundant candidates

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1459:
---
Attachment: LENS-1459.2017-08-16_16:28:29.patch

> Time union candidate creation phase is creating a combination with redundant 
> candidates
> ---
>
> Key: LENS-1459
> URL: https://issues.apache.org/jira/browse/LENS-1459
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1459.2017-08-16_16:28:29.patch
>
>
> After the optimization in LENS-1452, Combinations as mentioned in the jira 
> summary can get created. Say the time range queried is {{\[f, t)}}, Candidate 
> {{a}} and {{b}} can cover {{\[f, m)}} and candidate {{c}} can cover {{\[m, 
> t)}}. Say a Union candidate is represented as {{U(cand1, cand2,...)}}. Then 
> the code creates {{U(a,b,c), U(a,c) and U(b,c)}}. If {{U(a,b,c)}} is picked 
> as final candidate, then one of {{a}} or {{b}} doesn't resolve partitions and 
> {{time_range_in}} clause is left as it is for that. 



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


[jira] [Commented] (LENS-1459) Time union candidate creation phase is creating a combination with redundant candidates

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1459:


Small enough diff. Attaching directly

> Time union candidate creation phase is creating a combination with redundant 
> candidates
> ---
>
> Key: LENS-1459
> URL: https://issues.apache.org/jira/browse/LENS-1459
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1459.2017-08-16_16:28:29.patch
>
>
> After the optimization in LENS-1452, Combinations as mentioned in the jira 
> summary can get created. Say the time range queried is {{\[f, t)}}, Candidate 
> {{a}} and {{b}} can cover {{\[f, m)}} and candidate {{c}} can cover {{\[m, 
> t)}}. Say a Union candidate is represented as {{U(cand1, cand2,...)}}. Then 
> the code creates {{U(a,b,c), U(a,c) and U(b,c)}}. If {{U(a,b,c)}} is picked 
> as final candidate, then one of {{a}} or {{b}} doesn't resolve partitions and 
> {{time_range_in}} clause is left as it is for that. 



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


[jira] [Updated] (LENS-1459) Time union candidate creation phase is creating a combination with redundant candidates

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1459:
---
Status: Patch Available  (was: Open)

> Time union candidate creation phase is creating a combination with redundant 
> candidates
> ---
>
> Key: LENS-1459
> URL: https://issues.apache.org/jira/browse/LENS-1459
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1459.2017-08-16_16:28:29.patch
>
>
> After the optimization in LENS-1452, Combinations as mentioned in the jira 
> summary can get created. Say the time range queried is {{\[f, t)}}, Candidate 
> {{a}} and {{b}} can cover {{\[f, m)}} and candidate {{c}} can cover {{\[m, 
> t)}}. Say a Union candidate is represented as {{U(cand1, cand2,...)}}. Then 
> the code creates {{U(a,b,c), U(a,c) and U(b,c)}}. If {{U(a,b,c)}} is picked 
> as final candidate, then one of {{a}} or {{b}} doesn't resolve partitions and 
> {{time_range_in}} clause is left as it is for that. 



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


[jira] [Created] (LENS-1459) Time union candidate creation phase is creating a combination with redundant candidates

2017-08-16 Thread Rajat Khandelwal (JIRA)
Rajat Khandelwal created LENS-1459:
--

 Summary: Time union candidate creation phase is creating a 
combination with redundant candidates
 Key: LENS-1459
 URL: https://issues.apache.org/jira/browse/LENS-1459
 Project: Apache Lens
  Issue Type: Bug
  Components: cube
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal


After the optimization in LENS-1452, Combinations as mentioned in the jira 
summary can get created. Say the time range queried is {{\[f, t)}}, Candidate 
{{a}} and {{b}} can cover {{\[f, m)}} and candidate {{c}} can cover {{\[m, 
t)}}. Say a Union candidate is represented as {{U(cand1, cand2,...)}}. Then the 
code creates {{U(a,b,c), U(a,c) and U(b,c)}}. If {{U(a,b,c)}} is picked as 
final candidate, then one of {{a}} or {{b}} doesn't resolve partitions and 
{{time_range_in}} clause is left as it is for that. 



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


[jira] [Updated] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1439:
---
Status: Patch Available  (was: In Progress)

> Having clause getting skipped if query goes to a segmentation containing 
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1439.01.patch, LENS-1439.01.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext



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


[jira] [Updated] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1439:
---
Attachment: LENS-1439.01.patch

> Having clause getting skipped if query goes to a segmentation containing 
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1439.01.patch, LENS-1439.01.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext



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


[jira] [Commented] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1439:


Taking patch from reviewboard and attaching

> Having clause getting skipped if query goes to a segmentation containing 
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1439.01.patch, LENS-1439.01.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext



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


[jira] [Commented] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1439:


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

> Having clause getting skipped if query goes to a segmentation containing 
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1439.01.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext



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


[jira] [Work started] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Work on LENS-1439 started by Rajat Khandelwal.
--
> Having clause getting skipped if query goes to a segmentation containing 
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1439.01.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext



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


[jira] [Reopened] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment

2017-08-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal reopened LENS-1439:


Reopening as the issue is not fixed. 

> Having clause getting skipped if query goes to a segmentation containing 
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1439.01.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext



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


[jira] [Updated] (LENS-1456) Deadlock in jdbcdriver

2017-08-11 Thread Rajat Khandelwal (JIRA)

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

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

> Deadlock in jdbcdriver
> --
>
> Key: LENS-1456
> URL: https://issues.apache.org/jira/browse/LENS-1456
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Rajat Khandelwal
> Attachments: LENS-1456.2017-07-31_18:19:00.patch
>
>
> Here are the details :
> {noformat}
> Found one Java-level deadlock:
> =
> "lens-driver-jdbc-795":
>   waiting to lock monitor 0x7f98200140a8 (object 0x000319a3dc88, a 
> org.apache.lens.server.api.query.QueryContext),
>   which is held by "query-cancellation-pool-Thread-3"
> "query-cancellation-pool-Thread-3":
>   waiting to lock monitor 0x7f97ec002d08 (object 0x000319a8c6e0, a 
> java.util.ArrayList),
>   which is held by "lens-driver-jdbc-795"
> Java stack information for the threads listed above:
> ===
> "lens-driver-jdbc-795":
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.updateStatus(QueryExecutionServiceImpl.java:1049)
> - waiting to lock <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$1900(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$AsyncStatusUpdater.onDriverStatusUpdated(QueryExecutionServiceImpl.java:853)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:577)
> - locked <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:299)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:237)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> "query-cancellation-pool-Thread-3":
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:575)
> - waiting to lock <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:587)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver.cancelQuery(JDBCDriver.java:962)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.cancelQuery(QueryExecutionServiceImpl.java:2720)
> - locked <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$3500(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$CancelQueryTask.run(QueryExecutionServiceImpl.java:1667)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Found 1 deadlock.
> {noformat}



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


[jira] [Updated] (LENS-1456) Deadlock in jdbcdriver

2017-07-31 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1456:
---
Status: Patch Available  (was: Open)

> Deadlock in jdbcdriver
> --
>
> Key: LENS-1456
> URL: https://issues.apache.org/jira/browse/LENS-1456
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Rajat Khandelwal
> Attachments: LENS-1456.2017-07-31_18:19:00.patch
>
>
> Here are the details :
> {noformat}
> Found one Java-level deadlock:
> =
> "lens-driver-jdbc-795":
>   waiting to lock monitor 0x7f98200140a8 (object 0x000319a3dc88, a 
> org.apache.lens.server.api.query.QueryContext),
>   which is held by "query-cancellation-pool-Thread-3"
> "query-cancellation-pool-Thread-3":
>   waiting to lock monitor 0x7f97ec002d08 (object 0x000319a8c6e0, a 
> java.util.ArrayList),
>   which is held by "lens-driver-jdbc-795"
> Java stack information for the threads listed above:
> ===
> "lens-driver-jdbc-795":
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.updateStatus(QueryExecutionServiceImpl.java:1049)
> - waiting to lock <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$1900(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$AsyncStatusUpdater.onDriverStatusUpdated(QueryExecutionServiceImpl.java:853)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:577)
> - locked <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:299)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:237)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> "query-cancellation-pool-Thread-3":
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:575)
> - waiting to lock <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:587)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver.cancelQuery(JDBCDriver.java:962)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.cancelQuery(QueryExecutionServiceImpl.java:2720)
> - locked <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$3500(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$CancelQueryTask.run(QueryExecutionServiceImpl.java:1667)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Found 1 deadlock.
> {noformat}



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


[jira] [Updated] (LENS-1456) Deadlock in jdbcdriver

2017-07-31 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1456:
---
Attachment: LENS-1456.2017-07-31_18:19:00.patch

> Deadlock in jdbcdriver
> --
>
> Key: LENS-1456
> URL: https://issues.apache.org/jira/browse/LENS-1456
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Rajat Khandelwal
> Attachments: LENS-1456.2017-07-31_18:19:00.patch
>
>
> Here are the details :
> {noformat}
> Found one Java-level deadlock:
> =
> "lens-driver-jdbc-795":
>   waiting to lock monitor 0x7f98200140a8 (object 0x000319a3dc88, a 
> org.apache.lens.server.api.query.QueryContext),
>   which is held by "query-cancellation-pool-Thread-3"
> "query-cancellation-pool-Thread-3":
>   waiting to lock monitor 0x7f97ec002d08 (object 0x000319a8c6e0, a 
> java.util.ArrayList),
>   which is held by "lens-driver-jdbc-795"
> Java stack information for the threads listed above:
> ===
> "lens-driver-jdbc-795":
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.updateStatus(QueryExecutionServiceImpl.java:1049)
> - waiting to lock <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$1900(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$AsyncStatusUpdater.onDriverStatusUpdated(QueryExecutionServiceImpl.java:853)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:577)
> - locked <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:299)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:237)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> "query-cancellation-pool-Thread-3":
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:575)
> - waiting to lock <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:587)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver.cancelQuery(JDBCDriver.java:962)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.cancelQuery(QueryExecutionServiceImpl.java:2720)
> - locked <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$3500(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$CancelQueryTask.run(QueryExecutionServiceImpl.java:1667)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Found 1 deadlock.
> {noformat}



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


[jira] [Assigned] (LENS-1456) Deadlock in jdbcdriver

2017-07-31 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal reassigned LENS-1456:
--

Assignee: Rajat Khandelwal

> Deadlock in jdbcdriver
> --
>
> Key: LENS-1456
> URL: https://issues.apache.org/jira/browse/LENS-1456
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Rajat Khandelwal
> Attachments: LENS-1456.2017-07-31_18:19:00.patch
>
>
> Here are the details :
> {noformat}
> Found one Java-level deadlock:
> =
> "lens-driver-jdbc-795":
>   waiting to lock monitor 0x7f98200140a8 (object 0x000319a3dc88, a 
> org.apache.lens.server.api.query.QueryContext),
>   which is held by "query-cancellation-pool-Thread-3"
> "query-cancellation-pool-Thread-3":
>   waiting to lock monitor 0x7f97ec002d08 (object 0x000319a8c6e0, a 
> java.util.ArrayList),
>   which is held by "lens-driver-jdbc-795"
> Java stack information for the threads listed above:
> ===
> "lens-driver-jdbc-795":
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.updateStatus(QueryExecutionServiceImpl.java:1049)
> - waiting to lock <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$1900(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$AsyncStatusUpdater.onDriverStatusUpdated(QueryExecutionServiceImpl.java:853)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:577)
> - locked <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:299)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:237)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> "query-cancellation-pool-Thread-3":
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:575)
> - waiting to lock <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:587)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver.cancelQuery(JDBCDriver.java:962)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.cancelQuery(QueryExecutionServiceImpl.java:2720)
> - locked <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$3500(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$CancelQueryTask.run(QueryExecutionServiceImpl.java:1667)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Found 1 deadlock.
> {noformat}



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


[jira] [Commented] (LENS-1456) Deadlock in jdbcdriver

2017-07-31 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1456:


Small enough diff. Attaching directly

> Deadlock in jdbcdriver
> --
>
> Key: LENS-1456
> URL: https://issues.apache.org/jira/browse/LENS-1456
> Project: Apache Lens
>  Issue Type: Bug
>  Components: driver-jdbc
>Reporter: Amareshwari Sriramadasu
>Assignee: Rajat Khandelwal
> Attachments: LENS-1456.2017-07-31_18:19:00.patch
>
>
> Here are the details :
> {noformat}
> Found one Java-level deadlock:
> =
> "lens-driver-jdbc-795":
>   waiting to lock monitor 0x7f98200140a8 (object 0x000319a3dc88, a 
> org.apache.lens.server.api.query.QueryContext),
>   which is held by "query-cancellation-pool-Thread-3"
> "query-cancellation-pool-Thread-3":
>   waiting to lock monitor 0x7f97ec002d08 (object 0x000319a8c6e0, a 
> java.util.ArrayList),
>   which is held by "lens-driver-jdbc-795"
> Java stack information for the threads listed above:
> ===
> "lens-driver-jdbc-795":
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.updateStatus(QueryExecutionServiceImpl.java:1049)
> - waiting to lock <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$1900(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$AsyncStatusUpdater.onDriverStatusUpdated(QueryExecutionServiceImpl.java:853)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:577)
> - locked <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:299)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver$QueryCallable.call(JDBCDriver.java:237)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> "query-cancellation-pool-Thread-3":
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:575)
> - waiting to lock <0x000319a8c6e0> (a java.util.ArrayList)
> at 
> org.apache.lens.server.api.query.QueryContext.setDriverStatus(QueryContext.java:587)
> at 
> org.apache.lens.driver.jdbc.JDBCDriver.cancelQuery(JDBCDriver.java:962)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.cancelQuery(QueryExecutionServiceImpl.java:2720)
> - locked <0x000319a3dc88> (a 
> org.apache.lens.server.api.query.QueryContext)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl.access$3500(QueryExecutionServiceImpl.java:110)
> at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$CancelQueryTask.run(QueryExecutionServiceImpl.java:1667)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Found 1 deadlock.
> {noformat}



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


[jira] [Updated] (LENS-1457) ExpressionResolver pruning expression when some tables don't have ref columns of the expressions

2017-07-31 Thread Rajat Khandelwal (JIRA)

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

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

> ExpressionResolver pruning expression when some tables don't have ref columns 
> of the expressions
> 
>
> Key: LENS-1457
> URL: https://issues.apache.org/jira/browse/LENS-1457
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1457.01.patch
>
>
> In an expression {{f(a,b)}} where {{a}} and {{b}} are ref dim attributes 
> themselves. If a or b are not directly available in a fact and the chain 
> source columns are also not available, this expression is marked as 
> unanswerable from all facts. 



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


[jira] [Commented] (LENS-1457) ExpressionResolver pruning expression when some tables don't have ref columns of the expressions

2017-07-31 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1457:


Committed myself.

> ExpressionResolver pruning expression when some tables don't have ref columns 
> of the expressions
> 
>
> Key: LENS-1457
> URL: https://issues.apache.org/jira/browse/LENS-1457
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1457.01.patch
>
>
> In an expression {{f(a,b)}} where {{a}} and {{b}} are ref dim attributes 
> themselves. If a or b are not directly available in a fact and the chain 
> source columns are also not available, this expression is marked as 
> unanswerable from all facts. 



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


[jira] [Updated] (LENS-1457) ExpressionResolver pruning expression when some tables don't have ref columns of the expressions

2017-07-26 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1457:
---
Attachment: LENS-1457.01.patch

> ExpressionResolver pruning expression when some tables don't have ref columns 
> of the expressions
> 
>
> Key: LENS-1457
> URL: https://issues.apache.org/jira/browse/LENS-1457
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1457.01.patch
>
>
> In an expression {{f(a,b)}} where {{a}} and {{b}} are ref dim attributes 
> themselves. If a or b are not directly available in a fact and the chain 
> source columns are also not available, this expression is marked as 
> unanswerable from all facts. 



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


[jira] [Commented] (LENS-1457) ExpressionResolver pruning expression when some tables don't have ref columns of the expressions

2017-07-26 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1457:


Taking patch from reviewboard and attaching

> ExpressionResolver pruning expression when some tables don't have ref columns 
> of the expressions
> 
>
> Key: LENS-1457
> URL: https://issues.apache.org/jira/browse/LENS-1457
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1457.01.patch
>
>
> In an expression {{f(a,b)}} where {{a}} and {{b}} are ref dim attributes 
> themselves. If a or b are not directly available in a fact and the chain 
> source columns are also not available, this expression is marked as 
> unanswerable from all facts. 



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


[jira] [Commented] (LENS-1457) ExpressionResolver pruning expression when some tables don't have ref columns of the expressions

2017-07-26 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1457:


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

> ExpressionResolver pruning expression when some tables don't have ref columns 
> of the expressions
> 
>
> Key: LENS-1457
> URL: https://issues.apache.org/jira/browse/LENS-1457
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1457.01.patch
>
>
> In an expression {{f(a,b)}} where {{a}} and {{b}} are ref dim attributes 
> themselves. If a or b are not directly available in a fact and the chain 
> source columns are also not available, this expression is marked as 
> unanswerable from all facts. 



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


[jira] [Updated] (LENS-1457) ExpressionResolver pruning expression when some tables don't have ref columns of the expressions

2017-07-26 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1457:
---
Status: Patch Available  (was: In Progress)

> ExpressionResolver pruning expression when some tables don't have ref columns 
> of the expressions
> 
>
> Key: LENS-1457
> URL: https://issues.apache.org/jira/browse/LENS-1457
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1457.01.patch
>
>
> In an expression {{f(a,b)}} where {{a}} and {{b}} are ref dim attributes 
> themselves. If a or b are not directly available in a fact and the chain 
> source columns are also not available, this expression is marked as 
> unanswerable from all facts. 



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


[jira] [Work started] (LENS-1457) ExpressionResolver pruning expression when some tables don't have ref columns of the expressions

2017-07-26 Thread Rajat Khandelwal (JIRA)

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

Work on LENS-1457 started by Rajat Khandelwal.
--
> ExpressionResolver pruning expression when some tables don't have ref columns 
> of the expressions
> 
>
> Key: LENS-1457
> URL: https://issues.apache.org/jira/browse/LENS-1457
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> In an expression {{f(a,b)}} where {{a}} and {{b}} are ref dim attributes 
> themselves. If a or b are not directly available in a fact and the chain 
> source columns are also not available, this expression is marked as 
> unanswerable from all facts. 



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


[jira] [Created] (LENS-1457) ExpressionResolver pruning expression when some tables don't have ref columns of the expressions

2017-07-26 Thread Rajat Khandelwal (JIRA)
Rajat Khandelwal created LENS-1457:
--

 Summary: ExpressionResolver pruning expression when some tables 
don't have ref columns of the expressions
 Key: LENS-1457
 URL: https://issues.apache.org/jira/browse/LENS-1457
 Project: Apache Lens
  Issue Type: Bug
  Components: cube
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal


In an expression {{f(a,b)}} where {{a}} and {{b}} are ref dim attributes 
themselves. If a or b are not directly available in a fact and the chain source 
columns are also not available, this expression is marked as unanswerable from 
all facts. 



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


[jira] [Updated] (LENS-1455) Getting expression ast to generate default expression should consider all expression contexts

2017-07-20 Thread Rajat Khandelwal (JIRA)

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

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

> Getting expression ast to generate default expression should consider all 
> expression contexts
> -
>
> Key: LENS-1455
> URL: https://issues.apache.org/jira/browse/LENS-1455
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1455.01.patch, LENS-1455.02.patch, 
> LENS-1455.03.patch
>
>
> in case an expression is answered from a segmentation, the default expression 
> can't be generated. 



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


[jira] [Updated] (LENS-1454) Time Covering set algorithm is skipping some combinations

2017-07-20 Thread Rajat Khandelwal (JIRA)

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

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

> Time Covering set algorithm is skipping some combinations
> -
>
> Key: LENS-1454
> URL: https://issues.apache.org/jira/browse/LENS-1454
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1454.01.patch
>
>
> The current algorithm is incomplete. Will attach a patch. 



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


[jira] [Commented] (LENS-1455) Getting expression ast to generate default expression should consider all expression contexts

2017-07-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1455:


Committed myself.

> Getting expression ast to generate default expression should consider all 
> expression contexts
> -
>
> Key: LENS-1455
> URL: https://issues.apache.org/jira/browse/LENS-1455
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1455.01.patch, LENS-1455.02.patch, 
> LENS-1455.03.patch
>
>
> in case an expression is answered from a segmentation, the default expression 
> can't be generated. 



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


[jira] [Commented] (LENS-1453) Method metrics names duplicate for segmentation inner rewrite

2017-07-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1453:


Committed myself.

> Method metrics names duplicate for segmentation inner rewrite
> -
>
> Key: LENS-1453
> URL: https://issues.apache.org/jira/browse/LENS-1453
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1453.01.patch
>
>
> {noformat}
> java.lang.IllegalArgumentException: A metric named 
> lens.MethodMetricGauge.9a18f287-a40f-4108-b499-932c3edf6eaa-hive/prod-org.apache.lens.cube.parse.ColumnResolver-ITER-0
>  already exists
>   at com.codahale.metrics.MetricRegistry.register(MetricRegistry.java:91) 
> ~[metrics-core-3.0.2.jar:3.0.2]
>   at 
> org.apache.lens.server.api.metrics.MethodMetricGauge.markSuccess(MethodMetricGauge.java:61)
>  ~[lens-server-api-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:264)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:232)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationCandidate.rewriteInternal(SegmentationCandidate.java:145)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter$Exploder.shouldBeRemoved(SegmentationInnerRewriter.java:57)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter$Exploder.access$300(SegmentationInnerRewriter.java:49)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter.lambda$rewriteContext$0(SegmentationInnerRewriter.java:46)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter$$Lambda$82/1668365591.test(Unknown
>  Source) ~[na:na]
>   at java.util.Collection.removeIf(Collection.java:414) ~[na:1.8.0_40]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter.rewriteContext(SegmentationInnerRewriter.java:46)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:263)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:232)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:248)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.server.rewrite.RewriteUtil$DriverRewriterRunnable.run(RewriteUtil.java:392)
>  ~[classes/:na]
>   at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$RewriteEstimateRunnable.run(QueryExecutionServiceImpl.java:1855)
>  [classes/:na]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_40]
>   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.4.14#64029)


[jira] [Updated] (LENS-1453) Method metrics names duplicate for segmentation inner rewrite

2017-07-20 Thread Rajat Khandelwal (JIRA)

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

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

> Method metrics names duplicate for segmentation inner rewrite
> -
>
> Key: LENS-1453
> URL: https://issues.apache.org/jira/browse/LENS-1453
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1453.01.patch
>
>
> {noformat}
> java.lang.IllegalArgumentException: A metric named 
> lens.MethodMetricGauge.9a18f287-a40f-4108-b499-932c3edf6eaa-hive/prod-org.apache.lens.cube.parse.ColumnResolver-ITER-0
>  already exists
>   at com.codahale.metrics.MetricRegistry.register(MetricRegistry.java:91) 
> ~[metrics-core-3.0.2.jar:3.0.2]
>   at 
> org.apache.lens.server.api.metrics.MethodMetricGauge.markSuccess(MethodMetricGauge.java:61)
>  ~[lens-server-api-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:264)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:232)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationCandidate.rewriteInternal(SegmentationCandidate.java:145)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter$Exploder.shouldBeRemoved(SegmentationInnerRewriter.java:57)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter$Exploder.access$300(SegmentationInnerRewriter.java:49)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter.lambda$rewriteContext$0(SegmentationInnerRewriter.java:46)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter$$Lambda$82/1668365591.test(Unknown
>  Source) ~[na:na]
>   at java.util.Collection.removeIf(Collection.java:414) ~[na:1.8.0_40]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter.rewriteContext(SegmentationInnerRewriter.java:46)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:263)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:232)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:248)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.server.rewrite.RewriteUtil$DriverRewriterRunnable.run(RewriteUtil.java:392)
>  ~[classes/:na]
>   at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$RewriteEstimateRunnable.run(QueryExecutionServiceImpl.java:1855)
>  [classes/:na]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_40]
>   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.4.14#64029)


[jira] [Commented] (LENS-1454) Time Covering set algorithm is skipping some combinations

2017-07-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1454:


Committed myself.

> Time Covering set algorithm is skipping some combinations
> -
>
> Key: LENS-1454
> URL: https://issues.apache.org/jira/browse/LENS-1454
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1454.01.patch
>
>
> The current algorithm is incomplete. Will attach a patch. 



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


[jira] [Commented] (LENS-1455) Getting expression ast to generate default expression should consider all expression contexts

2017-07-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1455:


Taking patch from reviewboard and attaching

> Getting expression ast to generate default expression should consider all 
> expression contexts
> -
>
> Key: LENS-1455
> URL: https://issues.apache.org/jira/browse/LENS-1455
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1455.01.patch, LENS-1455.02.patch, 
> LENS-1455.03.patch
>
>
> in case an expression is answered from a segmentation, the default expression 
> can't be generated. 



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


[jira] [Updated] (LENS-1455) Getting expression ast to generate default expression should consider all expression contexts

2017-07-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1455:
---
Attachment: LENS-1455.03.patch

> Getting expression ast to generate default expression should consider all 
> expression contexts
> -
>
> Key: LENS-1455
> URL: https://issues.apache.org/jira/browse/LENS-1455
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1455.01.patch, LENS-1455.02.patch, 
> LENS-1455.03.patch
>
>
> in case an expression is answered from a segmentation, the default expression 
> can't be generated. 



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


[jira] [Commented] (LENS-1455) Getting expression ast to generate default expression should consider all expression contexts

2017-07-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1455:


Taking patch from reviewboard and attaching

> Getting expression ast to generate default expression should consider all 
> expression contexts
> -
>
> Key: LENS-1455
> URL: https://issues.apache.org/jira/browse/LENS-1455
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1455.01.patch, LENS-1455.02.patch
>
>
> in case an expression is answered from a segmentation, the default expression 
> can't be generated. 



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


[jira] [Updated] (LENS-1455) Getting expression ast to generate default expression should consider all expression contexts

2017-07-19 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1455:
---
Attachment: LENS-1455.01.patch

> Getting expression ast to generate default expression should consider all 
> expression contexts
> -
>
> Key: LENS-1455
> URL: https://issues.apache.org/jira/browse/LENS-1455
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1455.01.patch
>
>
> in case an expression is answered from a segmentation, the default expression 
> can't be generated. 



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


[jira] [Commented] (LENS-1455) Getting expression ast to generate default expression should consider all expression contexts

2017-07-19 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1455:


Taking patch from reviewboard and attaching

> Getting expression ast to generate default expression should consider all 
> expression contexts
> -
>
> Key: LENS-1455
> URL: https://issues.apache.org/jira/browse/LENS-1455
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1455.01.patch
>
>
> in case an expression is answered from a segmentation, the default expression 
> can't be generated. 



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


[jira] [Updated] (LENS-1455) Getting expression ast to generate default expression should consider all expression contexts

2017-07-19 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1455:
---
Status: Patch Available  (was: In Progress)

> Getting expression ast to generate default expression should consider all 
> expression contexts
> -
>
> Key: LENS-1455
> URL: https://issues.apache.org/jira/browse/LENS-1455
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1455.01.patch
>
>
> in case an expression is answered from a segmentation, the default expression 
> can't be generated. 



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


[jira] [Work started] (LENS-1455) Getting expression ast to generate default expression should consider all expression contexts

2017-07-19 Thread Rajat Khandelwal (JIRA)

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

Work on LENS-1455 started by Rajat Khandelwal.
--
> Getting expression ast to generate default expression should consider all 
> expression contexts
> -
>
> Key: LENS-1455
> URL: https://issues.apache.org/jira/browse/LENS-1455
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> in case an expression is answered from a segmentation, the default expression 
> can't be generated. 



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


[jira] [Updated] (LENS-1454) Time Covering set algorithm is skipping some combinations

2017-07-19 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1454:
---
Status: Patch Available  (was: In Progress)

> Time Covering set algorithm is skipping some combinations
> -
>
> Key: LENS-1454
> URL: https://issues.apache.org/jira/browse/LENS-1454
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1454.01.patch
>
>
> The current algorithm is incomplete. Will attach a patch. 



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


[jira] [Commented] (LENS-1454) Time Covering set algorithm is skipping some combinations

2017-07-19 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1454:


Taking patch from reviewboard and attaching

> Time Covering set algorithm is skipping some combinations
> -
>
> Key: LENS-1454
> URL: https://issues.apache.org/jira/browse/LENS-1454
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1454.01.patch
>
>
> The current algorithm is incomplete. Will attach a patch. 



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


[jira] [Commented] (LENS-1453) Method metrics names duplicate for segmentation inner rewrite

2017-07-19 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1453:


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

> Method metrics names duplicate for segmentation inner rewrite
> -
>
> Key: LENS-1453
> URL: https://issues.apache.org/jira/browse/LENS-1453
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1453.01.patch
>
>
> {noformat}
> java.lang.IllegalArgumentException: A metric named 
> lens.MethodMetricGauge.9a18f287-a40f-4108-b499-932c3edf6eaa-hive/prod-org.apache.lens.cube.parse.ColumnResolver-ITER-0
>  already exists
>   at com.codahale.metrics.MetricRegistry.register(MetricRegistry.java:91) 
> ~[metrics-core-3.0.2.jar:3.0.2]
>   at 
> org.apache.lens.server.api.metrics.MethodMetricGauge.markSuccess(MethodMetricGauge.java:61)
>  ~[lens-server-api-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:264)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:232)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationCandidate.rewriteInternal(SegmentationCandidate.java:145)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter$Exploder.shouldBeRemoved(SegmentationInnerRewriter.java:57)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter$Exploder.access$300(SegmentationInnerRewriter.java:49)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter.lambda$rewriteContext$0(SegmentationInnerRewriter.java:46)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter$$Lambda$82/1668365591.test(Unknown
>  Source) ~[na:na]
>   at java.util.Collection.removeIf(Collection.java:414) ~[na:1.8.0_40]
>   at 
> org.apache.lens.cube.parse.SegmentationInnerRewriter.rewriteContext(SegmentationInnerRewriter.java:46)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:263)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:232)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:248)
>  ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
>   at 
> org.apache.lens.server.rewrite.RewriteUtil$DriverRewriterRunnable.run(RewriteUtil.java:392)
>  ~[classes/:na]
>   at 
> org.apache.lens.server.query.QueryExecutionServiceImpl$RewriteEstimateRunnable.run(QueryExecutionServiceImpl.java:1855)
>  [classes/:na]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_40]
>   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.4.14#64029)


[jira] [Created] (LENS-1453) Method metrics names duplicate for segmentation inner rewrite

2017-07-19 Thread Rajat Khandelwal (JIRA)
Rajat Khandelwal created LENS-1453:
--

 Summary: Method metrics names duplicate for segmentation inner 
rewrite
 Key: LENS-1453
 URL: https://issues.apache.org/jira/browse/LENS-1453
 Project: Apache Lens
  Issue Type: Bug
  Components: cube
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal


{noformat}
java.lang.IllegalArgumentException: A metric named 
lens.MethodMetricGauge.9a18f287-a40f-4108-b499-932c3edf6eaa-hive/prod-org.apache.lens.cube.parse.ColumnResolver-ITER-0
 already exists
at com.codahale.metrics.MetricRegistry.register(MetricRegistry.java:91) 
~[metrics-core-3.0.2.jar:3.0.2]
at 
org.apache.lens.server.api.metrics.MethodMetricGauge.markSuccess(MethodMetricGauge.java:61)
 ~[lens-server-api-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:264)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:232)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.SegmentationCandidate.rewriteInternal(SegmentationCandidate.java:145)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.SegmentationInnerRewriter$Exploder.shouldBeRemoved(SegmentationInnerRewriter.java:57)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.SegmentationInnerRewriter$Exploder.access$300(SegmentationInnerRewriter.java:49)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.SegmentationInnerRewriter.lambda$rewriteContext$0(SegmentationInnerRewriter.java:46)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.SegmentationInnerRewriter$$Lambda$82/1668365591.test(Unknown
 Source) ~[na:na]
at java.util.Collection.removeIf(Collection.java:414) ~[na:1.8.0_40]
at 
org.apache.lens.cube.parse.SegmentationInnerRewriter.rewriteContext(SegmentationInnerRewriter.java:46)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:263)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:232)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.cube.parse.CubeQueryRewriter.rewrite(CubeQueryRewriter.java:248)
 ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at 
org.apache.lens.server.rewrite.RewriteUtil$DriverRewriterRunnable.run(RewriteUtil.java:392)
 ~[classes/:na]
at 
org.apache.lens.server.query.QueryExecutionServiceImpl$RewriteEstimateRunnable.run(QueryExecutionServiceImpl.java:1855)
 [classes/:na]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_40]
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.4.14#64029)


[jira] [Work started] (LENS-1452) Optimize Time Union candidate Algorithm

2017-07-10 Thread Rajat Khandelwal (JIRA)

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

Work on LENS-1452 started by Rajat Khandelwal.
--
> Optimize Time Union candidate Algorithm
> ---
>
> Key: LENS-1452
> URL: https://issues.apache.org/jira/browse/LENS-1452
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> Current algorithm: 
> * Create bitmap (equivalent to powerset)
> * from the powerset, add sets which can complete all time ranges as candidates
> * Prune sets which are contained in other sets
> Proposed change:
> The following recursion implemented iteratively: 
> {code}
> (ignoring cubeql for clarity)
> getCombinations(candidates) = getCombinationsRecursive(emptyList(), 
> candidates)
> getCombinationsRecursive(incompleteCombinations: List, 
> candidates: List) =
> head, tail = head and tail of linked List candidates
> add head to all elements of incompleteCombinations.
> add {{ [head] }} as one incompleteCombination.
> complete = remove now complete combinations from incompleteCombinations
> return {{complete ++ 
> getCombinationsTailRecursive(incompleteCombinations+[head], tail)}}
> {code}
> The improvement is, that redundant union candidates like {a,b,c} won't be 
> generated if {a,b} is already covering time ranges. This will only generate 
> minimal sets that cover time ranges. So the memory footprint isn't O( 2^n ) 
> anymore. 



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


[jira] [Updated] (LENS-1452) Optimize Time Union candidate Algorithm

2017-07-10 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1452:
---
Attachment: LENS-1452.01.patch

> Optimize Time Union candidate Algorithm
> ---
>
> Key: LENS-1452
> URL: https://issues.apache.org/jira/browse/LENS-1452
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1452.01.patch
>
>
> Current algorithm: 
> * Create bitmap (equivalent to powerset)
> * from the powerset, add sets which can complete all time ranges as candidates
> * Prune sets which are contained in other sets
> Proposed change:
> The following recursion implemented iteratively: 
> {code}
> (ignoring cubeql for clarity)
> getCombinations(candidates) = getCombinationsRecursive(emptyList(), 
> candidates)
> getCombinationsRecursive(incompleteCombinations: List, 
> candidates: List) =
> head, tail = head and tail of linked List candidates
> add head to all elements of incompleteCombinations.
> add {{ [head] }} as one incompleteCombination.
> complete = remove now complete combinations from incompleteCombinations
> return {{complete ++ 
> getCombinationsTailRecursive(incompleteCombinations+[head], tail)}}
> {code}
> The improvement is, that redundant union candidates like {a,b,c} won't be 
> generated if {a,b} is already covering time ranges. This will only generate 
> minimal sets that cover time ranges. So the memory footprint isn't O( 2^n ) 
> anymore. 



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


[jira] [Updated] (LENS-1452) Optimize Time Union candidate Algorithm

2017-07-10 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1452:
---
Status: Patch Available  (was: In Progress)

> Optimize Time Union candidate Algorithm
> ---
>
> Key: LENS-1452
> URL: https://issues.apache.org/jira/browse/LENS-1452
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1452.01.patch
>
>
> Current algorithm: 
> * Create bitmap (equivalent to powerset)
> * from the powerset, add sets which can complete all time ranges as candidates
> * Prune sets which are contained in other sets
> Proposed change:
> The following recursion implemented iteratively: 
> {code}
> (ignoring cubeql for clarity)
> getCombinations(candidates) = getCombinationsRecursive(emptyList(), 
> candidates)
> getCombinationsRecursive(incompleteCombinations: List, 
> candidates: List) =
> head, tail = head and tail of linked List candidates
> add head to all elements of incompleteCombinations.
> add {{ [head] }} as one incompleteCombination.
> complete = remove now complete combinations from incompleteCombinations
> return {{complete ++ 
> getCombinationsTailRecursive(incompleteCombinations+[head], tail)}}
> {code}
> The improvement is, that redundant union candidates like {a,b,c} won't be 
> generated if {a,b} is already covering time ranges. This will only generate 
> minimal sets that cover time ranges. So the memory footprint isn't O( 2^n ) 
> anymore. 



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


[jira] [Commented] (LENS-1452) Optimize Time Union candidate Algorithm

2017-07-10 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1452:


Taking patch from reviewboard and attaching

> Optimize Time Union candidate Algorithm
> ---
>
> Key: LENS-1452
> URL: https://issues.apache.org/jira/browse/LENS-1452
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1452.01.patch
>
>
> Current algorithm: 
> * Create bitmap (equivalent to powerset)
> * from the powerset, add sets which can complete all time ranges as candidates
> * Prune sets which are contained in other sets
> Proposed change:
> The following recursion implemented iteratively: 
> {code}
> (ignoring cubeql for clarity)
> getCombinations(candidates) = getCombinationsRecursive(emptyList(), 
> candidates)
> getCombinationsRecursive(incompleteCombinations: List, 
> candidates: List) =
> head, tail = head and tail of linked List candidates
> add head to all elements of incompleteCombinations.
> add {{ [head] }} as one incompleteCombination.
> complete = remove now complete combinations from incompleteCombinations
> return {{complete ++ 
> getCombinationsTailRecursive(incompleteCombinations+[head], tail)}}
> {code}
> The improvement is, that redundant union candidates like {a,b,c} won't be 
> generated if {a,b} is already covering time ranges. This will only generate 
> minimal sets that cover time ranges. So the memory footprint isn't O( 2^n ) 
> anymore. 



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


[jira] [Commented] (LENS-1452) Optimize Time Union candidate Algorithm

2017-07-10 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1452:


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

> Optimize Time Union candidate Algorithm
> ---
>
> Key: LENS-1452
> URL: https://issues.apache.org/jira/browse/LENS-1452
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> Current algorithm: 
> * Create bitmap (equivalent to powerset)
> * from the powerset, add sets which can complete all time ranges as candidates
> * Prune sets which are contained in other sets
> Proposed change:
> The following recursion implemented iteratively: 
> {code}
> (ignoring cubeql for clarity)
> getCombinations(candidates) = getCombinationsRecursive(emptyList(), 
> candidates)
> getCombinationsRecursive(incompleteCombinations: List, 
> candidates: List) =
> head, tail = head and tail of linked List candidates
> add head to all elements of incompleteCombinations.
> add {{ [head] }} as one incompleteCombination.
> complete = remove now complete combinations from incompleteCombinations
> return {{complete ++ 
> getCombinationsTailRecursive(incompleteCombinations+[head], tail)}}
> {code}
> The improvement is, that redundant union candidates like {a,b,c} won't be 
> generated if {a,b} is already covering time ranges. This will only generate 
> minimal sets that cover time ranges. So the memory footprint isn't O( 2^n ) 
> anymore. 



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


[jira] [Commented] (LENS-1451) Enforcing valid fact tables doesn't filter out segmentations

2017-07-06 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1451:


Committed myself.

> Enforcing valid fact tables doesn't filter out segmentations
> 
>
> Key: LENS-1451
> URL: https://issues.apache.org/jira/browse/LENS-1451
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1451.01.patch
>
>
> valid fact tables key is used to enforce which facts can be picked. 
> Currently, this property still lets segmentations remain valid candidates and 
> enforcing doesn't happen. 



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


[jira] [Updated] (LENS-1451) Enforcing valid fact tables doesn't filter out segmentations

2017-07-06 Thread Rajat Khandelwal (JIRA)

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

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

> Enforcing valid fact tables doesn't filter out segmentations
> 
>
> Key: LENS-1451
> URL: https://issues.apache.org/jira/browse/LENS-1451
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1451.01.patch
>
>
> valid fact tables key is used to enforce which facts can be picked. 
> Currently, this property still lets segmentations remain valid candidates and 
> enforcing doesn't happen. 



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


[jira] [Commented] (LENS-1451) Enforcing valid fact tables doesn't filter out segmentations

2017-07-06 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1451:


Taking patch from reviewboard and attaching

> Enforcing valid fact tables doesn't filter out segmentations
> 
>
> Key: LENS-1451
> URL: https://issues.apache.org/jira/browse/LENS-1451
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1451.01.patch
>
>
> valid fact tables key is used to enforce which facts can be picked. 
> Currently, this property still lets segmentations remain valid candidates and 
> enforcing doesn't happen. 



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


[jira] [Commented] (LENS-1451) Enforcing valid fact tables doesn't filter out segmentations

2017-07-06 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1451:


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

> Enforcing valid fact tables doesn't filter out segmentations
> 
>
> Key: LENS-1451
> URL: https://issues.apache.org/jira/browse/LENS-1451
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> valid fact tables key is used to enforce which facts can be picked. 
> Currently, this property still lets segmentations remain valid candidates and 
> enforcing doesn't happen. 



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


[jira] [Commented] (LENS-1445) Expression having reference column ends up rewriting wrong query

2017-06-23 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1445:


Committed. Thanks [~sushilmohanty]

> Expression having reference column ends up rewriting wrong query
> 
>
> Key: LENS-1445
> URL: https://issues.apache.org/jira/browse/LENS-1445
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Attachments: LENS-1445.patch
>
>
> Seeing failures in query rewrite when an expression is having a reference 
> column.
> for eg : sum(case when refcol = 'abc' then msr1 + msr2 end)



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


[jira] [Updated] (LENS-1444) Optimize the algorithm of finding all eligible union candidates

2017-06-23 Thread Rajat Khandelwal (JIRA)

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

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

> Optimize the algorithm of finding all eligible union candidates
> ---
>
> Key: LENS-1444
> URL: https://issues.apache.org/jira/browse/LENS-1444
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1444.01.patch
>
>
> Current algorithm is given {{n}} candidates, first find {{2 ^n^ -1}} union 
> candidates using power set and then among them, remove the ones which don't 
> cover the queried time range(s). 
> Proposed optimization: Pushdown of the prune logic. We'll not create a list 
> of {{2 ^n^ -1}} candidates, we'll check for coverability before adding it as 
> an eligible union candidate. This will bring down the number of 
> {{UnionCandidates}} in the memory and preventing Full-GC. 



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


[jira] [Updated] (LENS-1445) Expression having reference column ends up rewriting wrong query

2017-06-23 Thread Rajat Khandelwal (JIRA)

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

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

> Expression having reference column ends up rewriting wrong query
> 
>
> Key: LENS-1445
> URL: https://issues.apache.org/jira/browse/LENS-1445
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Attachments: LENS-1445.patch
>
>
> Seeing failures in query rewrite when an expression is having a reference 
> column.
> for eg : sum(case when refcol = 'abc' then msr1 + msr2 end)



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


[jira] [Commented] (LENS-1444) Optimize the algorithm of finding all eligible union candidates

2017-06-23 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1444:


Committed myself.

> Optimize the algorithm of finding all eligible union candidates
> ---
>
> Key: LENS-1444
> URL: https://issues.apache.org/jira/browse/LENS-1444
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1444.01.patch
>
>
> Current algorithm is given {{n}} candidates, first find {{2 ^n^ -1}} union 
> candidates using power set and then among them, remove the ones which don't 
> cover the queried time range(s). 
> Proposed optimization: Pushdown of the prune logic. We'll not create a list 
> of {{2 ^n^ -1}} candidates, we'll check for coverability before adding it as 
> an eligible union candidate. This will bring down the number of 
> {{UnionCandidates}} in the memory and preventing Full-GC. 



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


[jira] [Commented] (LENS-1444) Optimize the algorithm of finding all eligible union candidates

2017-06-22 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1444:


Taking patch from reviewboard and attaching

> Optimize the algorithm of finding all eligible union candidates
> ---
>
> Key: LENS-1444
> URL: https://issues.apache.org/jira/browse/LENS-1444
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1444.01.patch
>
>
> Current algorithm is given {{n}} candidates, first find {{2 ^n^ -1}} union 
> candidates using power set and then among them, remove the ones which don't 
> cover the queried time range(s). 
> Proposed optimization: Pushdown of the prune logic. We'll not create a list 
> of {{2 ^n^ -1}} candidates, we'll check for coverability before adding it as 
> an eligible union candidate. This will bring down the number of 
> {{UnionCandidates}} in the memory and preventing Full-GC. 



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


[jira] [Work started] (LENS-1444) Optimize the algorithm of finding all eligible union candidates

2017-06-22 Thread Rajat Khandelwal (JIRA)

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

Work on LENS-1444 started by Rajat Khandelwal.
--
> Optimize the algorithm of finding all eligible union candidates
> ---
>
> Key: LENS-1444
> URL: https://issues.apache.org/jira/browse/LENS-1444
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> Current algorithm is given {{n}} candidates, first find {{2 ^n^ -1}} union 
> candidates using power set and then among them, remove the ones which don't 
> cover the queried time range(s). 
> Proposed optimization: Pushdown of the prune logic. We'll not create a list 
> of {{2 ^n^ -1}} candidates, we'll check for coverability before adding it as 
> an eligible union candidate. This will bring down the number of 
> {{UnionCandidates}} in the memory and preventing Full-GC. 



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


[jira] [Commented] (LENS-1444) Optimize the algorithm of finding all eligible union candidates

2017-06-22 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1444:


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

> Optimize the algorithm of finding all eligible union candidates
> ---
>
> Key: LENS-1444
> URL: https://issues.apache.org/jira/browse/LENS-1444
> Project: Apache Lens
>  Issue Type: Task
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> Current algorithm is given {{n}} candidates, first find {{2 ^n^ -1}} union 
> candidates using power set and then among them, remove the ones which don't 
> cover the queried time range(s). 
> Proposed optimization: Pushdown of the prune logic. We'll not create a list 
> of {{2 ^n^ -1}} candidates, we'll check for coverability before adding it as 
> an eligible union candidate. This will bring down the number of 
> {{UnionCandidates}} in the memory and preventing Full-GC. 



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


[jira] [Created] (LENS-1444) Optimize the algorithm of finding all eligible union candidates

2017-06-22 Thread Rajat Khandelwal (JIRA)
Rajat Khandelwal created LENS-1444:
--

 Summary: Optimize the algorithm of finding all eligible union 
candidates
 Key: LENS-1444
 URL: https://issues.apache.org/jira/browse/LENS-1444
 Project: Apache Lens
  Issue Type: Task
  Components: cube
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal


Current algorithm is given {{n}} candidates, first find {{2 ^n^ -1}} union 
candidates using power set and then among them, remove the ones which don't 
cover the queried time range(s). 

Proposed optimization: Pushdown of the prune logic. We'll not create a list of 
{{2 ^n^ -1}} candidates, we'll check for coverability before adding it as an 
eligible union candidate. This will bring down the number of 
{{UnionCandidates}} in the memory and preventing Full-GC. 



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


[jira] [Commented] (LENS-1443) Fallback ranges not working for virtual facts

2017-06-21 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1443:


Committed myself.

> Fallback ranges not working for virtual facts
> -
>
> Key: LENS-1443
> URL: https://issues.apache.org/jira/browse/LENS-1443
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1443.01.patch, LENS-1443.03.patch
>
>
> fallback should also take source fact name, but it's operating with fact 
> name. 



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


[jira] [Updated] (LENS-1443) Fallback ranges not working for virtual facts

2017-06-21 Thread Rajat Khandelwal (JIRA)

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

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

> Fallback ranges not working for virtual facts
> -
>
> Key: LENS-1443
> URL: https://issues.apache.org/jira/browse/LENS-1443
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1443.01.patch, LENS-1443.03.patch
>
>
> fallback should also take source fact name, but it's operating with fact 
> name. 



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


[jira] [Commented] (LENS-1443) Fallback ranges not working for virtual facts

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1443:


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

> Fallback ranges not working for virtual facts
> -
>
> Key: LENS-1443
> URL: https://issues.apache.org/jira/browse/LENS-1443
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> fallback should also take source fact name, but it's operating with fact 
> name. 



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


[jira] [Work started] (LENS-1443) Fallback ranges not working for virtual facts

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Work on LENS-1443 started by Rajat Khandelwal.
--
> Fallback ranges not working for virtual facts
> -
>
> Key: LENS-1443
> URL: https://issues.apache.org/jira/browse/LENS-1443
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> fallback should also take source fact name, but it's operating with fact 
> name. 



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


[jira] [Created] (LENS-1443) Fallback ranges not working for virtual facts

2017-06-20 Thread Rajat Khandelwal (JIRA)
Rajat Khandelwal created LENS-1443:
--

 Summary: Fallback ranges not working for virtual facts
 Key: LENS-1443
 URL: https://issues.apache.org/jira/browse/LENS-1443
 Project: Apache Lens
  Issue Type: Bug
  Components: cube
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal


fallback should also take source fact name, but it's operating with fact name. 



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


[jira] [Commented] (LENS-1442) Optimize algorithm of CandidateCoveringSetResolver

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1442:


Committed myself.

> Optimize algorithm of CandidateCoveringSetResolver
> --
>
> Key: LENS-1442
> URL: https://issues.apache.org/jira/browse/LENS-1442
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1442.01.patch
>
>
> The algorithm is {{ O(2 ^n^ ) }}. If n grows to even 30, then the query gets 
> stuck. 



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


[jira] [Updated] (LENS-1442) Optimize algorithm of CandidateCoveringSetResolver

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

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

> Optimize algorithm of CandidateCoveringSetResolver
> --
>
> Key: LENS-1442
> URL: https://issues.apache.org/jira/browse/LENS-1442
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1442.01.patch
>
>
> The algorithm is {{ O(2 ^n^ ) }}. If n grows to even 30, then the query gets 
> stuck. 



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


[jira] [Commented] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1441:


Committed myself.

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch, LENS-1441.02.patch, 
> LENS-1441.03.patch, LENS-1441.04.patch, LENS-1441.05.patch, LENS-1441.06.patch
>
>
> An optimization. 



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


[jira] [Updated] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

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

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch, LENS-1441.02.patch, 
> LENS-1441.03.patch, LENS-1441.04.patch, LENS-1441.05.patch, LENS-1441.06.patch
>
>
> An optimization. 



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


[jira] [Commented] (LENS-1442) Optimize algorithm of CandidateCoveringSetResolver

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1442:


Taking patch from reviewboard and attaching

> Optimize algorithm of CandidateCoveringSetResolver
> --
>
> Key: LENS-1442
> URL: https://issues.apache.org/jira/browse/LENS-1442
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1442.01.patch
>
>
> The algorithm is {{ O(2 ^n^ ) }}. If n grows to even 30, then the query gets 
> stuck. 



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


[jira] [Updated] (LENS-1442) Optimize algorithm of CandidateCoveringSetResolver

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1442:
---
Attachment: LENS-1442.01.patch

> Optimize algorithm of CandidateCoveringSetResolver
> --
>
> Key: LENS-1442
> URL: https://issues.apache.org/jira/browse/LENS-1442
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1442.01.patch
>
>
> The algorithm is {{ O(2 ^n^ ) }}. If n grows to even 30, then the query gets 
> stuck. 



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


[jira] [Updated] (LENS-1442) Optimize algorithm of CandidateCoveringSetResolver

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1442:
---
Status: Patch Available  (was: In Progress)

> Optimize algorithm of CandidateCoveringSetResolver
> --
>
> Key: LENS-1442
> URL: https://issues.apache.org/jira/browse/LENS-1442
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1442.01.patch
>
>
> The algorithm is {{ O(2 ^n^ ) }}. If n grows to even 30, then the query gets 
> stuck. 



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


[jira] [Commented] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1441:


Taking patch from reviewboard and attaching

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch, LENS-1441.02.patch, 
> LENS-1441.03.patch, LENS-1441.04.patch
>
>
> An optimization. 



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


[jira] [Updated] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1441:
---
Attachment: LENS-1441.04.patch

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch, LENS-1441.02.patch, 
> LENS-1441.03.patch, LENS-1441.04.patch
>
>
> An optimization. 



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


[jira] [Commented] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1441:


Taking patch from reviewboard and attaching

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch, LENS-1441.02.patch, 
> LENS-1441.03.patch
>
>
> An optimization. 



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


[jira] [Updated] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1441:
---
Attachment: LENS-1441.03.patch

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch, LENS-1441.02.patch, 
> LENS-1441.03.patch
>
>
> An optimization. 



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


[jira] [Commented] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1441:


Taking patch from reviewboard and attaching

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch, LENS-1441.02.patch
>
>
> An optimization. 



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


[jira] [Updated] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-20 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1441:
---
Attachment: LENS-1441.02.patch

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch, LENS-1441.02.patch
>
>
> An optimization. 



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


[jira] [Commented] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1441:


Taking patch from reviewboard and attaching

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch
>
>
> An optimization. 



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


[jira] [Work started] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-16 Thread Rajat Khandelwal (JIRA)

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

Work on LENS-1441 started by Rajat Khandelwal.
--
> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch
>
>
> An optimization. 



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


[jira] [Updated] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1441:
---
Attachment: LENS-1441.01.patch

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch
>
>
> An optimization. 



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


[jira] [Commented] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1441:


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

> CandidateTableResolver should not add StorageCandidate if storage is not 
> supported
> --
>
> Key: LENS-1441
> URL: https://issues.apache.org/jira/browse/LENS-1441
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1441.01.patch
>
>
> An optimization. 



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


[jira] [Created] (LENS-1441) CandidateTableResolver should not add StorageCandidate if storage is not supported

2017-06-16 Thread Rajat Khandelwal (JIRA)
Rajat Khandelwal created LENS-1441:
--

 Summary: CandidateTableResolver should not add StorageCandidate if 
storage is not supported
 Key: LENS-1441
 URL: https://issues.apache.org/jira/browse/LENS-1441
 Project: Apache Lens
  Issue Type: Bug
  Components: cube
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal


An optimization. 



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


[jira] [Updated] (LENS-1438) Testcase failure after LENS-1432

2017-06-16 Thread Rajat Khandelwal (JIRA)

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

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

> Testcase failure after LENS-1432
> 
>
> Key: LENS-1438
> URL: https://issues.apache.org/jira/browse/LENS-1438
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1438.2017-06-13_15:01:36.patch
>
>
> Test failing: org.apache.lens.server.rewrite.TestRewriting#testCubeQuery



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


[jira] [Updated] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment

2017-06-16 Thread Rajat Khandelwal (JIRA)

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

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

> Having clause getting skipped if query goes to a segmentation containing 
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1439.01.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext



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


[jira] [Commented] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment

2017-06-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1439:


Committed myself.

> Having clause getting skipped if query goes to a segmentation containing 
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1439.01.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext



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


[jira] [Commented] (LENS-1438) Testcase failure after LENS-1432

2017-06-16 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal commented on LENS-1438:


Committed myself.

> Testcase failure after LENS-1432
> 
>
> Key: LENS-1438
> URL: https://issues.apache.org/jira/browse/LENS-1438
> Project: Apache Lens
>  Issue Type: Bug
>  Components: server
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1438.2017-06-13_15:01:36.patch
>
>
> Test failing: org.apache.lens.server.rewrite.TestRewriting#testCubeQuery



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


[jira] [Updated] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment

2017-06-15 Thread Rajat Khandelwal (JIRA)

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

Rajat Khandelwal updated LENS-1439:
---
Attachment: LENS-1439.01.patch

> Having clause getting skipped if query goes to a segmentation containing 
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
>  Issue Type: Bug
>  Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1439.01.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext



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


<    1   2   3   4   5   6   7   8   9   10   >