[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 ] Lavkesh Lahngir updated LENS-1413: -- Status: Patch Available (was: Open) > 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 > 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] [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 ] Lavkesh Lahngir updated LENS-1413: -- Attachment: LENS-1413.patch > 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 > 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] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Attachment: 0001-LENS-1410.patch > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-LENS-1410.patch, LENS-1410.1.patch > > > Make the filter while getting a list of partitions mandatory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Attachment: (was: LENS-1410.patch) > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1410.1.patch > > > Make the filter while getting a list of partitions mandatory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Attachment: LENS-1410.1.patch > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1410.1.patch, LENS-1410.patch, LENS-1410.patch > > > Make the filter while getting a list of partitions mandatory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Attachment: (was: LENS-1410.patch) > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1410.1.patch, LENS-1410.patch, LENS-1410.patch > > > Make the filter while getting a list of partitions mandatory -- 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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: LENS-1391.1.patch > 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.1.patch, LENS-1391.patch > > > Reviews comments fixes for MaxCoveringFactResolver and LeastPartitionResolver -- 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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: (was: LENS-1391.patch) > 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-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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: (was: LENS-1391.patch) > 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-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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: (was: LENS-1391.patch) > 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-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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: (was: LENS-1391.patch) > 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-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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: LENS-1391.patch > 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, LENS-1391.patch, LENS-1391.patch, > LENS-1391.patch > > > Reviews comments fixes for MaxCoveringFactResolver and LeastPartitionResolver -- 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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: LENS-1391.patch > 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, LENS-1391.patch, LENS-1391.patch > > > Reviews comments fixes for MaxCoveringFactResolver and LeastPartitionResolver -- 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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: (was: LENS-1391.patch) > 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, LENS-1391.patch, LENS-1391.patch > > > Reviews comments fixes for MaxCoveringFactResolver and LeastPartitionResolver -- 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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: LENS-1391.patch > 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, LENS-1391.patch, LENS-1391.patch > > > Reviews comments fixes for MaxCoveringFactResolver and LeastPartitionResolver -- 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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: LENS-1391.patch > 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, LENS-1391.patch > > > Reviews comments fixes for MaxCoveringFactResolver and LeastPartitionResolver -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Attachment: LENS-1410.patch > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1410.patch, LENS-1410.patch, LENS-1410.patch > > > Make the filter while getting a list of partitions mandatory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Attachment: LENS-1410.patch > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1410.patch, LENS-1410.patch > > > Make the filter while getting a list of partitions mandatory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Attachment: (was: LENS-1410.patch) > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1410.patch > > > Make the filter while getting a list of partitions mandatory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Attachment: LENS-1410.patch > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1410.patch, LENS-1410.patch > > > Make the filter while getting a list of partitions mandatory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Status: Patch Available (was: Open) > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1410.patch > > > Make the filter while getting a list of partitions mandatory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1410) Make the filter while getting a list of partitions mandatory
[ https://issues.apache.org/jira/browse/LENS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1410: -- Attachment: LENS-1410.patch > Make the filter while getting a list of partitions mandatory > - > > Key: LENS-1410 > URL: https://issues.apache.org/jira/browse/LENS-1410 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1410.patch > > > Make the filter while getting a list of partitions mandatory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1409) Remove Unknown.log file before lens startup
[ https://issues.apache.org/jira/browse/LENS-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1409: -- Attachment: default_query_id.patch > Remove Unknown.log file before lens startup > --- > > Key: LENS-1409 > URL: https://issues.apache.org/jira/browse/LENS-1409 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: default_query_id.patch > > > unknown.log is created and appended if queryId is not defined. it is reaching > a large size. We can delete it while lens-server startup. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1409) Remove Unknown.log file before lens startup
[ https://issues.apache.org/jira/browse/LENS-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1409: -- Status: Patch Available (was: Open) > Remove Unknown.log file before lens startup > --- > > Key: LENS-1409 > URL: https://issues.apache.org/jira/browse/LENS-1409 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: default_query_id.patch > > > unknown.log is created and appended if queryId is not defined. it is reaching > a large size. We can delete it while lens-server startup. -- 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 ] Lavkesh Lahngir updated LENS-1391: -- Status: Patch Available (was: Open) > 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-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 ] Lavkesh Lahngir updated LENS-1391: -- Attachment: LENS-1391.patch > 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-1393) Update the javax mail version to current
[ https://issues.apache.org/jira/browse/LENS-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1393: -- Status: Patch Available (was: Open) > 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 > Attachments: LENS-1393.patch > > > 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] [Created] (LENS-1393) Update the javax mail version to current
Lavkesh Lahngir created LENS-1393: - Summary: 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] [Created] (LENS-1391) Review comments for MaxCoveringFactResolver and LeastPartitionResolver On brach lens-1381
Lavkesh Lahngir created LENS-1391: - Summary: Review comments for MaxCoveringFactResolver and LeastPartitionResolver On brach 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] [Updated] (LENS-1390) Bug fixes after LENS-1386
[ https://issues.apache.org/jira/browse/LENS-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1390: -- Status: Patch Available (was: Open) > Bug fixes after LENS-1386 > - > > Key: LENS-1390 > URL: https://issues.apache.org/jira/browse/LENS-1390 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1390.patch > > > Few necessary fixes to complete Lens-1386 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1390) Bug fixes after LENS-1386
[ https://issues.apache.org/jira/browse/LENS-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1390: -- Attachment: LENS-1390.patch > Bug fixes after LENS-1386 > - > > Key: LENS-1390 > URL: https://issues.apache.org/jira/browse/LENS-1390 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1390.patch > > > Few necessary fixes to complete Lens-1386 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (LENS-1390) Bug fixes after LENS-1386
Lavkesh Lahngir created LENS-1390: - Summary: Bug fixes after LENS-1386 Key: LENS-1390 URL: https://issues.apache.org/jira/browse/LENS-1390 Project: Apache Lens Issue Type: Bug Components: server Reporter: Lavkesh Lahngir Assignee: Lavkesh Lahngir Few necessary fixes to complete Lens-1386 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1386) Add support for separate tables for update periods in one storage
[ https://issues.apache.org/jira/browse/LENS-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1386: -- Status: Patch Available (was: Open) > Add support for separate tables for update periods in one storage > - > > Key: LENS-1386 > URL: https://issues.apache.org/jira/browse/LENS-1386 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1386.patch > > > Xsd and Metastore changes: > (1) New Xsd construct > (2) Create Fact Changes > (3) CubeMetastoreClient changes for update period table name > (4) Validation that TableDescription should only be available at either table > level or at update period level -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1386) Add support for separate tables for update periods in one storage
[ https://issues.apache.org/jira/browse/LENS-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1386: -- Attachment: LENS-1386.patch > Add support for separate tables for update periods in one storage > - > > Key: LENS-1386 > URL: https://issues.apache.org/jira/browse/LENS-1386 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: LENS-1386.patch > > > Xsd and Metastore changes: > (1) New Xsd construct > (2) Create Fact Changes > (3) CubeMetastoreClient changes for update period table name > (4) Validation that TableDescription should only be available at either table > level or at update period level -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (LENS-1386) Fact Schema change to support all update periods in one storage
[ https://issues.apache.org/jira/browse/LENS-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1386: -- Summary: Fact Schema change to support all update periods in one storage (was: Vertica Fact Schema change to support all update periods in one storage) > Fact Schema change to support all update periods in one storage > --- > > Key: LENS-1386 > URL: https://issues.apache.org/jira/browse/LENS-1386 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > > Xsd and Metastore changes: > (1) New Xsd construct > (2) Create Fact Changes > (3) CubeMetastoreClient changes for update period table name > (4) Validation that TableDescription should only be available at either table > level or at update period level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1386) Vertica Fact Schema change to support all update periods in one storage
Lavkesh Lahngir created LENS-1386: - Summary: Vertica Fact Schema change to support all update periods in one storage Key: LENS-1386 URL: https://issues.apache.org/jira/browse/LENS-1386 Project: Apache Lens Issue Type: Task Reporter: Lavkesh Lahngir Assignee: Lavkesh Lahngir Xsd and Metastore changes: (1) New Xsd construct (2) Create Fact Changes (3) CubeMetastoreClient changes for update period table name (4) Validation that TableDescription should only be available at either table level or at update period level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1383) Add support for multiple table descriptors inside a storage.
[ https://issues.apache.org/jira/browse/LENS-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1383: -- Summary: Add support for multiple table descriptors inside a storage. (was: Add support for multiple table descriptor inside a storage. ) > Add support for multiple table descriptors inside a storage. > - > > Key: LENS-1383 > URL: https://issues.apache.org/jira/browse/LENS-1383 > Project: Apache Lens > Issue Type: New Feature >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1383) Add support for multiple table descriptor inside a storage.
Lavkesh Lahngir created LENS-1383: - Summary: Add support for multiple table descriptor inside a storage. Key: LENS-1383 URL: https://issues.apache.org/jira/browse/LENS-1383 Project: Apache Lens Issue Type: New Feature Reporter: Lavkesh Lahngir Assignee: Lavkesh Lahngir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1376) Retry framework for queries should separate server retries and driver retries
Lavkesh Lahngir created LENS-1376: - Summary: Retry framework for queries should separate server retries and driver retries Key: LENS-1376 URL: https://issues.apache.org/jira/browse/LENS-1376 Project: Apache Lens Issue Type: Bug Reporter: Lavkesh Lahngir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (LENS-1375) ImmediateRetryHandler.hasExhaustedRetries() should return true when failcount is equal to number of retries
[ https://issues.apache.org/jira/browse/LENS-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir reassigned LENS-1375: - Assignee: Lavkesh Lahngir > ImmediateRetryHandler.hasExhaustedRetries() should return true when failcount > is equal to number of retries > --- > > Key: LENS-1375 > URL: https://issues.apache.org/jira/browse/LENS-1375 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1375) ImmediateRetryHandler.hasExhaustedRetries() should return true when failcount is equal to number of retries
Lavkesh Lahngir created LENS-1375: - Summary: ImmediateRetryHandler.hasExhaustedRetries() should return true when failcount is equal to number of retries Key: LENS-1375 URL: https://issues.apache.org/jira/browse/LENS-1375 Project: Apache Lens Issue Type: Bug Reporter: Lavkesh Lahngir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1371) Add a substring based retry policy for failures
[ https://issues.apache.org/jira/browse/LENS-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1371: -- Attachment: 0001-Retry-policy.patch > Add a substring based retry policy for failures > --- > > Key: LENS-1371 > URL: https://issues.apache.org/jira/browse/LENS-1371 > Project: Apache Lens > Issue Type: New Feature >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Retry-patch.patch, 0001-Retry-policy.patch, > 0001-Retry-policy.patch, 0001-Retry-policy.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1371) Add a substring based retry policy for failures
[ https://issues.apache.org/jira/browse/LENS-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1371: -- Status: Patch Available (was: Open) > Add a substring based retry policy for failures > --- > > Key: LENS-1371 > URL: https://issues.apache.org/jira/browse/LENS-1371 > Project: Apache Lens > Issue Type: New Feature >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Retry-patch.patch, 0001-Retry-policy.patch, > 0001-Retry-policy.patch, 0001-Retry-policy.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1371) Add a substring based retry policy for failures
[ https://issues.apache.org/jira/browse/LENS-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1371: -- Status: Patch Available (was: Open) > Add a substring based retry policy for failures > --- > > Key: LENS-1371 > URL: https://issues.apache.org/jira/browse/LENS-1371 > Project: Apache Lens > Issue Type: New Feature >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Retry-patch.patch, 0001-Retry-policy.patch, > 0001-Retry-policy.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1371) Add a substring based retry policy for failures
[ https://issues.apache.org/jira/browse/LENS-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1371: -- Status: Open (was: Patch Available) > Add a substring based retry policy for failures > --- > > Key: LENS-1371 > URL: https://issues.apache.org/jira/browse/LENS-1371 > Project: Apache Lens > Issue Type: New Feature >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Retry-patch.patch, 0001-Retry-policy.patch, > 0001-Retry-policy.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1371) Add a substring based retry policy for failures
[ https://issues.apache.org/jira/browse/LENS-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1371: -- Attachment: 0001-Retry-policy.patch > Add a substring based retry policy for failures > --- > > Key: LENS-1371 > URL: https://issues.apache.org/jira/browse/LENS-1371 > Project: Apache Lens > Issue Type: New Feature >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Retry-patch.patch, 0001-Retry-policy.patch, > 0001-Retry-policy.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1371) Add a substring based retry policy for failures
[ https://issues.apache.org/jira/browse/LENS-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1371: -- Attachment: 0001-Retry-policy.patch > Add a substring based retry policy for failures > --- > > Key: LENS-1371 > URL: https://issues.apache.org/jira/browse/LENS-1371 > Project: Apache Lens > Issue Type: New Feature >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Retry-patch.patch, 0001-Retry-policy.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1371) Add a substring based retry policy for failures
[ https://issues.apache.org/jira/browse/LENS-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1371: -- Attachment: 0001-Retry-patch.patch > Add a substring based retry policy for failures > --- > > Key: LENS-1371 > URL: https://issues.apache.org/jira/browse/LENS-1371 > Project: Apache Lens > Issue Type: New Feature >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Retry-patch.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1371) Add a substring based retry policy for failures
[ https://issues.apache.org/jira/browse/LENS-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1371: -- Status: Patch Available (was: Open) > Add a substring based retry policy for failures > --- > > Key: LENS-1371 > URL: https://issues.apache.org/jira/browse/LENS-1371 > Project: Apache Lens > Issue Type: New Feature >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Retry-patch.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1352) Write JDBC driver Retry policy to recover queries lost after lens restart
[ https://issues.apache.org/jira/browse/LENS-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1352: -- Issue Type: Sub-task (was: Task) Parent: LENS-1371 > Write JDBC driver Retry policy to recover queries lost after lens restart > - > > Key: LENS-1352 > URL: https://issues.apache.org/jira/browse/LENS-1352 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Rajat Khandelwal >Assignee: Lavkesh Lahngir > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1353) Write HiveDriver retry policy to recover queries lost due to hive server restart
[ https://issues.apache.org/jira/browse/LENS-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1353: -- Issue Type: Sub-task (was: Task) Parent: LENS-1371 > Write HiveDriver retry policy to recover queries lost due to hive server > restart > > > Key: LENS-1353 > URL: https://issues.apache.org/jira/browse/LENS-1353 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Rajat Khandelwal >Assignee: Lavkesh Lahngir > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1371) Add a substring based retry policy for failures
Lavkesh Lahngir created LENS-1371: - Summary: Add a substring based retry policy for failures Key: LENS-1371 URL: https://issues.apache.org/jira/browse/LENS-1371 Project: Apache Lens Issue Type: New Feature Reporter: Lavkesh Lahngir Assignee: Lavkesh Lahngir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Attachment: 0001-data-delay.patch > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Data-dealy.patch, 0001-data-delay.patch, > data-delay.patch, data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1361: -- Status: Patch Available (was: Open) > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-DB-fixes.patch, ignore-db.patch, ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1361: -- Attachment: 0001-DB-fixes.patch > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-DB-fixes.patch, ignore-db.patch, ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588586#comment-15588586 ] Lavkesh Lahngir commented on LENS-1361: --- Init() should throw an error if there are errors. Table creation will not throw an error, that will result in internal server error while API calls. > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: ignore-db.patch, ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1361: -- Attachment: ignore-db.patch > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: ignore-db.patch, ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1361: -- Attachment: (was: ignore-db.patch) > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1361: -- Status: Open (was: Patch Available) > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1361: -- Attachment: ignore-db.patch > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: ignore-db.patch, ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1361: -- Status: Patch Available (was: In Progress) > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1361: -- Attachment: ignore-db.patch > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (LENS-1361) Ignore DB failure while scheduler startup.
[ https://issues.apache.org/jira/browse/LENS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-1361 started by Lavkesh Lahngir. - > Ignore DB failure while scheduler startup. > -- > > Key: LENS-1361 > URL: https://issues.apache.org/jira/browse/LENS-1361 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: ignore-db.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Status: Patch Available (was: Open) > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Data-dealy.patch, data-delay.patch, > data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Attachment: 0001-Data-dealy.patch > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Data-dealy.patch, data-delay.patch, > data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1285) Adding unit tests for scheduler API
[ https://issues.apache.org/jira/browse/LENS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1285: -- Attachment: 0001-API-tests.patch > Adding unit tests for scheduler API > --- > > Key: LENS-1285 > URL: https://issues.apache.org/jira/browse/LENS-1285 > Project: Apache Lens > Issue Type: Test >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > Attachments: 0001-API-tests.patch, 0001-Api-tests.patch, > 0001-Resource-tests.patch, Scheduler-API-tests.patch, > Scheduler-API-tests.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1285) Adding unit tests for scheduler API
[ https://issues.apache.org/jira/browse/LENS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1285: -- Status: Patch Available (was: Open) > Adding unit tests for scheduler API > --- > > Key: LENS-1285 > URL: https://issues.apache.org/jira/browse/LENS-1285 > Project: Apache Lens > Issue Type: Test >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > Attachments: 0001-API-tests.patch, 0001-Api-tests.patch, > 0001-Resource-tests.patch, Scheduler-API-tests.patch, > Scheduler-API-tests.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Status: Patch Available (was: Open) > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: data-delay.patch, data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Attachment: data-delay.patch > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: data-delay.patch, data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15547935#comment-15547935 ] Lavkesh Lahngir commented on LENS-1327: --- Yeah. It's not a necessary condition. > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1285) Adding unit tests for scheduler API
[ https://issues.apache.org/jira/browse/LENS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1285: -- Attachment: 0001-Resource-tests.patch > Adding unit tests for scheduler API > --- > > Key: LENS-1285 > URL: https://issues.apache.org/jira/browse/LENS-1285 > Project: Apache Lens > Issue Type: Test >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Resource-tests.patch, Scheduler-API-tests.patch, > Scheduler-API-tests.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1285) Adding unit tests for scheduler API
[ https://issues.apache.org/jira/browse/LENS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1285: -- Status: Patch Available (was: Open) > Adding unit tests for scheduler API > --- > > Key: LENS-1285 > URL: https://issues.apache.org/jira/browse/LENS-1285 > Project: Apache Lens > Issue Type: Test >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-Resource-tests.patch, Scheduler-API-tests.patch, > Scheduler-API-tests.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542175#comment-15542175 ] Lavkesh Lahngir edited comment on LENS-1327 at 10/4/16 10:06 AM: - The new flow for the instance life cycle is Launching -> waiting -> launching -> .. -> waiting -> Launching -> Launched -> Running. It will keep coming back to the waiting state if the data is not present. was (Author: lavkesh): The new flow for the instance life cycle is Launching -> waiting-> launching -> .. -> waiting -> Launching -> Launched -> Running. It will keep coming back to the waiting state if the data is not present. > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1326) session/sessions API returning no data on GUI/API though there are active sessions
[
https://issues.apache.org/jira/browse/LENS-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1326:
--
Attachment: session-default-value.patch
> session/sessions API returning no data on GUI/API though there are active
> sessions
> --
>
> Key: LENS-1326
> URL: https://issues.apache.org/jira/browse/LENS-1326
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Puneet Gupta
>Assignee: Lavkesh Lahngir
> Attachments: getsession-error.patch, getsession-error.patch,
> session-default-value.patch, session-default-value.patch
>
>
> The lens GUI and API is showing no sessions via sessions REST end point.
> Server metrics are showing active sessions though.
> {noformat}
> "org.apache.lens.server.api.session.SessionService.active-sessions" : {
> "value" : 5324
>},
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1326) session/sessions API returning no data on GUI/API though there are active sessions
[
https://issues.apache.org/jira/browse/LENS-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1326:
--
Attachment: session-default-value.patch
> session/sessions API returning no data on GUI/API though there are active
> sessions
> --
>
> Key: LENS-1326
> URL: https://issues.apache.org/jira/browse/LENS-1326
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Puneet Gupta
>Assignee: Lavkesh Lahngir
> Attachments: getsession-error.patch, getsession-error.patch,
> session-default-value.patch
>
>
> The lens GUI and API is showing no sessions via sessions REST end point.
> Server metrics are showing active sessions though.
> {noformat}
> "org.apache.lens.server.api.session.SessionService.active-sessions" : {
> "value" : 5324
>},
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542175#comment-15542175 ] Lavkesh Lahngir commented on LENS-1327: --- The new flow for the instance life cycle is Launching -> waiting-> launching -> .. -> waiting -> Launching -> Launched -> Running. It will keep coming back to the waiting state if the data is not present. > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Status: Patch Available (was: Open) > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Attachment: data-delay.patch > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: data-delay.patch, data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Status: Patch Available (was: Open) > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: data-delay.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1326) session/sessions API returning no data on GUI/API though there are active sessions
[
https://issues.apache.org/jira/browse/LENS-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542025#comment-15542025
]
Lavkesh Lahngir commented on LENS-1326:
---
One possible scenario is just after the hive restart.
SESSION_MAP will still contain session handle, but the Hive server won't be
able to get the session after the Hive restart.
> session/sessions API returning no data on GUI/API though there are active
> sessions
> --
>
> Key: LENS-1326
> URL: https://issues.apache.org/jira/browse/LENS-1326
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Puneet Gupta
>Assignee: Lavkesh Lahngir
> Attachments: getsession-error.patch, getsession-error.patch
>
>
> The lens GUI and API is showing no sessions via sessions REST end point.
> Server metrics are showing active sessions though.
> {noformat}
> "org.apache.lens.server.api.session.SessionService.active-sessions" : {
> "value" : 5324
>},
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1326) session/sessions API returning no data on GUI/API though there are active sessions
[
https://issues.apache.org/jira/browse/LENS-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1326:
--
Attachment: getsession-error.patch
> session/sessions API returning no data on GUI/API though there are active
> sessions
> --
>
> Key: LENS-1326
> URL: https://issues.apache.org/jira/browse/LENS-1326
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Puneet Gupta
>Assignee: Lavkesh Lahngir
> Attachments: getsession-error.patch, getsession-error.patch
>
>
> The lens GUI and API is showing no sessions via sessions REST end point.
> Server metrics are showing active sessions though.
> {noformat}
> "org.apache.lens.server.api.session.SessionService.active-sessions" : {
> "value" : 5324
>},
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1326) session/sessions API returning no data on GUI/API though there are active sessions
[
https://issues.apache.org/jira/browse/LENS-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1326:
--
Status: Patch Available (was: Open)
> session/sessions API returning no data on GUI/API though there are active
> sessions
> --
>
> Key: LENS-1326
> URL: https://issues.apache.org/jira/browse/LENS-1326
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Puneet Gupta
>Assignee: Lavkesh Lahngir
> Attachments: getsession-error.patch
>
>
> The lens GUI and API is showing no sessions via sessions REST end point.
> Server metrics are showing active sessions though.
> {noformat}
> "org.apache.lens.server.api.session.SessionService.active-sessions" : {
> "value" : 5324
>},
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1326) session/sessions API returning no data on GUI/API though there are active sessions
[
https://issues.apache.org/jira/browse/LENS-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1326:
--
Attachment: getsession-error.patch
> session/sessions API returning no data on GUI/API though there are active
> sessions
> --
>
> Key: LENS-1326
> URL: https://issues.apache.org/jira/browse/LENS-1326
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Puneet Gupta
>Assignee: Lavkesh Lahngir
> Attachments: getsession-error.patch
>
>
> The lens GUI and API is showing no sessions via sessions REST end point.
> Server metrics are showing active sessions though.
> {noformat}
> "org.apache.lens.server.api.session.SessionService.active-sessions" : {
> "value" : 5324
>},
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (LENS-1267) Instances which are in waiting state while restart are not getting resumed
[ https://issues.apache.org/jira/browse/LENS-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir resolved LENS-1267. --- Resolution: Fixed > Instances which are in waiting state while restart are not getting resumed > -- > > Key: LENS-1267 > URL: https://issues.apache.org/jira/browse/LENS-1267 > Project: Apache Lens > Issue Type: Bug >Reporter: Archana H >Assignee: Lavkesh Lahngir > > The Scheduler can not recover from restarting when it was in the middle of > launching a query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1320) Limit the maximum number of scheduled jobs per user
[ https://issues.apache.org/jira/browse/LENS-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1320: -- Attachment: 0001-job_validataion.patch > Limit the maximum number of scheduled jobs per user > --- > > Key: LENS-1320 > URL: https://issues.apache.org/jira/browse/LENS-1320 > Project: Apache Lens > Issue Type: Improvement >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: 0001-job_validataion.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Issue Type: Sub-task (was: Improvement) Parent: LENS-124 > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1327) Handle Data delay for scheduled jobs
[ https://issues.apache.org/jira/browse/LENS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1327: -- Summary: Handle Data delay for scheduled jobs (was: Handle Data delay) > Handle Data delay for scheduled jobs > > > Key: LENS-1327 > URL: https://issues.apache.org/jira/browse/LENS-1327 > Project: Apache Lens > Issue Type: Improvement >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1327) Handle Data delay
Lavkesh Lahngir created LENS-1327: - Summary: Handle Data delay Key: LENS-1327 URL: https://issues.apache.org/jira/browse/LENS-1327 Project: Apache Lens Issue Type: Improvement Reporter: Lavkesh Lahngir Assignee: Lavkesh Lahngir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1320) Limit the maximum number of scheduled jobs per user
Lavkesh Lahngir created LENS-1320: - Summary: Limit the maximum number of scheduled jobs per user Key: LENS-1320 URL: https://issues.apache.org/jira/browse/LENS-1320 Project: Apache Lens Issue Type: Improvement Reporter: Lavkesh Lahngir Assignee: Lavkesh Lahngir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1286) Handle Lens server restart
[ https://issues.apache.org/jira/browse/LENS-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1286: -- Attachment: restart.patch > Handle Lens server restart > -- > > Key: LENS-1286 > URL: https://issues.apache.org/jira/browse/LENS-1286 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: restart.patch > > > Scheduled events which are generated by AlarmService for scheduling are > processed by a SchedulerEventListener thread. > These steps are performed after receiving a scheduled event: > 1. Get the job stored in the SchedulerDAO > 2. Create a session with job owner and fill the session conf. > 3. Create the instance if it is not a rerun otherwise get the instance from > the store. > 4. Create a Run instance. > 5. Store instance (if not present) and run to the store. > 6. Launch the query. > 7. Update the run with the latest information. > 8. If there is a failure in query launch then update the run status to be > failed. > While EventListener is processing the event, it can be closed during the > shutdown of scheduler service. Closing the thread can cause operations to be > incomplete. > There are these stages where the thread can be interrupted: > 1. Shutdown just after the alarm Event is fired and received: > In this case, we won't have any entry for the instance run in the store. This > will cause a hole in the list of instances. > 2. Shutdown before query launch. > In this case, at least we will have an entry in the table and status as NEW. > 3. Shutdown after query launch. > In this case, the status won't be updated, and even if the query is launched > we will have no information about the handle. When this happens the > scheduled status will remain NEW > Of all the scenarios above, the first one is kind of annoying because there > is no way to generate the event from Alarm Service again if it is already > triggered. > Second and third scenarios can be handled manually by killing the instance > and re-running it. > Apart from the scheduler event listener thread, we have another thread which > processes the query end event which works as follows: > 1. Receive the event and check if this is a scheduled query. > 2. Check the final status of the query and set it as the instance status. > If a shutdown happens after receiving the query end event, it will cause the > status to remain as RUNNING. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1286) Handle Lens server restart
[ https://issues.apache.org/jira/browse/LENS-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1286: -- Status: Patch Available (was: Open) > Handle Lens server restart > -- > > Key: LENS-1286 > URL: https://issues.apache.org/jira/browse/LENS-1286 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: restart.patch > > > Scheduled events which are generated by AlarmService for scheduling are > processed by a SchedulerEventListener thread. > These steps are performed after receiving a scheduled event: > 1. Get the job stored in the SchedulerDAO > 2. Create a session with job owner and fill the session conf. > 3. Create the instance if it is not a rerun otherwise get the instance from > the store. > 4. Create a Run instance. > 5. Store instance (if not present) and run to the store. > 6. Launch the query. > 7. Update the run with the latest information. > 8. If there is a failure in query launch then update the run status to be > failed. > While EventListener is processing the event, it can be closed during the > shutdown of scheduler service. Closing the thread can cause operations to be > incomplete. > There are these stages where the thread can be interrupted: > 1. Shutdown just after the alarm Event is fired and received: > In this case, we won't have any entry for the instance run in the store. This > will cause a hole in the list of instances. > 2. Shutdown before query launch. > In this case, at least we will have an entry in the table and status as NEW. > 3. Shutdown after query launch. > In this case, the status won't be updated, and even if the query is launched > we will have no information about the handle. When this happens the > scheduled status will remain NEW > Of all the scenarios above, the first one is kind of annoying because there > is no way to generate the event from Alarm Service again if it is already > triggered. > Second and third scenarios can be handled manually by killing the instance > and re-running it. > Apart from the scheduler event listener thread, we have another thread which > processes the query end event which works as follows: > 1. Receive the event and check if this is a scheduled query. > 2. Check the final status of the query and set it as the instance status. > If a shutdown happens after receiving the query end event, it will cause the > status to remain as RUNNING. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1285) Adding unit tests for scheduler API
[ https://issues.apache.org/jira/browse/LENS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1285: -- Attachment: Scheduler-API-tests.patch > Adding unit tests for scheduler API > --- > > Key: LENS-1285 > URL: https://issues.apache.org/jira/browse/LENS-1285 > Project: Apache Lens > Issue Type: Test >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-API-tests.patch, Scheduler-API-tests.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1285) Adding unit tests for scheduler API
[ https://issues.apache.org/jira/browse/LENS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1285: -- Status: Patch Available (was: Open) > Adding unit tests for scheduler API > --- > > Key: LENS-1285 > URL: https://issues.apache.org/jira/browse/LENS-1285 > Project: Apache Lens > Issue Type: Test >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-API-tests.patch, Scheduler-API-tests.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1298) Thread should have ability to wait for Events to be processed
[
https://issues.apache.org/jira/browse/LENS-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1298:
--
Status: Patch Available (was: Reopened)
> Thread should have ability to wait for Events to be processed
> -
>
> Key: LENS-1298
> URL: https://issues.apache.org/jira/browse/LENS-1298
> Project: Apache Lens
> Issue Type: New Feature
>Reporter: Lavkesh Lahngir
>Assignee: Lavkesh Lahngir
> Fix For: 2.7
>
> Attachments: notifySync.patch, notifysync-bug.patch
>
>
> When a thread notifies event service to process any event, it should have a
> way to wait for it to be finished.
> {code}
> LensEvent event = new LensEvent();
> synchronized(event) {
>eventservice.notifyEvent(event);
>event.wait();
> }
> {code}
> The EventHandler will do a notifyall() on the event it is done handling.
> {code}
> public void run() {
> try {
> Class evtClass = event.getClass();
> // Call listeners directly listening for this event type
> handleEvent(eventListeners.get(evtClass), event);
> Class superClass = evtClass.getSuperclass();
> // Call listeners which listen of super types of this event type
> while (LensEvent.class.isAssignableFrom(superClass)) {
> if (eventListeners.containsKey(superClass)) {
> handleEvent(eventListeners.get(superClass), event);
> }
> superClass = superClass.getSuperclass();
> }
> } finally {
> synchronized (event) {
> event.notifyAll();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (LENS-1298) Thread should have ability to wait for Events to be processed
[
https://issues.apache.org/jira/browse/LENS-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469659#comment-15469659
]
Lavkesh Lahngir edited comment on LENS-1298 at 9/7/16 5:56 AM:
---
In test case the EventListener should not be Async.
was (Author: lavkesh):
In test case there EventListener Should not be Async.
> Thread should have ability to wait for Events to be processed
> -
>
> Key: LENS-1298
> URL: https://issues.apache.org/jira/browse/LENS-1298
> Project: Apache Lens
> Issue Type: New Feature
>Reporter: Lavkesh Lahngir
>Assignee: Lavkesh Lahngir
> Fix For: 2.7
>
> Attachments: notifySync.patch
>
>
> When a thread notifies event service to process any event, it should have a
> way to wait for it to be finished.
> {code}
> LensEvent event = new LensEvent();
> synchronized(event) {
>eventservice.notifyEvent(event);
>event.wait();
> }
> {code}
> The EventHandler will do a notifyall() on the event it is done handling.
> {code}
> public void run() {
> try {
> Class evtClass = event.getClass();
> // Call listeners directly listening for this event type
> handleEvent(eventListeners.get(evtClass), event);
> Class superClass = evtClass.getSuperclass();
> // Call listeners which listen of super types of this event type
> while (LensEvent.class.isAssignableFrom(superClass)) {
> if (eventListeners.containsKey(superClass)) {
> handleEvent(eventListeners.get(superClass), event);
> }
> superClass = superClass.getSuperclass();
> }
> } finally {
> synchronized (event) {
> event.notifyAll();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (LENS-1298) Thread should have ability to wait for Events to be processed
[
https://issues.apache.org/jira/browse/LENS-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458593#comment-15458593
]
Lavkesh Lahngir commented on LENS-1298:
---
We have taken slight different approach than originally proposed.
We can directly call the handler.run() from the notifySync() method.
> Thread should have ability to wait for Events to be processed
> -
>
> Key: LENS-1298
> URL: https://issues.apache.org/jira/browse/LENS-1298
> Project: Apache Lens
> Issue Type: New Feature
>Reporter: Lavkesh Lahngir
>Assignee: Lavkesh Lahngir
> Attachments: notifySync.patch
>
>
> When a thread notifies event service to process any event, it should have a
> way to wait for it to be finished.
> {code}
> LensEvent event = new LensEvent();
> synchronized(event) {
>eventservice.notifyEvent(event);
>event.wait();
> }
> {code}
> The EventHandler will do a notifyall() on the event it is done handling.
> {code}
> public void run() {
> try {
> Class evtClass = event.getClass();
> // Call listeners directly listening for this event type
> handleEvent(eventListeners.get(evtClass), event);
> Class superClass = evtClass.getSuperclass();
> // Call listeners which listen of super types of this event type
> while (LensEvent.class.isAssignableFrom(superClass)) {
> if (eventListeners.containsKey(superClass)) {
> handleEvent(eventListeners.get(superClass), event);
> }
> superClass = superClass.getSuperclass();
> }
> } finally {
> synchronized (event) {
> event.notifyAll();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1298) Thread should have ability to wait for Events to be processed
[
https://issues.apache.org/jira/browse/LENS-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1298:
--
Attachment: notifySync.patch
> Thread should have ability to wait for Events to be processed
> -
>
> Key: LENS-1298
> URL: https://issues.apache.org/jira/browse/LENS-1298
> Project: Apache Lens
> Issue Type: New Feature
>Reporter: Lavkesh Lahngir
>Assignee: Lavkesh Lahngir
> Attachments: notifySync.patch
>
>
> When a thread notifies event service to process any event, it should have a
> way to wait for it to be finished.
> {code}
> LensEvent event = new LensEvent();
> synchronized(event) {
>eventservice.notifyEvent(event);
>event.wait();
> }
> {code}
> The EventHandler will do a notifyall() on the event it is done handling.
> {code}
> public void run() {
> try {
> Class evtClass = event.getClass();
> // Call listeners directly listening for this event type
> handleEvent(eventListeners.get(evtClass), event);
> Class superClass = evtClass.getSuperclass();
> // Call listeners which listen of super types of this event type
> while (LensEvent.class.isAssignableFrom(superClass)) {
> if (eventListeners.containsKey(superClass)) {
> handleEvent(eventListeners.get(superClass), event);
> }
> superClass = superClass.getSuperclass();
> }
> } finally {
> synchronized (event) {
> event.notifyAll();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1306) Wrong hsql query is created when there are multiple facts and no dimension.
[ https://issues.apache.org/jira/browse/LENS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1306: -- Attachment: hsql.patch > Wrong hsql query is created when there are multiple facts and no dimension. > > > Key: LENS-1306 > URL: https://issues.apache.org/jira/browse/LENS-1306 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: hsql.patch, hsql.patch, multifact-fix.patch > > > When there are more than 2 fact tables resolved and there are no dimension, > It results into wrong HSQL query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1306) Wrong hsql query is created when there are multiple facts and no dimension.
[ https://issues.apache.org/jira/browse/LENS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1306: -- Attachment: hsql.patch > Wrong hsql query is created when there are multiple facts and no dimension. > > > Key: LENS-1306 > URL: https://issues.apache.org/jira/browse/LENS-1306 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: hsql.patch, hsql.patch, multifact-fix.patch > > > When there are more than 2 fact tables resolved and there are no dimension, > It results into wrong HSQL query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1306) Wrong hsql query is created when there are multiple facts and no dimension.
[ https://issues.apache.org/jira/browse/LENS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1306: -- Status: Patch Available (was: Open) > Wrong hsql query is created when there are multiple facts and no dimension. > > > Key: LENS-1306 > URL: https://issues.apache.org/jira/browse/LENS-1306 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: multifact-fix.patch > > > When there are more than 2 fact tables resolved and there are no dimension, > It results into wrong HSQL query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
