[jira] [Closed] (LENS-1429) Queries failing intermittently with NO_REF_COL_AVAILABLE
[
https://issues.apache.org/jira/browse/LENS-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divakar Tomar closed LENS-1429.
---
verified
> Queries failing intermittently with NO_REF_COL_AVAILABLE
>
>
> Key: LENS-1429
> URL: https://issues.apache.org/jira/browse/LENS-1429
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Fix For: 2.7
>
> Attachments: LENS-1429.patch
>
>
> Have seen queries failing intermittently with below error.
> {CODE}
> 16 May 2017 11:59:39 [5af8e7ad-b9d7-44db-abdf-d8a28bdb9f3c]
> [f38a238e-abcb-4168-a052-7114cee1c3a6 estimate-128] WARN
> org.apache.lens.server.rewrite.RewriteUtil - Driver : hive/prod Skipped for
> the query rewriting due to
> org.apache.lens.server.api.error.LensException:
> NO_REF_COL_AVAILABLE[my_ref_col]
> at
> org.apache.lens.cube.parse.DenormalizationResolver$DenormalizationContext.pickColumnsForTable(DenormalizationResolver.java:227)
> ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
> org.apache.lens.cube.parse.DenormalizationResolver$DenormalizationContext.rewriteDenormctx(DenormalizationResolver.java:150)
> ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
> org.apache.lens.cube.parse.DimHQLContext.addDenormDims(DimHQLContext.java:119)
> ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
> org.apache.lens.cube.parse.MultiCandidateQueryWriterContext.addDenormDims(MultiCandidateQueryWriterContext.java:56)
> ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
> org.apache.lens.cube.parse.CubeQueryContext.getQueryWriter(CubeQueryContext.java:927)
> ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
> org.apache.lens.cube.parse.CubeQueryContext.toHQL(CubeQueryContext.java:947)
> ~[lens-cube-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
> org.apache.lens.server.rewrite.RewriteUtil$DriverRewriterRunnable.run(RewriteUtil.java:396)
> ~[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]
> {CODE}
--
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
[
https://issues.apache.org/jira/browse/LENS-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128709#comment-16128709
]
Hudson commented on LENS-1459:
--
FAILURE: Integrated in Jenkins build Lens-Commit #1433 (See
[https://builds.apache.org/job/Lens-Commit/1433/])
LENS-1459: Time union candidate creation phase is creating a combination
(rajatgupta59: rev e6f1ce0e2927d84a9cd2800f7630305114af1bb4)
* (edit)
lens-cube/src/main/java/org/apache/lens/cube/parse/CandidateCoveringSetsResolver.java
> 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
[
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
[
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] [Closed] (LENS-1430) Expressions are not getting resolved correctly in union query
[
https://issues.apache.org/jira/browse/LENS-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divakar Tomar closed LENS-1430.
---
verified
> Expressions are not getting resolved correctly in union query
> -
>
> Key: LENS-1430
> URL: https://issues.apache.org/jira/browse/LENS-1430
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Fix For: 2.7
>
> Attachments: LENS-1430_1.patch, LENS-1430.patch
>
>
> Expressions are not getting resolved correctly for the below case
> {CODE}
> case when expr1 = 0 then 0 else expr2 * 100 / expr1 end
> {CODE}
> expr1 is answerable by Candidate1 and Candidate2
> expr2 is answerable by Candidate1
--
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
[
https://issues.apache.org/jira/browse/LENS-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128654#comment-16128654
]
Hadoop QA commented on LENS-1459:
-
Applied patch:
[LENS-1459.2017-08-16_16:28:29.patch|https://issues.apache.org/jira/secure/attachment/12882117/LENS-1459.2017-08-16_16%3A28%3A29.patch]
and ran command: mvn clean install -fae. Result: Success. Build Job:
https://builds.apache.org/job/PreCommit-Lens-Build/1382/
> 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
[
https://issues.apache.org/jira/browse/LENS-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128641#comment-16128641
]
Amareshwari Sriramadasu commented on LENS-1459:
---
+1
> 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
[
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
[
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
[
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
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] [Commented] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment
[
https://issues.apache.org/jira/browse/LENS-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128596#comment-16128596
]
Hadoop QA commented on LENS-1439:
-
Applied patch:
[LENS-1439.01.patch|https://issues.apache.org/jira/secure/attachment/12882104/LENS-1439.01.patch]
and ran command: mvn clean install -fae. Result: Success. Build Job:
https://builds.apache.org/job/PreCommit-Lens-Build/1381/
> 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] [Closed] (LENS-1433) Virtual Fact over a fact with single storage - multi update period is writing wrong query
[
https://issues.apache.org/jira/browse/LENS-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divakar Tomar closed LENS-1433.
---
verified
> Virtual Fact over a fact with single storage - multi update period is writing
> wrong query
> -
>
> Key: LENS-1433
> URL: https://issues.apache.org/jira/browse/LENS-1433
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajitha R
> Fix For: 2.7
>
> Attachments: LENS-1433.patch
>
>
> it's rewriting {{from storage_virtualfact}} whereas it should be {{from
> storage_fact}}
--
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
[
https://issues.apache.org/jira/browse/LENS-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128569#comment-16128569
]
Amareshwari Sriramadasu commented on LENS-1439:
---
[~prongs] Can we add unit test?
> 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
[
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
[
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
[
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
[
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
[
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)
Review Request 61683: LENS-1439: Having clause getting skipped if query goes to a segmentation containing single segment
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61683/
---
Review request for lens.
Bugs: LENS-1439
https://issues.apache.org/jira/browse/LENS-1439
Repository: lens
Description
---
The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
Diffs
-
lens-cube/src/main/java/org/apache/lens/cube/parse/StorageCandidateHQLContext.java
494b08e3b04bcdfea3de449f3740589cc481ba38
Diff: https://reviews.apache.org/r/61683/diff/1/
Testing
---
Thanks,
Rajat Khandelwal
[jira] [Reopened] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment
[
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] [Issue Comment Deleted] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment
[
https://issues.apache.org/jira/browse/LENS-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divakar Tomar updated LENS-1439:
Comment: was deleted
(was: verified
)
> 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)
