[jira] [Closed] (LENS-1419) UnionCandidates getting pruned when only dim attributes projected
[ https://issues.apache.org/jira/browse/LENS-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divakar Tomar closed LENS-1419. --- > UnionCandidates getting pruned when only dim attributes projected > - > > Key: LENS-1419 > URL: https://issues.apache.org/jira/browse/LENS-1419 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Sushil Mohanty >Assignee: Sushil Mohanty > Fix For: 2.7 > > Attachments: LENS-1419.patch > > > In current code there is a bug which prunes all UnionCandidates when only dim > attributes selected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1462) Query with same dim attribute twice referring to join chain ending with putting that field twice in GROUP BY clause
[ https://issues.apache.org/jira/browse/LENS-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divakar Tomar updated LENS-1462: Summary: Query with same dim attribute twice referring to join chain ending with putting that field twice in GROUP BY clause (was: Query with same dim attribute twice referring to join chain ending with putting that field only once) > Query with same dim attribute twice referring to join chain ending with > putting that field twice in GROUP BY clause > --- > > Key: LENS-1462 > URL: https://issues.apache.org/jira/browse/LENS-1462 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Divakar Tomar >Assignee: Sushil Mohanty > > When same column appears twice in the query , it comes only once in the > rewritten query (when segmentation is the selected candidate) while appears > twice in GROUP BY clause. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1462) Query with same dim attribute twice referring to join chain ending with putting that field only once
[ https://issues.apache.org/jira/browse/LENS-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divakar Tomar updated LENS-1462: Description: When same column appears twice in the query , it comes only once in the rewritten query (when segmentation is the selected candidate) while appears twice in GROUP BY clause. (was: When same column appears twice in the query , it comes only once in the rewritten query (when segmentation is the selected candidate).) > Query with same dim attribute twice referring to join chain ending with > putting that field only once > > > Key: LENS-1462 > URL: https://issues.apache.org/jira/browse/LENS-1462 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Divakar Tomar >Assignee: Sushil Mohanty > > When same column appears twice in the query , it comes only once in the > rewritten query (when segmentation is the selected candidate) while appears > twice in GROUP BY clause. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1403) Measures getting repeated in inner select of union query
[ https://issues.apache.org/jira/browse/LENS-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divakar Tomar closed LENS-1403. --- verified > Measures getting repeated in inner select of union query > > > Key: LENS-1403 > URL: https://issues.apache.org/jira/browse/LENS-1403 > Project: Apache Lens > Issue Type: Sub-task > Components: cube >Reporter: Sushil Mohanty >Assignee: Sushil Mohanty > Fix For: 2.7 > > Attachments: LENS-1403_2.patch > > > Measure columns are getting repeated if its queried multiple times in the > same query eg: same measure can be part of select and having clause. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1264) Group by promotion not happening with aggregate dim attributes
[
https://issues.apache.org/jira/browse/LENS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divakar Tomar closed LENS-1264.
---
verified
> Group by promotion not happening with aggregate dim attributes
> ---
>
> Key: LENS-1264
> URL: https://issues.apache.org/jira/browse/LENS-1264
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Sushil Mohanty
>Assignee: Sushil Mohanty
> Fix For: 2.7
>
> Attachments: LENS-1264.patch
>
>
> {CODE}
>
>
>
> cube query :
> query execute cube select country,distinct_users from testcube where
> time_range_in(time_col,'2016-07-31-00','2016-07-31-01')
> rewritten query :
> SELECT distinct (testcube.country), count(distinct (testcube.user)) FROM
> db.fact_table testcube WHERE (((testcube.dt) in ('2016-07-31-00')))
> {CODE}
> Query fails with the following:
> Error Message: Line 1:226 Not yet supported place for UDAF 'count'
> Column testcube.country should be part of group by as there is already
> aggregate column used in select.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Issue Comment Deleted] (LENS-1420) Bug fixes in cube segmentation final rewritten query
[ https://issues.apache.org/jira/browse/LENS-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divakar Tomar updated LENS-1420: Comment: was deleted (was: verified ) > Bug fixes in cube segmentation final rewritten query > - > > Key: LENS-1420 > URL: https://issues.apache.org/jira/browse/LENS-1420 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Sushil Mohanty >Assignee: Sushil Mohanty > Fix For: 2.7 > > Attachments: LENS-1420_1.patch > > > Found the below issues in fact-to-fact union and cube segmentation rewritten > query. > 1. Expressions used in having clause are not resolved in the final rewritten > query incase of picked candidate is a segmentation. > 2. Alias is not being replaced in order by clause for segmentation queries. > 3. Query with two dim attributes referring to same join chain ending with > wrong alias replacement. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1420) Bug fixes in cube segmentation final rewritten query
[ https://issues.apache.org/jira/browse/LENS-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divakar Tomar closed LENS-1420. --- verified > Bug fixes in cube segmentation final rewritten query > - > > Key: LENS-1420 > URL: https://issues.apache.org/jira/browse/LENS-1420 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Sushil Mohanty >Assignee: Sushil Mohanty > Fix For: 2.7 > > Attachments: LENS-1420_1.patch > > > Found the below issues in fact-to-fact union and cube segmentation rewritten > query. > 1. Expressions used in having clause are not resolved in the final rewritten > query incase of picked candidate is a segmentation. > 2. Alias is not being replaced in order by clause for segmentation queries. > 3. Query with two dim attributes referring to same join chain ending with > wrong alias replacement. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (LENS-1420) Bug fixes in cube segmentation final rewritten query
[ https://issues.apache.org/jira/browse/LENS-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133013#comment-16133013 ] Divakar Tomar edited comment on LENS-1420 at 8/21/17 10:41 AM: --- case 3 still persists. When same column appears twice in the query , it comes only once in the rewritten query (when segmentation is the selected candidate) and appears twice in group by clause. all other cases are verified. was (Author: divakar_tomar): case 3 still persists. When same column appears twice in the query , it comes only once in the rewritten query (when segmentation is the selected candidate). > Bug fixes in cube segmentation final rewritten query > - > > Key: LENS-1420 > URL: https://issues.apache.org/jira/browse/LENS-1420 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Sushil Mohanty >Assignee: Sushil Mohanty > Fix For: 2.7 > > Attachments: LENS-1420_1.patch > > > Found the below issues in fact-to-fact union and cube segmentation rewritten > query. > 1. Expressions used in having clause are not resolved in the final rewritten > query incase of picked candidate is a segmentation. > 2. Alias is not being replaced in order by clause for segmentation queries. > 3. Query with two dim attributes referring to same join chain ending with > wrong alias replacement. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1386) Add support for separate tables for update periods in one storage
[ https://issues.apache.org/jira/browse/LENS-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana H closed LENS-1386. --- > Add support for separate tables for update periods in one storage > - > > Key: LENS-1386 > URL: https://issues.apache.org/jira/browse/LENS-1386 > Project: Apache Lens > Issue Type: Task > Components: api, cube, server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > Attachments: LENS-1386.patch > > > Xsd and Metastore changes: > (1) New Xsd construct > (2) Create Fact Changes > (3) CubeMetastoreClient changes for update period table name > (4) Validation that TableDescription should only be available at either table > level or at update period level -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1340) Adding API for data completeness checker
[ https://issues.apache.org/jira/browse/LENS-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana H closed LENS-1340. --- > Adding API for data completeness checker > > > Key: LENS-1340 > URL: https://issues.apache.org/jira/browse/LENS-1340 > Project: Apache Lens > Issue Type: Sub-task > Components: cube >Reporter: Narayan Periwal >Assignee: Narayan Periwal > Fix For: 2.7 > > Attachments: LENS-1340.patch, LENS-1340-v2.patch > > > The data completeness API will take the factTag, startDate, endDate and > measure's list as input. > It will return the completeness percentage for each of the measures for the > given factTag and time range. -- 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=16134995#comment-16134995
]
Hadoop QA commented on LENS-1439:
-
Applied patch:
[LENS-1439.02.patch|https://issues.apache.org/jira/secure/attachment/12882835/LENS-1439.02.patch]
and ran command: mvn clean install -fae. Result: Success. Build Job:
https://builds.apache.org/job/PreCommit-Lens-Build/1384/
> 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,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (LENS-1392) Fix failing TestCases in org.apache.lens.server.query.QueryAPIErrorResponseTest
[ https://issues.apache.org/jira/browse/LENS-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana H closed LENS-1392. --- > Fix failing TestCases in > org.apache.lens.server.query.QueryAPIErrorResponseTest > > > Key: LENS-1392 > URL: https://issues.apache.org/jira/browse/LENS-1392 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.7 > > Attachments: lens-1392.patch > > > Failed tests: > QueryAPIErrorResponseTest.testQueryColumnWithBothStartDateAndEndDate:209->testColUnAvailableInTimeRange:297 > expected [dimfield8d6e29df822945c49ea03d3533806cca can only be queried after > Thursday, January 1, 2015 12:00:00 AM UTC and before Friday, January 30, 2015 > 11:00:00 PM UTC. Please adjust the selected time range accordingly.] but > found [No fact table has the queried columns : > [dimfield8d6e29df822945c49ea03d3533806cca]] > QueryAPIErrorResponseTest.testQueryColumnWithBothStartDateAndEndDate:209->testColUnAvailableInTimeRange:297 > expected [dimfield16cc374b445443a6ae8fce39fad190d1 can only be queried after > Thursday, January 1, 2015 12:00:00 AM UTC and before Friday, January 30, 2015 > 11:00:00 PM UTC. Please adjust the selected time range accordingly.] but > found [No fact table has the queried columns : > [dimfield16cc374b445443a6ae8fce39fad190d1]] > QueryAPIErrorResponseTest.testQueryColumnWithOnlyEndDate:245->testColUnAvailableInTimeRange:297 > expected [dimfieldc7f0b34c257d4fde80dacaaf0d61d600 can only be queried > before Friday, January 30, 2015 11:00:00 PM UTC. Please adjust the selected > time range accordingly.] but found [No fact table has the queried columns : > [dimfieldc7f0b34c257d4fde80dacaaf0d61d600]] > QueryAPIErrorResponseTest.testQueryColumnWithOnlyEndDate:245->testColUnAvailableInTimeRange:297 > expected [dimfield3931859c8fdf47a49beaadba222915d6 can only be queried > before Friday, January 30, 2015 11:00:00 PM UTC. Please adjust the selected > time range accordingly.] but found [No fact table has the queried columns : > [dimfield3931859c8fdf47a49beaadba222915d6]] > QueryAPIErrorResponseTest.testQueryColumnWithOnlyStartDate:227->testColUnAvailableInTimeRange:297 > expected [dimfield4b536214dcf0413e9bd7190d9efa139b can only be queried after > Thursday, January 1, 2015 12:00:00 AM UTC. Please adjust the selected time > range accordingly.] but found [No fact table has the queried columns : > [dimfield4b536214dcf0413e9bd7190d9efa139b]] > QueryAPIErrorResponseTest.testQueryColumnWithOnlyStartDate:227->testColUnAvailableInTimeRange:297 > expected [dimfield85771da365a44789a42fd8f800fbbe50 can only be queried after > Thursday, January 1, 2015 12:00:00 AM UTC. Please adjust the selected time > range accordingly.] but found [No fact table has the queried columns : > [dimfield85771da365a44789a42fd8f800fbbe50]] > Tests run: 321, Failures: 6, Errors: 0, Skipped: 18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1304) Log Driver query in lens finished_queries table as well
[ https://issues.apache.org/jira/browse/LENS-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana H closed LENS-1304. --- > Log Driver query in lens finished_queries table as well > --- > > Key: LENS-1304 > URL: https://issues.apache.org/jira/browse/LENS-1304 > Project: Apache Lens > Issue Type: Task > Components: server >Reporter: Raghavendra Singh >Assignee: Raghavendra Singh > Labels: incompatible > Fix For: 2.7 > > Attachments: LENS-1304.05.patch > > > Make driver query available in the finished_queries stats for deeper analytics -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1405) Xsd for virtual fact
[ https://issues.apache.org/jira/browse/LENS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana H closed LENS-1405. --- > Xsd for virtual fact > > > Key: LENS-1405 > URL: https://issues.apache.org/jira/browse/LENS-1405 > Project: Apache Lens > Issue Type: Sub-task > Components: cube >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.7 > > Attachments: lens_latest.patch, Lens-patch > > > To define a xsd for virtual fact. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1319) Lens Client doesn't provide the option to pass query conf while submitting the query
[ https://issues.apache.org/jira/browse/LENS-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana H closed LENS-1319. --- > Lens Client doesn't provide the option to pass query conf while submitting > the query > > > Key: LENS-1319 > URL: https://issues.apache.org/jira/browse/LENS-1319 > Project: Apache Lens > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Srikanth Sundarrajan >Assignee: Srikanth Sundarrajan > Fix For: 2.7 > > Attachments: LENS-1319.patch > > > Lens Client doesn't provide the option to pass query conf while submitting > the query. Lens Server however allow the conf to posted as a form param along > with other parameters. Lens Client need to be extended to pass the LensConf > along. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-974) Add cube-segmentation for base cube
[ https://issues.apache.org/jira/browse/LENS-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana H closed LENS-974. -- > Add cube-segmentation for base cube > --- > > Key: LENS-974 > URL: https://issues.apache.org/jira/browse/LENS-974 > Project: Apache Lens > Issue Type: New Feature > Components: cube >Reporter: Sushil Mohanty >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: e1f17d45.png, LENS-974.17.patch, LENS-974.18.patch, > LENS-974.20.patch, LENS-974.21.patch, LENS-974.22.patch, LENS-974.23.patch, > LENS-974.24.patch, LENS-974.25.patch > > > With cube segmentation a cube can have multiple cubes and all these child > cubes together will make the cube complete. > CubeSegmentation and CubeFactTable will sit together, which means it can > belong to only one base cube. A base cube can have one or more cube > segmentations. Fields of segmentation will be intersection of all columns of > its cubes. Segmentation will have weight to compare with its buddies (facts > or other segmentations). Also it can have start and end time defined or it > can derive from its underline facts. > eg: > base_cube > |_fact1 > |_fact2 > |_cube_segment1 > |_cube1 > |_fact_11 > |_fact_12 > ... > ... > |_cube_segment2 > |_cube2 > |_fact_21 > |_fact_22 > ... > ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1381) Support Fact to Fact Union
[ https://issues.apache.org/jira/browse/LENS-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana H closed LENS-1381. --- > Support Fact to Fact Union > -- > > Key: LENS-1381 > URL: https://issues.apache.org/jira/browse/LENS-1381 > Project: Apache Lens > Issue Type: New Feature >Reporter: Puneet Gupta >Assignee: Sushil Mohanty > Fix For: 2.7 > > Attachments: LENS-1381_4.patch, LENS-1381_checkstyle_fix_1.patch, > LENS-1381_checkstyle_fix.patch > > > Currently Lens supports Union-ing data across different storages in a single > Fact. With this JIRA Lens server will be able to Union Data Across Facts too. -- 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=16134956#comment-16134956
]
Rajat Khandelwal commented on LENS-1439:
[~amareshwari] Added in latest 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,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (LENS-1380) Revamp testcase division
[ https://issues.apache.org/jira/browse/LENS-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana H closed LENS-1380. --- > Revamp testcase division > > > Key: LENS-1380 > URL: https://issues.apache.org/jira/browse/LENS-1380 > Project: Apache Lens > Issue Type: Task > Components: regression >Reporter: Archana H >Assignee: Archana H > Fix For: 2.7 > > Attachments: LENS-1380.patch > > > Currently multiple testcases are clubbed in the same class file. Separating > them to feature wise test class files. Also renaming few test class names to > have "IT" in the beginning. -- 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=16134919#comment-16134919
]
Hadoop QA commented on LENS-1439:
-
Applied patch:
[LENS-1439.02.patch|https://issues.apache.org/jira/secure/attachment/12882835/LENS-1439.02.patch]
and ran command: mvn clean install -fae. Result: Failure. Build Job:
https://builds.apache.org/job/PreCommit-Lens-Build/1383/
> 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,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (LENS-1289) Fact column start_time and end_time not getting reflected with update fact command
[ https://issues.apache.org/jira/browse/LENS-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divakar Tomar closed LENS-1289. --- > Fact column start_time and end_time not getting reflected with update fact > command > -- > > Key: LENS-1289 > URL: https://issues.apache.org/jira/browse/LENS-1289 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Sushil Mohanty >Assignee: Sushil Mohanty > Fix For: 2.7 > > Attachments: LENS-1289.patch > > > As part of LENS-197 we have added start and end time support for fact > columns, which works for create fact table. We need to support the same for > update fact as well. -- 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.02.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,
> LENS-1439.02.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=16134863#comment-16134863
]
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,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Re: 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/
---
(Updated Aug. 21, 2017, 1:53 p.m.)
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 (updated)
-
lens-cube/src/main/java/org/apache/lens/cube/parse/StorageCandidateHQLContext.java
494b08e3b04bcdfea3de449f3740589cc481ba38
lens-cube/src/test/java/org/apache/lens/cube/parse/TestCubeSegmentationRewriter.java
7e1714bc301a748bf2c49dc9a707c1072c36f66b
lens-cube/src/test/resources/schema/cubes/derived/union_join_ctx_der1.xml
c23a029b80ab4342e130d4778eb84559c6806b7e
Diff: https://reviews.apache.org/r/61683/diff/2/
Changes: https://reviews.apache.org/r/61683/diff/1-2/
Testing
---
Thanks,
Rajat Khandelwal
[jira] [Closed] (LENS-197) Allow start and end times for columns in fact tables
[ https://issues.apache.org/jira/browse/LENS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divakar Tomar closed LENS-197. -- verified > Allow start and end times for columns in fact tables > > > Key: LENS-197 > URL: https://issues.apache.org/jira/browse/LENS-197 > Project: Apache Lens > Issue Type: Improvement > Components: cube >Reporter: Amareshwari Sriramadasu >Assignee: Sushil Mohanty > Fix For: 2.7 > > Attachments: LENS-197-2.patch > > > We can have columns being promoted/demoted from one aggregate fact to other, > with usage of columns in reports. > We need this for the following use cases: > # If field is moved to a lower cost fact: Since the fact is having lower cost > it will be picked up for processing, but if the life of column queried does > not fit in the range queried, a higher level fact should be picked up. If > lower level fact is picked, it would lead to wrong results. > # If field is moved to a higher cost fact, i.e. its life ending in a lower > cost fact. Again, depending on the range queried, either lower or higher > level fact should be picked up. It will be more like optimization for this > case. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
