[jira] [Commented] (LENS-1009) Queries with large sql are not getting purged
[ https://issues.apache.org/jira/browse/LENS-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017727#comment-17017727 ] Puneet Gupta commented on LENS-1009: Don't think this has been fixed. Use the workaround mentioned by [~amareshwari] and alter the database table directly. > Queries with large sql are not getting purged > - > > Key: LENS-1009 > URL: https://issues.apache.org/jira/browse/LENS-1009 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Priority: Major > > Lens creates finished_queries table with column userquery as varchar(1). > If a query is larger than that, while purging it throws an exception > regarding data truncation. After that, there are retries for purging and it > keeps on retrying. After some time the logs get cluttered since purge > failure logs are everywhere. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (LENS-1506) Kerberos authentication in lens
[ https://issues.apache.org/jira/browse/LENS-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1506: --- Fix Version/s: 2.8 > Kerberos authentication in lens > --- > > Key: LENS-1506 > URL: https://issues.apache.org/jira/browse/LENS-1506 > Project: Apache Lens > Issue Type: Improvement > Components: client, driver-hive, python-client, server >Reporter: Ankit Kailaswar >Assignee: Ankit Kailaswar >Priority: Major > Fix For: 2.8 > > Attachments: Lens-1506.1.patch, Lens-1506.2.patch, Lens-1506.3.patch, > Lens-1506.4.patch, Lens-1506_patch, design3.png > > > Current Lens implementation is broken when we try to enable kerberos > authentication in lens as mentioned at > [https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2] in > following ways, > 1. openSession REST API fails to create new session for user. Currently it > supports only passwd types of authentication. > 2. If the underlying hive driver is running with kerberos authentication then > driver initialization flow to obtain hive transport for hive driver in lens > errors out. Hive server accepts only sasl messages but lens continues using > PLAINSASL. > 3. If hadoop cluster has kerberos authentication enabled then all hdfs calls > (persisting services, all hdfs path in conf etc) fail. > 4. Lens as if now doesnt supports refreshing KDC token before it expires. > Changes required in lens to fully support kerberose authentication are as > follows, > # lens's hive driver must use SASL for all communication in to kerberozied > hive. Current thrift client for hive doesn't support this functionality. > # Lens must refresh KDC ticket before it expires. > # All clients must be authenticated with kerberose authentication before > session creation. > # In kerberos mode all hive driver query should be executed with single > cluster user as "lens". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LENS-1506) Kerberos authentication in lens
[ https://issues.apache.org/jira/browse/LENS-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426805#comment-16426805 ] Puneet Gupta commented on LENS-1506: Committed. Thanks [~ankitkailaswar] > Kerberos authentication in lens > --- > > Key: LENS-1506 > URL: https://issues.apache.org/jira/browse/LENS-1506 > Project: Apache Lens > Issue Type: Improvement > Components: client, driver-hive, python-client, server >Reporter: Ankit Kailaswar >Assignee: Ankit Kailaswar >Priority: Major > Fix For: 2.8 > > Attachments: Lens-1506.1.patch, Lens-1506.2.patch, Lens-1506.3.patch, > Lens-1506.4.patch, Lens-1506_patch, design3.png > > > Current Lens implementation is broken when we try to enable kerberos > authentication in lens as mentioned at > [https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2] in > following ways, > 1. openSession REST API fails to create new session for user. Currently it > supports only passwd types of authentication. > 2. If the underlying hive driver is running with kerberos authentication then > driver initialization flow to obtain hive transport for hive driver in lens > errors out. Hive server accepts only sasl messages but lens continues using > PLAINSASL. > 3. If hadoop cluster has kerberos authentication enabled then all hdfs calls > (persisting services, all hdfs path in conf etc) fail. > 4. Lens as if now doesnt supports refreshing KDC token before it expires. > Changes required in lens to fully support kerberose authentication are as > follows, > # lens's hive driver must use SASL for all communication in to kerberozied > hive. Current thrift client for hive doesn't support this functionality. > # Lens must refresh KDC ticket before it expires. > # All clients must be authenticated with kerberose authentication before > session creation. > # In kerberos mode all hive driver query should be executed with single > cluster user as "lens". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LENS-1506) Kerberos authentication in lens
[ https://issues.apache.org/jira/browse/LENS-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400337#comment-16400337 ] Puneet Gupta commented on LENS-1506: [~ankitkailaswar] This review request covers all the changes 1- 4 ? > Kerberos authentication in lens > --- > > Key: LENS-1506 > URL: https://issues.apache.org/jira/browse/LENS-1506 > Project: Apache Lens > Issue Type: Improvement > Components: client, driver-hive, python-client, server >Reporter: Ankit Kailaswar >Assignee: Ankit Kailaswar >Priority: Major > Attachments: design3.png > > > Current Lens implementation is broken when we try to enable kerberos > authentication in lens as mentioned at > [https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2] in > following ways, > 1. openSession REST API fails to create new session for user. Currently it > supports only passwd types of authentication. > 2. If the underlying hive driver is running with kerberos authentication then > driver initialization flow to obtain hive transport for hive driver in lens > errors out. Hive server accepts only sasl messages but lens continues using > PLAINSASL. > 3. If hadoop cluster has kerberos authentication enabled then all hdfs calls > (persisting services, all hdfs path in conf etc) fail. > 4. Lens as if now doesnt supports refreshing KDC token before it expires. > Changes required in lens to fully support kerberose authentication are as > follows, > # lens's hive driver must use SASL for all communication in to kerberozied > hive. Current thrift client for hive doesn't support this functionality. > # Lens must refresh KDC ticket before it expires. > # All clients must be authenticated with kerberose authentication before > session creation. > # In kerberos mode all hive driver query should be executed with single > cluster user as "lens". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LENS-1497) NPE while closing idle connections
[
https://issues.apache.org/jira/browse/LENS-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335458#comment-16335458
]
Puneet Gupta commented on LENS-1497:
Committed. Thanks [~rajitha.r]
> NPE while closing idle connections
> ---
>
> Key: LENS-1497
> URL: https://issues.apache.org/jira/browse/LENS-1497
> Project: Apache Lens
> Issue Type: Bug
> Components: server
>Reporter: Rajitha R
>Assignee: Rajitha R
>Priority: Major
> Fix For: 2.8
>
> Attachments: LENS-1497.patch
>
>
> {code}
> 21 Dec 2017 15:25:59 [e88aa05a-c454-44c1-8e52-e7bd741a5df6]
> [pool-16-thread-1] WARN org.apache.lens.server.session.HiveSessionService -
> Unknown error while checking for inactive sessions -
> java.lang.NullPointerException: null
> at
> org.apache.lens.server.BaseLensService.decrementSessionCountForUser(BaseLensService.java:343)
> ~[classes/:na]
> at
> org.apache.lens.server.BaseLensService.closeSession(BaseLensService.java:321)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService.closeInternal(HiveSessionService.java:497)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService.access$300(HiveSessionService.java:59)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService$SessionExpiryRunnable.runInternal(HiveSessionService.java:547)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService$SessionExpiryRunnable.run(HiveSessionService.java:569)
> ~[classes/:na]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_131]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_131]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_131]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sche
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (LENS-1497) NPE while closing idle connections
[
https://issues.apache.org/jira/browse/LENS-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Puneet Gupta updated LENS-1497:
---
Fix Version/s: 2.8
> NPE while closing idle connections
> ---
>
> Key: LENS-1497
> URL: https://issues.apache.org/jira/browse/LENS-1497
> Project: Apache Lens
> Issue Type: Bug
> Components: server
>Reporter: Rajitha R
>Assignee: Rajitha R
>Priority: Major
> Fix For: 2.8
>
> Attachments: LENS-1497.patch
>
>
> {code}
> 21 Dec 2017 15:25:59 [e88aa05a-c454-44c1-8e52-e7bd741a5df6]
> [pool-16-thread-1] WARN org.apache.lens.server.session.HiveSessionService -
> Unknown error while checking for inactive sessions -
> java.lang.NullPointerException: null
> at
> org.apache.lens.server.BaseLensService.decrementSessionCountForUser(BaseLensService.java:343)
> ~[classes/:na]
> at
> org.apache.lens.server.BaseLensService.closeSession(BaseLensService.java:321)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService.closeInternal(HiveSessionService.java:497)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService.access$300(HiveSessionService.java:59)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService$SessionExpiryRunnable.runInternal(HiveSessionService.java:547)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService$SessionExpiryRunnable.run(HiveSessionService.java:569)
> ~[classes/:na]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_131]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_131]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_131]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sche
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (LENS-1497) NPE while closing idle connections
[
https://issues.apache.org/jira/browse/LENS-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Puneet Gupta updated LENS-1497:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> NPE while closing idle connections
> ---
>
> Key: LENS-1497
> URL: https://issues.apache.org/jira/browse/LENS-1497
> Project: Apache Lens
> Issue Type: Bug
> Components: server
>Reporter: Rajitha R
>Assignee: Rajitha R
>Priority: Major
> Fix For: 2.8
>
> Attachments: LENS-1497.patch
>
>
> {code}
> 21 Dec 2017 15:25:59 [e88aa05a-c454-44c1-8e52-e7bd741a5df6]
> [pool-16-thread-1] WARN org.apache.lens.server.session.HiveSessionService -
> Unknown error while checking for inactive sessions -
> java.lang.NullPointerException: null
> at
> org.apache.lens.server.BaseLensService.decrementSessionCountForUser(BaseLensService.java:343)
> ~[classes/:na]
> at
> org.apache.lens.server.BaseLensService.closeSession(BaseLensService.java:321)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService.closeInternal(HiveSessionService.java:497)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService.access$300(HiveSessionService.java:59)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService$SessionExpiryRunnable.runInternal(HiveSessionService.java:547)
> ~[classes/:na]
> at
> org.apache.lens.server.session.HiveSessionService$SessionExpiryRunnable.run(HiveSessionService.java:569)
> ~[classes/:na]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_131]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_131]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_131]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sche
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (LENS-1500) Test cases failing in master
[
https://issues.apache.org/jira/browse/LENS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Puneet Gupta updated LENS-1500:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Test cases failing in master
> -
>
> Key: LENS-1500
> URL: https://issues.apache.org/jira/browse/LENS-1500
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajitha R
>Assignee: Rajitha R
>Priority: Major
> Fix For: 2.8
>
> Attachments: LENS-1500.patch
>
>
> Latest master code has some of the test cases failing as follows. This seems
> to happen as we entered new year and month. Needs to be investigated
> {code}
> Failed tests:
>
> TestUnionQueries.testDimAttrExpressionQuery:218->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testNonAggregateOverAggregateFunction:290->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testSingleFactMultiStorage:342->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testSingleFactSingleStorageWithMultipleTableDescriptions:390->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testUnionQueries:89->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (LENS-1500) Test cases failing in master
[
https://issues.apache.org/jira/browse/LENS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Puneet Gupta updated LENS-1500:
---
Fix Version/s: 2.8
> Test cases failing in master
> -
>
> Key: LENS-1500
> URL: https://issues.apache.org/jira/browse/LENS-1500
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajitha R
>Assignee: Rajitha R
>Priority: Major
> Fix For: 2.8
>
> Attachments: LENS-1500.patch
>
>
> Latest master code has some of the test cases failing as follows. This seems
> to happen as we entered new year and month. Needs to be investigated
> {code}
> Failed tests:
>
> TestUnionQueries.testDimAttrExpressionQuery:218->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testNonAggregateOverAggregateFunction:290->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testSingleFactMultiStorage:342->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testSingleFactSingleStorageWithMultipleTableDescriptions:390->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testUnionQueries:89->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (LENS-1500) Test cases failing in master
[
https://issues.apache.org/jira/browse/LENS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335453#comment-16335453
]
Puneet Gupta commented on LENS-1500:
Committed. Thanks [~rajitha.r]
> Test cases failing in master
> -
>
> Key: LENS-1500
> URL: https://issues.apache.org/jira/browse/LENS-1500
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajitha R
>Assignee: Rajitha R
>Priority: Major
> Fix For: 2.8
>
> Attachments: LENS-1500.patch
>
>
> Latest master code has some of the test cases failing as follows. This seems
> to happen as we entered new year and month. Needs to be investigated
> {code}
> Failed tests:
>
> TestUnionQueries.testDimAttrExpressionQuery:218->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testNonAggregateOverAggregateFunction:290->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testSingleFactMultiStorage:342->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testSingleFactSingleStorageWithMultipleTableDescriptions:390->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
>
> TestUnionQueries.testUnionQueries:89->TestQueryRewrite.rewrite:89->TestQueryRewrite.rewriteCtx:98
> » Lens
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (LENS-1495) Lens commit build failure due to checkstyle error
[ https://issues.apache.org/jira/browse/LENS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299889#comment-16299889 ] Puneet Gupta commented on LENS-1495: Committed. Thanks [~rajitha.r] > Lens commit build failure due to checkstyle error > - > > Key: LENS-1495 > URL: https://issues.apache.org/jira/browse/LENS-1495 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1495.patch > > > Checkstyle error in Lensserver code needs to be fixed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1495) Lens commit build failure due to checkstyle error
[ https://issues.apache.org/jira/browse/LENS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1495: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Lens commit build failure due to checkstyle error > - > > Key: LENS-1495 > URL: https://issues.apache.org/jira/browse/LENS-1495 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1495.patch > > > Checkstyle error in Lensserver code needs to be fixed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1495) Lens commit build failure due to checkstyle error
[ https://issues.apache.org/jira/browse/LENS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1495: --- Fix Version/s: 2.8 > Lens commit build failure due to checkstyle error > - > > Key: LENS-1495 > URL: https://issues.apache.org/jira/browse/LENS-1495 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1495.patch > > > Checkstyle error in Lensserver code needs to be fixed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1493) TotalQueryCost logic broken
[ https://issues.apache.org/jira/browse/LENS-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296652#comment-16296652 ] Puneet Gupta commented on LENS-1493: Committed. Thanks [~rajitha.r] > TotalQueryCost logic broken > > > Key: LENS-1493 > URL: https://issues.apache.org/jira/browse/LENS-1493 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1493.patch > > > The totalQueryCost method in DefaultEstimatedQueryCollection is throwing > following error : > Error in query submitter > java.lang.ClassCastException: > org.apache.lens.server.api.query.cost.FactPartitionBasedQueryCost cannot be > cast to org.apache.lens.server.api.query.cost.StaticQueryCost > at > org.apache.lens.server.api.query.cost.StaticQueryCost.add(StaticQueryCost.java:33) > > at > org.apache.lens.server.query.collect.DefaultEstimatedQueryCollection.getTotalQueryCost(DefaultEstimatedQueryCollection.java:171) > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1493) TotalQueryCost logic broken
[ https://issues.apache.org/jira/browse/LENS-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1493: --- Resolution: Fixed Status: Resolved (was: Patch Available) > TotalQueryCost logic broken > > > Key: LENS-1493 > URL: https://issues.apache.org/jira/browse/LENS-1493 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1493.patch > > > The totalQueryCost method in DefaultEstimatedQueryCollection is throwing > following error : > Error in query submitter > java.lang.ClassCastException: > org.apache.lens.server.api.query.cost.FactPartitionBasedQueryCost cannot be > cast to org.apache.lens.server.api.query.cost.StaticQueryCost > at > org.apache.lens.server.api.query.cost.StaticQueryCost.add(StaticQueryCost.java:33) > > at > org.apache.lens.server.query.collect.DefaultEstimatedQueryCollection.getTotalQueryCost(DefaultEstimatedQueryCollection.java:171) > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1493) TotalQueryCost logic broken
[ https://issues.apache.org/jira/browse/LENS-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1493: --- Fix Version/s: 2.8 > TotalQueryCost logic broken > > > Key: LENS-1493 > URL: https://issues.apache.org/jira/browse/LENS-1493 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1493.patch > > > The totalQueryCost method in DefaultEstimatedQueryCollection is throwing > following error : > Error in query submitter > java.lang.ClassCastException: > org.apache.lens.server.api.query.cost.FactPartitionBasedQueryCost cannot be > cast to org.apache.lens.server.api.query.cost.StaticQueryCost > at > org.apache.lens.server.api.query.cost.StaticQueryCost.add(StaticQueryCost.java:33) > > at > org.apache.lens.server.query.collect.DefaultEstimatedQueryCollection.getTotalQueryCost(DefaultEstimatedQueryCollection.java:171) > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1480) For virtual facts, column start and end times are not working
[ https://issues.apache.org/jira/browse/LENS-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1480: --- Resolution: Fixed Status: Resolved (was: Patch Available) > For virtual facts, column start and end times are not working > - > > Key: LENS-1480 > URL: https://issues.apache.org/jira/browse/LENS-1480 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1480.1.patch, LENS-1480.patch > > > For virtual facts, column start times are not working -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1480) For virtual facts, column start and end times are not working
[ https://issues.apache.org/jira/browse/LENS-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1480: --- Fix Version/s: 2.8 > For virtual facts, column start and end times are not working > - > > Key: LENS-1480 > URL: https://issues.apache.org/jira/browse/LENS-1480 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1480.1.patch, LENS-1480.patch > > > For virtual facts, column start times are not working -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1480) For virtual facts, column start and end times are not working
[ https://issues.apache.org/jira/browse/LENS-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296640#comment-16296640 ] Puneet Gupta commented on LENS-1480: Committed. Thanks [~rajitha.r] > For virtual facts, column start and end times are not working > - > > Key: LENS-1480 > URL: https://issues.apache.org/jira/browse/LENS-1480 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1480.1.patch, LENS-1480.patch > > > For virtual facts, column start times are not working -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1486) Disable test case testQueryAliveOnSessionClose
[ https://issues.apache.org/jira/browse/LENS-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260496#comment-16260496 ] Puneet Gupta commented on LENS-1486: +1 > Disable test case testQueryAliveOnSessionClose > --- > > Key: LENS-1486 > URL: https://issues.apache.org/jira/browse/LENS-1486 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Sushil Mohanty >Assignee: Sushil Mohanty > Attachments: LENS-1486.patch > > > TestQueryIndependenceFromSessionClose.testQueryAliveOnSessionClose is failing > in past few builds, commenting it temporarily to make the build pass. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1484) Lens Server pre commit build failing due to enunciate plugin
[ https://issues.apache.org/jira/browse/LENS-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1484: --- Attachment: LENS-1484.patch Simple patch. Uploading directly > Lens Server pre commit build failing due to enunciate plugin > > > Key: LENS-1484 > URL: https://issues.apache.org/jira/browse/LENS-1484 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: LENS-1484.patch > > > [ERROR] Failed to execute goal > com.webcohesion.enunciate:enunciate-maven-plugin:2.5.0:docs (default) on > project lens-server: freemarker.core._TemplateModelException: An error has > occurred when reading existing sub-variable "securityRoles"; see cause > exception! The type of the containing value was: extended_hash+string > (com.webcohesion.enunciate.modules.jaxrs.api.impl.MethodImpl wrapped into > f.e.b.StringModel) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1484) Lens Server pre commit build failing due to enunciate plugin
[ https://issues.apache.org/jira/browse/LENS-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1484: --- Status: Patch Available (was: Open) > Lens Server pre commit build failing due to enunciate plugin > > > Key: LENS-1484 > URL: https://issues.apache.org/jira/browse/LENS-1484 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: LENS-1484.patch > > > [ERROR] Failed to execute goal > com.webcohesion.enunciate:enunciate-maven-plugin:2.5.0:docs (default) on > project lens-server: freemarker.core._TemplateModelException: An error has > occurred when reading existing sub-variable "securityRoles"; see cause > exception! The type of the containing value was: extended_hash+string > (com.webcohesion.enunciate.modules.jaxrs.api.impl.MethodImpl wrapped into > f.e.b.StringModel) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (LENS-1484) Lens Server pre commit build failing due to enunciate plugin
[ https://issues.apache.org/jira/browse/LENS-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta reassigned LENS-1484: -- Assignee: Puneet Gupta > Lens Server pre commit build failing due to enunciate plugin > > > Key: LENS-1484 > URL: https://issues.apache.org/jira/browse/LENS-1484 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > > [ERROR] Failed to execute goal > com.webcohesion.enunciate:enunciate-maven-plugin:2.5.0:docs (default) on > project lens-server: freemarker.core._TemplateModelException: An error has > occurred when reading existing sub-variable "securityRoles"; see cause > exception! The type of the containing value was: extended_hash+string > (com.webcohesion.enunciate.modules.jaxrs.api.impl.MethodImpl wrapped into > f.e.b.StringModel) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (LENS-1484) Lens Server pre commit build failing due to enunciate plugin
Puneet Gupta created LENS-1484: -- Summary: Lens Server pre commit build failing due to enunciate plugin Key: LENS-1484 URL: https://issues.apache.org/jira/browse/LENS-1484 Project: Apache Lens Issue Type: Bug Components: server Reporter: Puneet Gupta [ERROR] Failed to execute goal com.webcohesion.enunciate:enunciate-maven-plugin:2.5.0:docs (default) on project lens-server: freemarker.core._TemplateModelException: An error has occurred when reading existing sub-variable "securityRoles"; see cause exception! The type of the containing value was: extended_hash+string (com.webcohesion.enunciate.modules.jaxrs.api.impl.MethodImpl wrapped into f.e.b.StringModel) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1425) Update 2.7 release documentation
[ https://issues.apache.org/jira/browse/LENS-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16235261#comment-16235261 ] Puneet Gupta commented on LENS-1425: Under the incompatibility section , we can remove these LENS-968 (This is a new feature) and LENS-1359 (LENS-1013 was actual incompatibility in driver hook which was released in lens 2.6) > Update 2.7 release documentation > > > Key: LENS-1425 > URL: https://issues.apache.org/jira/browse/LENS-1425 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Raju Bairishetti >Assignee: Raju Bairishetti >Priority: Major > Fix For: 2.7 > > Attachments: LENS-1425.patch > > > Update the release documentation with 2.7 features -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1478) Queries with partial data set as false lookahead not working
[ https://issues.apache.org/jira/browse/LENS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171303#comment-16171303 ] Puneet Gupta commented on LENS-1478: +1 > Queries with partial data set as false lookahead not working > > > Key: LENS-1478 > URL: https://issues.apache.org/jira/browse/LENS-1478 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Sushil Mohanty >Assignee: Sushil Mohanty > Attachments: LENS-1478.patch > > > For queries with set lens.cube.query.fail.if.data.partial=false lookahead > queries partitions are not getting resolved and the being rewritten same as > input time_range_in function. This results query failure with syntax error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1476) Order By clause is not rewritten correctly when column is wrapped with function
[ https://issues.apache.org/jira/browse/LENS-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164370#comment-16164370 ] Puneet Gupta commented on LENS-1476: +1 for patch > Order By clause is not rewritten correctly when column is wrapped with > function > --- > > Key: LENS-1476 > URL: https://issues.apache.org/jira/browse/LENS-1476 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Sushil Mohanty >Assignee: Sushil Mohanty > Attachments: LENS-1476.patch > > > Order by clauses like to_date(datecol) is not not rewritten properly in the > final union query. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (LENS-1436) Lens Server's previously persisted state should be backed up before creating a new persisted state
Puneet Gupta created LENS-1436: -- Summary: Lens Server's previously persisted state should be backed up before creating a new persisted state Key: LENS-1436 URL: https://issues.apache.org/jira/browse/LENS-1436 Project: Apache Lens Issue Type: Improvement Components: server Reporter: Puneet Gupta As of now lens server state is persisted up every 5 mins . The sate is also persisted when server is going down. Consider a scenario where server is running out of memory or all its threads are blocked and writes a corrupt state while going down. In this case we lose all the queries and/or session info. Proposal : before creating a server state snapshot, the previous snapshot (folder) should be backed up. Now we will have two persisted states, the current one and backed up state(5 mins old state). If the current state is corrupt, server can use the backed up state in which case we lose out only on last 5 mins of state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (LENS-1431) Data Availability Feature broken
[ https://issues.apache.org/jira/browse/LENS-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038641#comment-16038641 ] Puneet Gupta commented on LENS-1431: review Request : https://reviews.apache.org/r/59830 > Data Availability Feature broken > - > > Key: LENS-1431 > URL: https://issues.apache.org/jira/browse/LENS-1431 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Sushrut Meghshyam Ikhar >Assignee: Sushrut Meghshyam Ikhar > Attachments: LENS-1431.patch > > > If data availability is enabled on a partition-coulmn- > and availability for measure is > threshold still availability is shown as > FALSE -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel=16036867#comment-16036867
]
Puneet Gupta commented on LENS-1429:
+1
> 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
> 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.3.15#6346)
[jira] [Created] (LENS-1426) Support max limit for "timeoutmillis" in EXECUTE_WITH_TIMEOUT option
Puneet Gupta created LENS-1426: -- Summary: Support max limit for "timeoutmillis" in EXECUTE_WITH_TIMEOUT option Key: LENS-1426 URL: https://issues.apache.org/jira/browse/LENS-1426 Project: Apache Lens Issue Type: Improvement Components: server Reporter: Puneet Gupta We can set the max to 5 mins and if a user sets the timeoutmillis > 5 mins , this api can throw an exception. Reason : this is a blocking call and blocks a request thread on server. Long timeoutmillis values can cause DOS by blocking all the request threads -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (LENS-981) Add Memory gatekeepers for InMemoryResultSet to prevent any OOM on lens server
[ https://issues.apache.org/jira/browse/LENS-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta reassigned LENS-981: - Assignee: Lavkesh Lahngir (was: Puneet Gupta) > Add Memory gatekeepers for InMemoryResultSet to prevent any OOM on lens server > -- > > Key: LENS-981 > URL: https://issues.apache.org/jira/browse/LENS-981 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Puneet Gupta >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > > In Some cases operations on InMemoryResultSet can result is high memory usage > on LensServer > 1. InMemoryResultSet.toQueryResult() is done for a huge result > 2. lens.query.prefetch.inmemory.resultset.rows = Huge Number . > In both cases we need to have some gate keeping as these features can be > accessed/configured by users -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (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 ] Puneet Gupta updated LENS-1419: --- Comment: was deleted (was: +1) > 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 > 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.3.15#6346)
[jira] [Commented] (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:comment-tabpanel=15996544#comment-15996544 ] Puneet Gupta commented on LENS-1419: +1 > 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 > 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.3.15#6346)
[jira] [Updated] (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 ] Puneet Gupta updated LENS-1419: --- Status: Patch Available (was: Open) > 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 > 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.3.15#6346)
[jira] [Commented] (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:comment-tabpanel=15996543#comment-15996543 ] Puneet Gupta commented on LENS-1419: +1 > 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 > 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.3.15#6346)
[jira] [Updated] (LENS-1413) Estimates failing with Task rejection errors
[ https://issues.apache.org/jira/browse/LENS-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1413: --- Fix Version/s: 2.7 > Estimates failing with Task rejection errors > > > Key: LENS-1413 > URL: https://issues.apache.org/jira/browse/LENS-1413 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > Attachments: LENS-1413.patch > > > # Cancel estimates for other drivers when the estimate pool queue is full. > # Return the appropriate error message -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (LENS-1413) Estimates failing with Task rejection errors
[ https://issues.apache.org/jira/browse/LENS-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982667#comment-15982667 ] Puneet Gupta commented on LENS-1413: Committed. Thanks [~lavkesh] > Estimates failing with Task rejection errors > > > Key: LENS-1413 > URL: https://issues.apache.org/jira/browse/LENS-1413 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > Attachments: LENS-1413.patch > > > # Cancel estimates for other drivers when the estimate pool queue is full. > # Return the appropriate error message -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (LENS-1391) Review comments for MaxCoveringFactResolver and LeastPartitionResolver On branch lens-1381
[ https://issues.apache.org/jira/browse/LENS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972412#comment-15972412 ] Puneet Gupta commented on LENS-1391: [~lavkesh] please fix the checkstyle errors > Review comments for MaxCoveringFactResolver and LeastPartitionResolver On > branch lens-1381 > -- > > Key: LENS-1391 > URL: https://issues.apache.org/jira/browse/LENS-1391 > Project: Apache Lens > Issue Type: Task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1391.patch > > > Reviews comments fixes for MaxCoveringFactResolver and LeastPartitionResolver -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1407) "fact show timelines" should not report timeline outside of fact/storage validity period
[ https://issues.apache.org/jira/browse/LENS-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1407: --- Summary: "fact show timelines" should not report timeline outside of fact/storage validity period (was: Fact show timelines should not report timeline outside of fact/storage validity period) > "fact show timelines" should not report timeline outside of fact/storage > validity period > > > Key: LENS-1407 > URL: https://issues.apache.org/jira/browse/LENS-1407 > Project: Apache Lens > Issue Type: Bug > Components: metadata >Reporter: Puneet Gupta >Priority: Minor > > Fact show timelines even reports missing partitions outside of fact/storage > start and end time. > This should not be the case . Partitions that do not fall within the storage > start and end time should not be considered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (LENS-1407) Fact show timelines should not report timeline outside of fact/storage validity period
Puneet Gupta created LENS-1407: -- Summary: Fact show timelines should not report timeline outside of fact/storage validity period Key: LENS-1407 URL: https://issues.apache.org/jira/browse/LENS-1407 Project: Apache Lens Issue Type: Bug Components: metadata Reporter: Puneet Gupta Priority: Minor Fact show timelines even reports missing partitions outside of fact/storage start and end time. This should not be the case . Partitions that do not fall within the storage start and end time should not be considered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (LENS-1397) Support query rewrite for separate table per update period in a storage
[ https://issues.apache.org/jira/browse/LENS-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945001#comment-15945001 ] Puneet Gupta commented on LENS-1397: Taking patch from reviewboard and attaching > Support query rewrite for separate table per update period in a storage > --- > > Key: LENS-1397 > URL: https://issues.apache.org/jira/browse/LENS-1397 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: LENS-1397.03.patch > > > Consider the case where a Storage S has three update periods and each update > period has a different table description "table_desc" as supported in > LENS-1386. > We should be able to rewrite queries for such storages -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1397) Support query rewrite for separate table per update period in a storage
[ https://issues.apache.org/jira/browse/LENS-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1397: --- Status: Patch Available (was: In Progress) > Support query rewrite for separate table per update period in a storage > --- > > Key: LENS-1397 > URL: https://issues.apache.org/jira/browse/LENS-1397 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: LENS-1397.03.patch > > > Consider the case where a Storage S has three update periods and each update > period has a different table description "table_desc" as supported in > LENS-1386. > We should be able to rewrite queries for such storages -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (LENS-1397) Support query rewrite for separate table per update period in a storage
[ https://issues.apache.org/jira/browse/LENS-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-1397 started by Puneet Gupta. -- > Support query rewrite for separate table per update period in a storage > --- > > Key: LENS-1397 > URL: https://issues.apache.org/jira/browse/LENS-1397 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > > Consider the case where a Storage S has three update periods and each update > period has a different table description "table_desc" as supported in > LENS-1386. > We should be able to rewrite queries for such storages -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (LENS-1400) Convert CubeTestSetup to setup using xml files instead of code
[ https://issues.apache.org/jira/browse/LENS-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902507#comment-15902507 ] Puneet Gupta commented on LENS-1400: This will be very helpful in writing new test cases and understanding/optimizing the current ones. Thanks [~prongs] > 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 > > 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.3.15#6346)
[jira] [Updated] (LENS-1401) FallBack Range not considered while doing TimeRange validation for facts and columns
[ https://issues.apache.org/jira/browse/LENS-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1401: --- Component/s: (was: server) cube > FallBack Range not considered while doing TimeRange validation for facts and > columns > > > Key: LENS-1401 > URL: https://issues.apache.org/jira/browse/LENS-1401 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Puneet Gupta > > There is a problem in query rewriting flow wrt to fallback time. > Fallback is decided only in StorageTableResolution phase but until then the > user supplied TimeRange is used to validate facts and columns (and not > fallback range). If Fallback range is very different from actual time range > there can be a very obvious issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1397) Support query rewrite for separate table per update period in a storage
[ https://issues.apache.org/jira/browse/LENS-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1397: --- Summary: Support query rewrite for separate table per update period in a storage (was: Support query rewrite for separate table per update periods in a storage) > Support query rewrite for separate table per update period in a storage > --- > > Key: LENS-1397 > URL: https://issues.apache.org/jira/browse/LENS-1397 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > > Consider the case where a Storage S has three update periods and each update > period has a different table description "table_desc" as supported in > LENS-1386. > We should be able to rewrite queries for such storages -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (LENS-1397) Support query rewrite for separate table per update periods in a storage
Puneet Gupta created LENS-1397: -- Summary: Support query rewrite for separate table per update periods in a storage Key: LENS-1397 URL: https://issues.apache.org/jira/browse/LENS-1397 Project: Apache Lens Issue Type: Sub-task Components: server Reporter: Puneet Gupta Assignee: Puneet Gupta Consider the case where a Storage S has three update periods and each update period has a different table description "table_desc" as supported in LENS-1386. We should be able to rewrite queries for such storages -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (LENS-1372) QueryRetryTest is flaky
[
https://issues.apache.org/jira/browse/LENS-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887439#comment-15887439
]
Puneet Gupta commented on LENS-1372:
Not sure how ctx can be null on restart.
org.apache.lens.server.query.QueryExecutionServiceImpl#writeExternal is
persisting all query contexts (QueryExecutionServiceImpl#allQueries) before
restart and restoring them after restart
QueryExecutionServiceImpl#readExternal).
Do we see any persistence failures in log
(org.apache.lens.server.LensServices#stop,
aorg.apache.lens.server.LensServices#persistLensServiceState) ?
> QueryRetryTest is flaky
> ---
>
> Key: LENS-1372
> URL: https://issues.apache.org/jira/browse/LENS-1372
> Project: Apache Lens
> Issue Type: Test
> Components: server, test
>Affects Versions: 2.7
>Reporter: Ted Yu
>Assignee: Rajat Khandelwal
>Priority: Minor
> Fix For: 2.7
>
>
> From
> https://builds.apache.org/job/PreCommit-Lens-Build/1145/testReport/junit/org.apache.lens.server.query.retry/QueryRetryTest/testRestartWhileRetry/
> :
> {code}
> java.lang.NullPointerException: null
> at
> org.apache.lens.server.query.retry.QueryRetryTest.testRestartWhileRetry(QueryRetryTest.java:201)
> {code}
> Here is related code:
> {code}
> ctx = getQueryService().getQueryContext(handle);
> while (!ctx.getStatus().finished()) {
> {code}
> The test should handle the case where status is null.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (LENS-1393) Update the javax mail version to current
[ https://issues.apache.org/jira/browse/LENS-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877275#comment-15877275 ] Puneet Gupta commented on LENS-1393: +1 > Update the javax mail version to current > > > Key: LENS-1393 > URL: https://issues.apache.org/jira/browse/LENS-1393 > Project: Apache Lens > Issue Type: Task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > > Sending mail with the older version of javax mail was causing threads to > stuck because of connection timeout to the mail server was not honored. > Updating to the new version solves the problem. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (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 ] Puneet Gupta updated LENS-1392: --- Status: Patch Available (was: In Progress) > 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 > 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.3.15#6346)
[jira] [Updated] (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 ] Puneet Gupta updated LENS-1392: --- Resolution: Fixed Status: Resolved (was: Patch Available) > 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 > 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.3.15#6346)
[jira] [Commented] (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:comment-tabpanel=15875792#comment-15875792 ] Puneet Gupta commented on LENS-1392: Committed myself. > 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 > 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.3.15#6346)
[jira] [Updated] (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 ] Puneet Gupta updated LENS-1392: --- Attachment: lens-1392.patch Taking patch form review board and attaching https://reviews.apache.org/r/56877/ > 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 > 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.3.15#6346)
[jira] [Work started] (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 ] Work on LENS-1392 started by Puneet Gupta. -- > 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 > > 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.3.15#6346)
[jira] [Created] (LENS-1392) Fix failing TestCases in org.apache.lens.server.query.QueryAPIErrorResponseTest
Puneet Gupta created LENS-1392: -- Summary: 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 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.3.15#6346)
[jira] [Updated] (LENS-1391) Review comments for MaxCoveringFactResolver and LeastPartitionResolver On branch lens-1381
[ https://issues.apache.org/jira/browse/LENS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1391: --- Summary: Review comments for MaxCoveringFactResolver and LeastPartitionResolver On branch lens-1381 (was: Review comments for MaxCoveringFactResolver and LeastPartitionResolver On brach lens-1381) > Review comments for MaxCoveringFactResolver and LeastPartitionResolver On > branch lens-1381 > -- > > Key: LENS-1391 > URL: https://issues.apache.org/jira/browse/LENS-1391 > Project: Apache Lens > Issue Type: Task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > > Reviews comments fixes for MaxCoveringFactResolver and LeastPartitionResolver -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (LENS-1382) org.apache.lens.client.LensStatement#getAllQueryDetails is returning wrong result
Puneet Gupta created LENS-1382: -- Summary: org.apache.lens.client.LensStatement#getAllQueryDetails is returning wrong result Key: LENS-1382 URL: https://issues.apache.org/jira/browse/LENS-1382 Project: Apache Lens Issue Type: Bug Reporter: Puneet Gupta Assignee: Puneet Gupta Priority: Minor org.apache.lens.client.LensStatement#getAllQueryDetails is returning List instead of List -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1379) Session expiry is not working properly
[ https://issues.apache.org/jira/browse/LENS-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1379: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Session expiry is not working properly > -- > > Key: LENS-1379 > URL: https://issues.apache.org/jira/browse/LENS-1379 > Project: Apache Lens > Issue Type: Bug > Components: server >Affects Versions: 2.6 >Reporter: Amareshwari Sriramadasu >Assignee: Amareshwari Sriramadasu > Fix For: 2.7 > > Attachments: LENS-1379.2.patch > > > We are seeing session expiry is not working properly and found two reasons > for the same : > * isActive method logic is not marking expired sessions as inactive. > * Upon restart lastAccessTime is getting reset to restore time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1379) Session expiry is not working properly
[ https://issues.apache.org/jira/browse/LENS-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15792779#comment-15792779 ] Puneet Gupta commented on LENS-1379: Committed. Thanks [~amareshwari] > Session expiry is not working properly > -- > > Key: LENS-1379 > URL: https://issues.apache.org/jira/browse/LENS-1379 > Project: Apache Lens > Issue Type: Bug > Components: server >Affects Versions: 2.6 >Reporter: Amareshwari Sriramadasu >Assignee: Amareshwari Sriramadasu > Fix For: 2.7 > > Attachments: LENS-1379.2.patch > > > We are seeing session expiry is not working properly and found two reasons > for the same : > * isActive method logic is not marking expired sessions as inactive. > * Upon restart lastAccessTime is getting reset to restore time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1381) Support Fact to Fact Union
[ https://issues.apache.org/jira/browse/LENS-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766896#comment-15766896 ] Puneet Gupta commented on LENS-1381: Created branch for initial changes refs/heads/lens-1381 [created] b6f0cc3d4 > 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: Puneet Gupta > > 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.3.4#6332)
[jira] [Commented] (LENS-1381) Support Fact to Fact Union
[ https://issues.apache.org/jira/browse/LENS-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743976#comment-15743976 ] Puneet Gupta commented on LENS-1381: We are planning to create a feature branch for this since there will be lots of changes in the code. > 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: Puneet Gupta > > 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.3.4#6332)
[jira] [Assigned] (LENS-1381) Support Fact to Fact Union
[ https://issues.apache.org/jira/browse/LENS-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta reassigned LENS-1381: -- Assignee: Puneet Gupta > 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: Puneet Gupta > > 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.3.4#6332)
[jira] [Commented] (LENS-1381) Support Fact to Fact Union
[ https://issues.apache.org/jira/browse/LENS-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743967#comment-15743967 ] Puneet Gupta commented on LENS-1381: Design for this requirement : *Current rewrite flow* - Currently the rewrite flow relies on Set and Setwhich represents the participating Facts and combination of Facts(in case of join between 2 or more facts) that can answer the user query respectively. - Set is initially populated considering all the Facts will participate and the Set is created based on joins that are required to answer the query (with assumption that two two facts can be joined if they have the dimensions that are being queried by the user. After joining the facts, the queried measures which are split across facts are picked). Along the rewrite flow the above data structures are pruned based on column availability, data availability, storage validity, fact validity, cost,etc. In the last a final CandidateFact combination is picked from Set . - To write the rewritten query for the picked candidate combination, one of the following contexts are created -- SingleFactSingleStorageHQLContext or (Candidate combination has single fact and single storage) -- SingleFactMultiStorageHQLContext or (Candidate combination has single fact and multiple storages within that fact - Union Query) -- MultiFactHQLContext (Candidate combination has multiple facts - Join Query) *New Flow* # The new flow will work at Storage level and will use a list of StorageCandidates. Initially all Storages are candidates. # The list of StorageCandidates is pruned based on column availability, storage validity, fact validity, update period validity,etc # The StorageCandidates are then grouped to ensure that a group can cover the entire time range queried by the user. Its possible for a group to have a single StorageCandidate incase this storage alone can fulfill the time ranges queried. If a group has more that one storages , then this group is represented as a UnionCandidate. # The groups created in step 3 ( UnionCandidates and StorageCandidates) are used to find a measure covering group such that members of this group cover all the measures queried by the user. Again its possible for this group to have a single member (which can be a StorageCandidate or a UnionCandidate) that can answer all the measures. If the group has more than one members, then that group is represented as a JoinCandidate # JoinCandidate, UnionCandidate and StorageCandidate extend the same Candidate Interface. # The groups created in step 4 are further pruned based on data availability, cost ,etc we pick a winning group (Candidate) # Query is then written for this winning Candidate > 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 > > 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.3.4#6332)
[jira] [Created] (LENS-1381) Support Fact to Fact Union
Puneet Gupta created LENS-1381: -- Summary: 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 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.3.4#6332)
[jira] [Commented] (LENS-1359) Add driver hooks for user based filtering of queries
[ https://issues.apache.org/jira/browse/LENS-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662838#comment-15662838 ] Puneet Gupta commented on LENS-1359: Committed. Thanks [~prongs] > Add driver hooks for user based filtering of queries > > > Key: LENS-1359 > URL: https://issues.apache.org/jira/browse/LENS-1359 > Project: Apache Lens > Issue Type: Task >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Labels: incompatible > Fix For: 2.7 > > Attachments: LENS-1359.01.patch, LENS-1359.02.patch, > LENS-1359.03.patch, LENS-1359.04.patch, LENS-1359.05.patch, > LENS-1359.06.patch, LENS-1359.07.patch, LENS-1359.08.patch, > LENS-1359.09.patch, LENS-1359.10.patch, LENS-1359.11.patch, > LENS-1359.12.patch, LENS-1359.13.patch, LENS-1359.14.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1359) Add driver hooks for user based filtering of queries
[ https://issues.apache.org/jira/browse/LENS-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1359: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add driver hooks for user based filtering of queries > > > Key: LENS-1359 > URL: https://issues.apache.org/jira/browse/LENS-1359 > Project: Apache Lens > Issue Type: Task >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Labels: incompatible > Fix For: 2.7 > > Attachments: LENS-1359.01.patch, LENS-1359.02.patch, > LENS-1359.03.patch, LENS-1359.04.patch, LENS-1359.05.patch, > LENS-1359.06.patch, LENS-1359.07.patch, LENS-1359.08.patch, > LENS-1359.09.patch, LENS-1359.10.patch, LENS-1359.11.patch, > LENS-1359.12.patch, LENS-1359.13.patch, LENS-1359.14.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1359) Add driver hooks for user based filtering of queries
[ https://issues.apache.org/jira/browse/LENS-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1359: --- Fix Version/s: 2.7 > Add driver hooks for user based filtering of queries > > > Key: LENS-1359 > URL: https://issues.apache.org/jira/browse/LENS-1359 > Project: Apache Lens > Issue Type: Task >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Labels: incompatible > Fix For: 2.7 > > Attachments: LENS-1359.01.patch, LENS-1359.02.patch, > LENS-1359.03.patch, LENS-1359.04.patch, LENS-1359.05.patch, > LENS-1359.06.patch, LENS-1359.07.patch, LENS-1359.08.patch, > LENS-1359.09.patch, LENS-1359.10.patch, LENS-1359.11.patch, > LENS-1359.12.patch, LENS-1359.13.patch, LENS-1359.14.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1359) Add driver hooks for user based filtering of queries
[ https://issues.apache.org/jira/browse/LENS-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650700#comment-15650700 ] Puneet Gupta commented on LENS-1359: Patch doesn't cleanly apply. Please sync with latest and update > Add driver hooks for user based filtering of queries > > > Key: LENS-1359 > URL: https://issues.apache.org/jira/browse/LENS-1359 > Project: Apache Lens > Issue Type: Task >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Labels: incompatible > Attachments: LENS-1359.01.patch, LENS-1359.02.patch, > LENS-1359.03.patch, LENS-1359.04.patch, LENS-1359.05.patch, > LENS-1359.06.patch, LENS-1359.07.patch, LENS-1359.08.patch, > LENS-1359.09.patch, LENS-1359.10.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1359) Add driver hooks for user based filtering of queries
[ https://issues.apache.org/jira/browse/LENS-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1359: --- Status: Open (was: Patch Available) > Add driver hooks for user based filtering of queries > > > Key: LENS-1359 > URL: https://issues.apache.org/jira/browse/LENS-1359 > Project: Apache Lens > Issue Type: Task >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Labels: incompatible > Attachments: LENS-1359.01.patch, LENS-1359.02.patch, > LENS-1359.03.patch, LENS-1359.04.patch, LENS-1359.05.patch, > LENS-1359.06.patch, LENS-1359.07.patch, LENS-1359.08.patch, > LENS-1359.09.patch, LENS-1359.10.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1342) Unclosed InputStreamReader in PropertyBasedUserConfigLoader
[
https://issues.apache.org/jira/browse/LENS-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628238#comment-15628238
]
Puneet Gupta commented on LENS-1342:
Resubmitting to check failures
https://builds.apache.org/job/PreCommit-Lens-Build/1143/
> Unclosed InputStreamReader in PropertyBasedUserConfigLoader
> ---
>
> Key: LENS-1342
> URL: https://issues.apache.org/jira/browse/LENS-1342
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
> Attachments: 1342.v1.txt
>
>
> {code}
> try {
> properties.load(new InputStreamReader(new FileInputStream(new
> File(filename)), "UTF-8"));
> } catch (IOException e) {
> throw new UserConfigLoaderException("property file not found. Provided
> path was: " + filename);
> }
> {code}
> The InputStreamReader should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (LENS-1310) Release Lens 2.6
[ https://issues.apache.org/jira/browse/LENS-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta resolved LENS-1310. Resolution: Fixed Fix Version/s: 2.6 > Release Lens 2.6 > > > Key: LENS-1310 > URL: https://issues.apache.org/jira/browse/LENS-1310 > Project: Apache Lens > Issue Type: Task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1363) Error While building Lens Site
[ https://issues.apache.org/jira/browse/LENS-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1363: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Error While building Lens Site > -- > > Key: LENS-1363 > URL: https://issues.apache.org/jira/browse/LENS-1363 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.7 > > Attachments: lens-1363.patch > > > 1. The output of enunciate had changed after upgrading it. > Need to update tools/scripts/generate-site-public.sh accordingly. > 2. Download links are pointing to lens 2.6. Need to change to point to 2.6.1 > 3. Roles need to be updated in pom.xml for two team members -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1363) Error While building Lens Site
[ https://issues.apache.org/jira/browse/LENS-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1363: --- Fix Version/s: 2.7 > Error While building Lens Site > -- > > Key: LENS-1363 > URL: https://issues.apache.org/jira/browse/LENS-1363 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.7 > > Attachments: lens-1363.patch > > > 1. The output of enunciate had changed after upgrading it. > Need to update tools/scripts/generate-site-public.sh accordingly. > 2. Download links are pointing to lens 2.6. Need to change to point to 2.6.1 > 3. Roles need to be updated in pom.xml for two team members -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1363) Error While building Lens Site
[ https://issues.apache.org/jira/browse/LENS-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607539#comment-15607539 ] Puneet Gupta commented on LENS-1363: Committed myself. > Error While building Lens Site > -- > > Key: LENS-1363 > URL: https://issues.apache.org/jira/browse/LENS-1363 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.7 > > Attachments: lens-1363.patch > > > 1. The output of enunciate had changed after upgrading it. > Need to update tools/scripts/generate-site-public.sh accordingly. > 2. Download links are pointing to lens 2.6. Need to change to point to 2.6.1 > 3. Roles need to be updated in pom.xml for two team members -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1363) Error While building Lens Site
[ https://issues.apache.org/jira/browse/LENS-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1363: --- Description: 1. The output of enunciate had changed after upgrading it. Need to update tools/scripts/generate-site-public.sh accordingly. 2. Download links are pointing to lens 2.6. Need to change to point to 2.6.1 3. Roles need to be updated in pom.xml for two team members was: The output of enunciate had changed after upgrading it. Need to update tools/scripts/generate-site-public.sh accordingly. > Error While building Lens Site > -- > > Key: LENS-1363 > URL: https://issues.apache.org/jira/browse/LENS-1363 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: lens-1363.patch > > > 1. The output of enunciate had changed after upgrading it. > Need to update tools/scripts/generate-site-public.sh accordingly. > 2. Download links are pointing to lens 2.6. Need to change to point to 2.6.1 > 3. Roles need to be updated in pom.xml for two team members -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1363) Error While building Lens Site
[ https://issues.apache.org/jira/browse/LENS-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1363: --- Status: Patch Available (was: Open) Small Change. Attaching patch directly for review > Error While building Lens Site > -- > > Key: LENS-1363 > URL: https://issues.apache.org/jira/browse/LENS-1363 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: lens-1363.patch > > > The output of enunciate had changed after upgrading it. > Need to update tools/scripts/generate-site-public.sh accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1363) Error While building Lens Site
[ https://issues.apache.org/jira/browse/LENS-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1363: --- Attachment: lens-1363.patch > Error While building Lens Site > -- > > Key: LENS-1363 > URL: https://issues.apache.org/jira/browse/LENS-1363 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: lens-1363.patch > > > The output of enunciate had changed after upgrading it. > Need to update tools/scripts/generate-site-public.sh accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1365) REST Api docs generated via enunciate plugin 2.5 has two entries for JSON data type
[ https://issues.apache.org/jira/browse/LENS-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1365: --- Description: See attached images > REST Api docs generated via enunciate plugin 2.5 has two entries for JSON > data type > --- > > Key: LENS-1365 > URL: https://issues.apache.org/jira/browse/LENS-1365 > Project: Apache Lens > Issue Type: Bug >Reporter: Puneet Gupta > Attachments: screenshot-1.png, screenshot-2.png > > > See attached images -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1365) REST Api docs generated via enunciate plugin 2.5 has two entries for JSON data type
[ https://issues.apache.org/jira/browse/LENS-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1365: --- Attachment: screenshot-2.png > REST Api docs generated via enunciate plugin 2.5 has two entries for JSON > data type > --- > > Key: LENS-1365 > URL: https://issues.apache.org/jira/browse/LENS-1365 > Project: Apache Lens > Issue Type: Bug >Reporter: Puneet Gupta > Attachments: screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1365) REST Api docs generated via enunciate plugin 2.5 has two entries for JSON data type
[ https://issues.apache.org/jira/browse/LENS-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1365: --- Attachment: screenshot-1.png > REST Api docs generated via enunciate plugin 2.5 has two entries for JSON > data type > --- > > Key: LENS-1365 > URL: https://issues.apache.org/jira/browse/LENS-1365 > Project: Apache Lens > Issue Type: Bug >Reporter: Puneet Gupta > Attachments: screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1365) REST Api docs generated via enunciate plugin 2.5 has two entries for JSON data type
Puneet Gupta created LENS-1365: -- Summary: REST Api docs generated via enunciate plugin 2.5 has two entries for JSON data type Key: LENS-1365 URL: https://issues.apache.org/jira/browse/LENS-1365 Project: Apache Lens Issue Type: Bug Reporter: Puneet Gupta -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1363) Error While building Lens Site
Puneet Gupta created LENS-1363: -- Summary: Error While building Lens Site Key: LENS-1363 URL: https://issues.apache.org/jira/browse/LENS-1363 Project: Apache Lens Issue Type: Sub-task Reporter: Puneet Gupta Assignee: Puneet Gupta The output of enunciate had changed after upgrading it. Need to update tools/scripts/generate-site-public.sh accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1325) Support encoded urls for query HTTP notifications
[ https://issues.apache.org/jira/browse/LENS-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1325: --- Attachment: lens-1325.v2.patch > Support encoded urls for query HTTP notifications > - > > Key: LENS-1325 > URL: https://issues.apache.org/jira/browse/LENS-1325 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.7 > > Attachments: lens-1325.v2.patch > > > This notification url is working : > http://x:8000/v1/data/?access_token=ABC123 > This is giving 400 bad request : > http://:8000/v1/data/?access_token=ABC123=xyz > Please check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1325) Support encoded urls for query HTTP notifications
[ https://issues.apache.org/jira/browse/LENS-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588492#comment-15588492 ] Puneet Gupta commented on LENS-1325: https://reviews.apache.org/r/52341 > Support encoded urls for query HTTP notifications > - > > Key: LENS-1325 > URL: https://issues.apache.org/jira/browse/LENS-1325 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.7 > > > This notification url is working : > http://x:8000/v1/data/?access_token=ABC123 > This is giving 400 bad request : > http://:8000/v1/data/?access_token=ABC123=xyz > Please check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (LENS-1325) Support encoded urls for query HTTP notifications
[ https://issues.apache.org/jira/browse/LENS-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-1325 started by Puneet Gupta. -- > Support encoded urls for query HTTP notifications > - > > Key: LENS-1325 > URL: https://issues.apache.org/jira/browse/LENS-1325 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.7 > > > This notification url is working : > http://x:8000/v1/data/?access_token=ABC123 > This is giving 400 bad request : > http://:8000/v1/data/?access_token=ABC123=xyz > Please check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1324) Support more hooks in DriverQueryHook
[ https://issues.apache.org/jira/browse/LENS-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528607#comment-15528607 ] Puneet Gupta commented on LENS-1324: https://reviews.apache.org/r/52337/ > Support more hooks in DriverQueryHook > - > > Key: LENS-1324 > URL: https://issues.apache.org/jira/browse/LENS-1324 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.7 > > > Currently we have two hooks > 1. preLaunch > 2. postDriverSelection > Need to add some hooks that can hook into rewrite and estimate flow also. > 1.preRewrite, postRewrite > 2.preEstimate,postEstimate > NoOpDriverQueryHook will have default empty implementation for these new > methods . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (LENS-1324) Support more hooks in DriverQueryHook
[ https://issues.apache.org/jira/browse/LENS-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-1324 started by Puneet Gupta. -- > Support more hooks in DriverQueryHook > - > > Key: LENS-1324 > URL: https://issues.apache.org/jira/browse/LENS-1324 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.7 > > > Currently we have two hooks > 1. preLaunch > 2. postDriverSelection > Need to add some hooks that can hook into rewrite and estimate flow also. > 1.preRewrite, postRewrite > 2.preEstimate,postEstimate > NoOpDriverQueryHook will have default empty implementation for these new > methods . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-743) Query failure retries for transient errors
[ https://issues.apache.org/jira/browse/LENS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528395#comment-15528395 ] Puneet Gupta commented on LENS-743: --- [~prongs] Thanks for documenting this one in such detail. +1 for dual re-policy (driver+server) I had one doubt. Suppose we have 3 drivers (d1,d,2,d3). Query was run on d1 and failed twice and d1's policy confirmed a no-retry. The server policy said try on d2,d3 and d2 was chosen based on cost. Then 2 tries were done on d2 and they failed too and d2's policy confirmed a no-retry. Will the server policy now try on d3 alone now or d1 and d3? > Query failure retries for transient errors > -- > > Key: LENS-743 > URL: https://issues.apache.org/jira/browse/LENS-743 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Amareshwari Sriramadasu >Assignee: Rajat Khandelwal > Labels: gsoc2016, java > > There have to be retries for query failures for transient errors like network > errors (Hive server not reachable/ Metastore not reachable/ DB not > reachable). Retries should be available for each phase - submission, > execution, updating status, fetching results and formatting. > Right now, any such failure results in marking query as failed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1337) Update Release documentation for lens 2.6.1
[ https://issues.apache.org/jira/browse/LENS-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1337: --- Attachment: lens-1337.v2.patch "updated 2.6.x docs link to 2.6.1" in release-history.apt > Update Release documentation for lens 2.6.1 > --- > > Key: LENS-1337 > URL: https://issues.apache.org/jira/browse/LENS-1337 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Affects Versions: 2.6 >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Fix For: 2.6 > > Attachments: lens-1337.patch, lens-1337.v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (LENS-1337) Update Release documentation for lens 2.6.1
[ https://issues.apache.org/jira/browse/LENS-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta reassigned LENS-1337: -- Assignee: Puneet Gupta > Update Release documentation for lens 2.6.1 > --- > > Key: LENS-1337 > URL: https://issues.apache.org/jira/browse/LENS-1337 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: lens-1337.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (LENS-1337) Update Release documentation for lens 2.6.1
[ https://issues.apache.org/jira/browse/LENS-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516706#comment-15516706 ] Puneet Gupta edited comment on LENS-1337 at 9/23/16 3:05 PM: - [~amareshwari] can you check the doc changes was (Author: puneet884): @Amareshwari can you check the doc changes > Update Release documentation for lens 2.6.1 > --- > > Key: LENS-1337 > URL: https://issues.apache.org/jira/browse/LENS-1337 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: lens-1337.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1337) Update Release documentation for lens 2.6.1
[ https://issues.apache.org/jira/browse/LENS-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516706#comment-15516706 ] Puneet Gupta commented on LENS-1337: @Amareshwari can you check the doc changes > Update Release documentation for lens 2.6.1 > --- > > Key: LENS-1337 > URL: https://issues.apache.org/jira/browse/LENS-1337 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta >Assignee: Puneet Gupta > Attachments: lens-1337.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1337) Update Release documentation for lens 2.6.1
[ https://issues.apache.org/jira/browse/LENS-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1337: --- Attachment: lens-1337.patch > Update Release documentation for lens 2.6.1 > --- > > Key: LENS-1337 > URL: https://issues.apache.org/jira/browse/LENS-1337 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta > Attachments: lens-1337.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1337) Update Release documentation for lens 2.6.1
[ https://issues.apache.org/jira/browse/LENS-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516701#comment-15516701 ] Puneet Gupta commented on LENS-1337: Looks like only release-history.apt needs version change. The download.apt should not require change in download link. > Update Release documentation for lens 2.6.1 > --- > > Key: LENS-1337 > URL: https://issues.apache.org/jira/browse/LENS-1337 > Project: Apache Lens > Issue Type: Sub-task > Components: build >Reporter: Puneet Gupta > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (LENS-1336) lens/contrib is not included in modules
[ https://issues.apache.org/jira/browse/LENS-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1336: --- Comment: was deleted (was: Simple patch attaching directly .) > 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 >Reporter: Puneet Gupta >Priority: Blocker > Fix For: 2.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1336) lens/contrib is not included in modules
[ https://issues.apache.org/jira/browse/LENS-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1336: --- Attachment: (was: lens-1336.patch) > 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 >Reporter: Puneet Gupta >Priority: Blocker > Fix For: 2.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1336) lens/contrib is not included in modules
[ https://issues.apache.org/jira/browse/LENS-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-1336: --- Attachment: lens-1336.patch Simple patch attaching directly . > 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 >Reporter: Puneet Gupta >Priority: Blocker > Fix For: 2.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1337) Update Release documentation for lens 2.6.1
Puneet Gupta created LENS-1337: -- Summary: Update Release documentation for lens 2.6.1 Key: LENS-1337 URL: https://issues.apache.org/jira/browse/LENS-1337 Project: Apache Lens Issue Type: Sub-task Reporter: Puneet Gupta -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1336) lens/contrib is not included in modules
Puneet Gupta created LENS-1336: -- Summary: 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 Reporter: Puneet Gupta Priority: Blocker Fix For: 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
