[jira] [Updated] (LENS-987) [Server] AlarmService for scheduling time based queries
[ https://issues.apache.org/jira/browse/LENS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-987: - Attachment: Diff.html Attached: diff of the test case to make it work Refer to https://reviews.apache.org/r/48541/ > [Server] AlarmService for scheduling time based queries > --- > > Key: LENS-987 > URL: https://issues.apache.org/jira/browse/LENS-987 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Ajay Yadava >Assignee: Ajay Yadava > Fix For: 2.6 > > Attachments: Diff.html, LENS-987-v2.patch > > > AlarmService to trigger execution of queries according to a given schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1143: -- Status: Patch Available (was: Open) > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Fix For: 2.6 > > Attachments: 0001-Changes-in-the-test-case.patch, > 0001-Fixing-Text-case-for-duplicate-queries.patch, 0001-Test-case-fix.patch, > fix-test-case-1.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1143: -- Attachment: fix-test-case.patch > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Fix For: 2.6 > > Attachments: 0001-Changes-in-the-test-case.patch, > 0001-Fixing-Text-case-for-duplicate-queries.patch, 0001-Test-case-fix.patch, > fix-test-case.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1143: -- Attachment: fix-test-case-1.patch > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Fix For: 2.6 > > Attachments: 0001-Changes-in-the-test-case.patch, > 0001-Fixing-Text-case-for-duplicate-queries.patch, 0001-Test-case-fix.patch, > fix-test-case-1.patch, fix-test-case.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1143: -- Attachment: (was: fix-test-case.patch) > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Fix For: 2.6 > > Attachments: 0001-Changes-in-the-test-case.patch, > 0001-Fixing-Text-case-for-duplicate-queries.patch, 0001-Test-case-fix.patch, > fix-test-case-1.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1143: -- Attachment: 0001-Changes-in-the-test-case.patch > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Fix For: 2.6 > > Attachments: 0001-Changes-in-the-test-case.patch, > 0001-Fixing-Text-case-for-duplicate-queries.patch, 0001-Test-case-fix.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-987) [Server] AlarmService for scheduling time based queries
[ https://issues.apache.org/jira/browse/LENS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-987: - Attachment: alarmservice-test-fix.patch > [Server] AlarmService for scheduling time based queries > --- > > Key: LENS-987 > URL: https://issues.apache.org/jira/browse/LENS-987 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Ajay Yadava >Assignee: Ajay Yadava > Fix For: 2.6 > > Attachments: Diff.html, LENS-987-v2.patch, alarmservice-test-fix.patch > > > AlarmService to trigger execution of queries according to a given schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-987) [Server] AlarmService for scheduling time based queries
[ https://issues.apache.org/jira/browse/LENS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-987: - Status: Patch Available (was: Open) > [Server] AlarmService for scheduling time based queries > --- > > Key: LENS-987 > URL: https://issues.apache.org/jira/browse/LENS-987 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Ajay Yadava >Assignee: Ajay Yadava > Fix For: 2.6 > > Attachments: Diff.html, LENS-987-v2.patch, alarmservice-test-fix.patch > > > AlarmService to trigger execution of queries according to a given schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1143: -- Attachment: 0001-Test-case-fix.patch > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Fix For: 2.6 > > Attachments: 0001-Fixing-Text-case-for-duplicate-queries.patch, > 0001-Test-case-fix.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1143: -- Status: Patch Available (was: Reopened) > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Fix For: 2.6 > > Attachments: 0001-Fixing-Text-case-for-duplicate-queries.patch, > 0001-Test-case-fix.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (LENS-988) [Server] StateStore for LensScheduler
[ https://issues.apache.org/jira/browse/LENS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir reassigned LENS-988: Assignee: Lavkesh Lahngir (was: Ajay Yadava) > [Server] StateStore for LensScheduler > - > > Key: LENS-988 > URL: https://issues.apache.org/jira/browse/LENS-988 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Ajay Yadava >Assignee: Lavkesh Lahngir > > Dividing server side component into smaller tasks. This task is for creating > a persistent store for lens scheduler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1201) [Code cleanup] Move API classes to correct place.
Lavkesh Lahngir created LENS-1201: - Summary: [Code cleanup] Move API classes to correct place. Key: LENS-1201 URL: https://issues.apache.org/jira/browse/LENS-1201 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-1201) [Code cleanup] Move API classes to correct place.
[ https://issues.apache.org/jira/browse/LENS-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1201: -- Attachment: code_cleanup.patch > [Code cleanup] Move API classes to correct place. > -- > > Key: LENS-1201 > URL: https://issues.apache.org/jira/browse/LENS-1201 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: code_cleanup.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1195) State Machine for Jobs and Job instances
Lavkesh Lahngir created LENS-1195: - Summary: State Machine for Jobs and Job instances Key: LENS-1195 URL: https://issues.apache.org/jira/browse/LENS-1195 Project: Apache Lens Issue Type: Sub-task Reporter: Lavkesh Lahngir Assignee: Ajay Yadava Job's state -> NEW, SCHEDULED, EXPIRED, PAUSED. Job's instance -> WAITING, LAUNCHED, FAILED, SUCCEEDED, KILLED, TIME-OUT(?). (In the case of input data is not available) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1195) State Machine for Jobs and Job instances
[ https://issues.apache.org/jira/browse/LENS-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1195: -- Description: Job's state -> NEW, SCHEDULED, EXPIRED, PAUSED. Job instance's state -> WAITING, LAUNCHED, FAILED, SUCCEEDED, KILLED, TIME-OUT(?). (In the case of input data is not available) was: Job's state -> NEW, SCHEDULED, EXPIRED, PAUSED. Job's instance -> WAITING, LAUNCHED, FAILED, SUCCEEDED, KILLED, TIME-OUT(?). (In the case of input data is not available) > State Machine for Jobs and Job instances > > > Key: LENS-1195 > URL: https://issues.apache.org/jira/browse/LENS-1195 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Ajay Yadava > > Job's state -> NEW, SCHEDULED, EXPIRED, PAUSED. > Job instance's state -> WAITING, LAUNCHED, FAILED, SUCCEEDED, KILLED, > TIME-OUT(?). (In the case of input data is not available) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-988) [Server] StateStore for LensScheduler
[ https://issues.apache.org/jira/browse/LENS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-988: - Attachment: scheduler-store.patch > [Server] StateStore for LensScheduler > - > > Key: LENS-988 > URL: https://issues.apache.org/jira/browse/LENS-988 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Ajay Yadava >Assignee: Lavkesh Lahngir > Attachments: scheduler-store.patch > > > Dividing server side component into smaller tasks. This task is for creating > a persistent store for lens scheduler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-988) [Server] StateStore for LensScheduler
[ https://issues.apache.org/jira/browse/LENS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-988: - Status: Patch Available (was: Open) > [Server] StateStore for LensScheduler > - > > Key: LENS-988 > URL: https://issues.apache.org/jira/browse/LENS-988 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Ajay Yadava >Assignee: Lavkesh Lahngir > Attachments: scheduler-store.patch > > > Dividing server side component into smaller tasks. This task is for creating > a persistent store for lens scheduler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1205) Fix ToXMLString class to serialise and deserialise Xjob
Lavkesh Lahngir created LENS-1205: - Summary: Fix ToXMLString class to serialise and deserialise Xjob Key: LENS-1205 URL: https://issues.apache.org/jira/browse/LENS-1205 Project: Apache Lens Issue Type: Bug Reporter: Lavkesh Lahngir Assignee: Lavkesh Lahngir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1205) Fix ToXMLString class to serialise and deserialise Xjob
[ https://issues.apache.org/jira/browse/LENS-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1205: -- Attachment: fix-ToXMLString.patch > Fix ToXMLString class to serialise and deserialise Xjob > --- > > Key: LENS-1205 > URL: https://issues.apache.org/jira/browse/LENS-1205 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: fix-ToXMLString.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1205) Fix ToXMLString class to serialise and deserialise Xjob
[ https://issues.apache.org/jira/browse/LENS-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1205: -- Description: Classes generated from xsd do not contain the @XMLRootElement. We need to Pass a JAXBElement object while calling marshal() method. Also at the time unmarshal(), it returns the JAXBElement. > Fix ToXMLString class to serialise and deserialise Xjob > --- > > Key: LENS-1205 > URL: https://issues.apache.org/jira/browse/LENS-1205 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: fix-ToXMLString.patch > > > Classes generated from xsd do not contain the @XMLRootElement. We need to > Pass a JAXBElement object while calling marshal() method. Also at the time > unmarshal(), it returns the JAXBElement. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1206) Test Cases for SchedulerDAO
[ https://issues.apache.org/jira/browse/LENS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1206: -- Status: Patch Available (was: Open) > Test Cases for SchedulerDAO > --- > > Key: LENS-1206 > URL: https://issues.apache.org/jira/browse/LENS-1206 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: scheduler-store-test.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1206) Test Cases for SchedulerDAO
[ https://issues.apache.org/jira/browse/LENS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1206: -- Attachment: scheduler-store-test.patch > Test Cases for SchedulerDAO > --- > > Key: LENS-1206 > URL: https://issues.apache.org/jira/browse/LENS-1206 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: scheduler-store-test.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1206) Test Cases for SchedulerDAO
[ https://issues.apache.org/jira/browse/LENS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1206: -- Attachment: (was: scheduler-store-test.patch) > Test Cases for SchedulerDAO > --- > > Key: LENS-1206 > URL: https://issues.apache.org/jira/browse/LENS-1206 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: scheduler-store-test.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1206) Test Cases for SchedulerDAO
[ https://issues.apache.org/jira/browse/LENS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1206: -- Attachment: scheduler-store-test.patch > Test Cases for SchedulerDAO > --- > > Key: LENS-1206 > URL: https://issues.apache.org/jira/browse/LENS-1206 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: scheduler-store-test.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (LENS-1019) Return same handle for repeated query from same user
[ https://issues.apache.org/jira/browse/LENS-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir reassigned LENS-1019: - Assignee: Lavkesh Lahngir > Return same handle for repeated query from same user > > > Key: LENS-1019 > URL: https://issues.apache.org/jira/browse/LENS-1019 > Project: Apache Lens > Issue Type: Improvement >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > > If query is repeated from user - with same query, same name, same conf on the > same session > and earlier is still queued or running, then return the same handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1019) Return same handle for repeated query from same user
Lavkesh Lahngir created LENS-1019: - Summary: Return same handle for repeated query from same user Key: LENS-1019 URL: https://issues.apache.org/jira/browse/LENS-1019 Project: Apache Lens Issue Type: Improvement Reporter: Lavkesh Lahngir If query is repeated from user - with same query, same name, same conf on the same session and earlier is still queued or running, then return the same handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir reopened LENS-1143: --- This patch is incomplete. > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Fix For: 2.6 > > Attachments: 0001-Fixing-Text-case-for-duplicate-queries.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
Lavkesh Lahngir created LENS-1143: - Summary: Fix test cases to incorporate LENS-1019 changes Key: LENS-1143 URL: https://issues.apache.org/jira/browse/LENS-1143 Project: Apache Lens Issue Type: Bug Reporter: Lavkesh Lahngir Assignee: Lavkesh Lahngir Priority: Blocker Test cases should keep lens.server.duplicate.query.allowed true by default. Because some of the test cases might be submitting the same query and expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1143: -- Attachment: 0001-Fixing-Text-case-for-duplicate-queries.patch > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Attachments: 0001-Fixing-Text-case-for-duplicate-queries.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1143) Fix test cases to incorporate LENS-1019 changes
[ https://issues.apache.org/jira/browse/LENS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1143: -- Status: Patch Available (was: Open) > Fix test cases to incorporate LENS-1019 changes > --- > > Key: LENS-1143 > URL: https://issues.apache.org/jira/browse/LENS-1143 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > Attachments: 0001-Fixing-Text-case-for-duplicate-queries.patch > > > Test cases should keep lens.server.duplicate.query.allowed true by default. > Because some of the test cases might be submitting the same query and > expecting the queue length to increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1019) Return same handle for repeated query from same user
[ https://issues.apache.org/jira/browse/LENS-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1019: -- Attachment: (was: LENS-1019.diff) > Return same handle for repeated query from same user > > > Key: LENS-1019 > URL: https://issues.apache.org/jira/browse/LENS-1019 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.6 > > Attachments: LENS-1019.patch > > > If query is repeated from user - with same query, same name, same conf on the > same session > and earlier is still queued or running, then return the same handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1019) Return same handle for repeated query from same user
[ https://issues.apache.org/jira/browse/LENS-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1019: -- Attachment: LENS-1019.patch > Return same handle for repeated query from same user > > > Key: LENS-1019 > URL: https://issues.apache.org/jira/browse/LENS-1019 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.6 > > Attachments: LENS-1019.patch > > > If query is repeated from user - with same query, same name, same conf on the > same session > and earlier is still queued or running, then return the same handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1019) Return same handle for repeated query from same user
[ https://issues.apache.org/jira/browse/LENS-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1019: -- Component/s: server > Return same handle for repeated query from same user > > > Key: LENS-1019 > URL: https://issues.apache.org/jira/browse/LENS-1019 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.6 > > Attachments: LENS-1019.diff > > > If query is repeated from user - with same query, same name, same conf on the > same session > and earlier is still queued or running, then return the same handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1019) Return same handle for repeated query from same user
[ https://issues.apache.org/jira/browse/LENS-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1019: -- Fix Version/s: 2.6 Status: Patch Available (was: Open) > Return same handle for repeated query from same user > > > Key: LENS-1019 > URL: https://issues.apache.org/jira/browse/LENS-1019 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.6 > > Attachments: LENS-1019.diff > > > If query is repeated from user - with same query, same name, same conf on the > same session > and earlier is still queued or running, then return the same handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1019) Return same handle for repeated query from same user
[ https://issues.apache.org/jira/browse/LENS-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281399#comment-15281399 ] Lavkesh Lahngir commented on LENS-1019: --- Review request: https://reviews.apache.org/r/47007/ > Return same handle for repeated query from same user > > > Key: LENS-1019 > URL: https://issues.apache.org/jira/browse/LENS-1019 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.6 > > Attachments: LENS-1019.diff > > > If query is repeated from user - with same query, same name, same conf on the > same session > and earlier is still queued or running, then return the same handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1019) Return same handle for repeated query from same user
[ https://issues.apache.org/jira/browse/LENS-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272272#comment-15272272 ] Lavkesh Lahngir commented on LENS-1019: --- 1. There is no need to check for sync queries, because they are very short lived. Or there will be a timeout of a fixe duration which will cancel the query which are not completed. 2. We have to check if the user provided conf is the same for the previous query. QueryContext class has a lensconf which is updated with all the configurations. So the user-conf is merged in the lensConf. There is no separate way to get the user-conf. We can store the user-conf in QueryContext or if we want to optimise, we could just store a md5-hash of the conf. > Return same handle for repeated query from same user > > > Key: LENS-1019 > URL: https://issues.apache.org/jira/browse/LENS-1019 > Project: Apache Lens > Issue Type: Improvement >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > > If query is repeated from user - with same query, same name, same conf on the > same session > and earlier is still queued or running, then return the same handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (LENS-127) Create scheduler client side apis.
[ https://issues.apache.org/jira/browse/LENS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir reassigned LENS-127: Assignee: Lavkesh Lahngir > Create scheduler client side apis. > -- > > Key: LENS-127 > URL: https://issues.apache.org/jira/browse/LENS-127 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > > This task is to put client side api for specifying schedule and trigger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-128: - Attachment: (was: core-scheduler.patch) > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > Fix For: 2.6 > > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-128: - Status: Patch Available (was: Open) > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > Fix For: 2.6 > > Attachments: core-scheduler.patch > > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-128: - Attachment: core-scheduler.patch > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > Fix For: 2.6 > > Attachments: core-scheduler.patch, core-scheduler.patch, > core-scheduler.patch > > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-128: - Status: Patch Available (was: Open) > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > Fix For: 2.6 > > Attachments: core-scheduler.patch, core-scheduler.patch, > core-scheduler.patch > > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1258) len-ui changes for session list page.
Lavkesh Lahngir created LENS-1258: - Summary: len-ui changes for session list page. Key: LENS-1258 URL: https://issues.apache.org/jira/browse/LENS-1258 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] [Resolved] (LENS-1226) Add ability to analyze sessions
[ https://issues.apache.org/jira/browse/LENS-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir resolved LENS-1226. --- Resolution: Fixed > Add ability to analyze sessions > --- > > Key: LENS-1226 > URL: https://issues.apache.org/jira/browse/LENS-1226 > Project: Apache Lens > Issue Type: Improvement > Components: server >Reporter: Amareshwari Sriramadasu >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > > We should be able to analyse all active sessions. > We should have ability to look at the following information : > - Who are the users holding active sessions > - When was the last time the session is accessed > - How many pending queries are there in session and etc. > and more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (LENS-1255) Instance run result path is set NULL in job_instance_run_table
[ https://issues.apache.org/jira/browse/LENS-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir resolved LENS-1255. --- Resolution: Fixed Fix Version/s: 2.7 > Instance run result path is set NULL in job_instance_run_table > --- > > Key: LENS-1255 > URL: https://issues.apache.org/jira/browse/LENS-1255 > Project: Apache Lens > Issue Type: Bug >Reporter: Archana H >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > > mysql> select * from job_instance_run_table ; > | id | runid | sessionhandle > > > | starttime | endtime | resultpath > | > queryhandle | status| > | 515858df-a486-44a2-bb62-de659996842c | 1 | encoding="UTF-8" > standalone="yes"?>ea298134-24d1-4b93-b834-10ba971625fb1ff8129f-8d6e-45e5-b473-d77b841f1e3c > | 1470224250044 | 1470224250765 | NULL > | > 16cd5612-52c8-494f-8e1b-06431fc6cbef | SUCCEEDED | -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (LENS-1247) Scheduler's submit job is not setting db and session config passed
[
https://issues.apache.org/jira/browse/LENS-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir resolved LENS-1247.
---
Resolution: Fixed
Fix Version/s: 2.7
> Scheduler's submit job is not setting db and session config passed
> --
>
> Key: LENS-1247
> URL: https://issues.apache.org/jira/browse/LENS-1247
> Project: Apache Lens
> Issue Type: Bug
> Components: server
>Reporter: Archana H
>Assignee: Lavkesh Lahngir
> Fix For: 2.7
>
>
> Job details:
> | 59ede960-05b7-40ba-a19f-bd4ec59713d4 | standalone="yes"?> xmlns="uri:lens:job:0.1">job1exp_yodacube
> select id,name from sample_dim where name !=
> 'first'DAILY2016-08-02T00:00:00.000+05:302016-08-07T00:00:00.000+05:30
> | archana.h | SCHEDULED | 1470055222974 | 1470055223094 | job1|
> Error:
> {CODE}
> 01 Aug 2016 12:38:34 [d93a86f6-b748-4b7d-bdd0-d6aa40de8620]
> [SchedulerEventListener_AsyncThread-5] ERROR
> org.apache.lens.server.scheduler.SchedulerEventListener - Exception occurred
> while launching the job instance for ae6523b3-f979-4dac-8274-15fc35e886fb for
> nominal time 146765700
> org.apache.lens.server.api.error.LensMultiCauseException:
> SEMANTIC_ERROR[Error while compiling statement: FAILED: SemanticException
> [Error 10001]: Line 1:37 Table not found 'sample_dim']
> at
> org.apache.lens.server.query.QueryExecutionServiceImpl.rewriteAndSelect(QueryExecutionServiceImpl.java:1596)
> ~[classes/:na]
> at
> org.apache.lens.server.query.QueryExecutionServiceImpl.executeAsyncInternal(QueryExecutionServiceImpl.java:2047)
> ~[classes/:na]
> at
> org.apache.lens.server.query.QueryExecutionServiceImpl.executeAsync(QueryExecutionServiceImpl.java:1970)
> ~[classes/:na]
> at
> org.apache.lens.server.scheduler.SchedulerEventListener.process(SchedulerEventListener.java:149)
> [classes/:na]
> at
> org.apache.lens.server.scheduler.SchedulerEventListener.process(SchedulerEventListener.java:48)
> [classes/:na]
> at
> org.apache.lens.server.api.events.AsyncEventListener$1.run(AsyncEventListener.java:110)
> [lens-server-api-2.6.8-inm-SNAPSHOT.jar:2.6.8-inm-SNAPSHOT]
> 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]
> Caused by: org.apache.hive.service.cli.HiveSQLException: Error while
> compiling statement: FAILED: SemanticException [Error 10001]: Line 1:37 Table
> not found 'sample_dim'
> at
> org.apache.hive.service.cli.thrift.ThriftCLIServiceClient.checkStatus(ThriftCLIServiceClient.java:99)
> ~[hive-service-2.1.3-inm-SNAPSHOT.jar:2.1.3-inm-SNAPSHOT]
> at
> org.apache.hive.service.cli.thrift.ThriftCLIServiceClient.executeStatementInternal(ThriftCLIServiceClient.java:202)
> ~[hive-service-2.1.3-inm-SNAPSHOT.jar:2.1.3-inm-SNAPSHOT]
> at
> org.apache.hive.service.cli.thrift.ThriftCLIServiceClient.executeStatement(ThriftCLIServiceClient.java:172)
> ~[hive-service-2.1.3-inm-SNAPSHOT.jar:2.1.3-inm-SNAPSHOT]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_40]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0_40]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_40]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_40]
> at
> org.apache.hive.service.cli.thrift.RetryingThriftCLIServiceClient.invokeInternal(RetryingThriftCLIServiceClient.java:322)
> ~[hive-service-2.1.3-inm-SNAPSHOT.jar:2.1.3-inm-SNAPSHOT]
> at
> org.apache.hive.service.cli.thrift.RetryingThriftCLIServiceClient.invoke(RetryingThriftCLIServiceClient.java:350)
> ~[hive-service-2.1.3-inm-SNAPSHOT.jar:2.1.3-inm-SNAPSHOT]
> at com.sun.proxy.$Proxy89.executeStatement(Unknown Source) ~[na:na]
> at
> org.apache.hive.service.cli.thrift.RetryingThriftCLIServiceClient$CLIServiceClientWrapper.executeStatement(RetryingThriftCLIServiceClient.java:131)
> ~[hive-service-2.1.3-inm-SNAPSHOT.jar:2.1.3-inm-SNAPSHOT]
> at
> org.apache.lens.driver.hive.HiveDriver.execute(HiveDriver.java:521)
> ~[lens-driver-hive-2.6.8-inm-SNAPSHOT.jar:2.6.8-inm-SNAPSHOT]
> at
> org.apache.lens.driver.hive.HiveDriver.explain(HiveDriver.java:451)
> ~[lens-driver-hive-2.6.8-inm-SNAPSHOT.jar:2.6.8-inm-SNAPSHOT]
> at
> org.apache.lens.driver.hive.HiveDriver.estimate(HiveDriver.java:422)
> ~[lens-driver-hive-2.6.8-inm-SNAPSHOT.jar:2.6.8-inm-SNAPSHOT]
> at
>
[jira] [Resolved] (LENS-1252) Scheduler's getJobDefinition api is giving response status 500, if accept media type is "application/xml"
[
https://issues.apache.org/jira/browse/LENS-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir resolved LENS-1252.
---
Resolution: Fixed
Fix Version/s: 2.7
> Scheduler's getJobDefinition api is giving response status 500, if accept
> media type is "application/xml"
> -
>
> Key: LENS-1252
> URL: https://issues.apache.org/jira/browse/LENS-1252
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Archana H
>Assignee: Lavkesh Lahngir
> Fix For: 2.7
>
>
> xml:
> {CODE}
> 16 > GET
> http://192.168.138.252:/lensapi/scheduler/jobs/3a77f190-7656-499f-9a39-62e6ffce9044?sessionid=%3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22+standalone%3D%22yes%22%3F%3E%3ClensSessionHandle%3E%3CpublicId%3E1d79103e-b9d0-4f88-9de3-03f865c0d04f%3C%2FpublicId%3E%3CsecretId%3E3c0ca72c-6e63-47b9-96b8-9e5f571be700%3C%2FsecretId%3E%3C%2FlensSessionHandle%3E
> 16 > accept: application/xml
> 16 > connection: keep-alive
> 16 > host: 192.168.138.252:
> 16 > user-agent: Jersey/2.22.1 (HttpUrlConnection 1.8.0_91)
> 02 Aug 2016 10:40:20 [] [grizzly-http-server-7] INFO
> org.apache.lens.server.LensServer.request - 16 * Server responded with a
> response on thread grizzly-http-server-7
> 16 < 500
> 16 < Content-Type: application/xml
> HTTP 500 Internal Server Error
> {CODE}
> json:
> {CODE}
> 19 > GET
> http://192.168.138.252:/lensapi/scheduler/jobs/3a77f190-7656-499f-9a39-62e6ffce9044?sessionid=%3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22+standalone%3D%22yes%22%3F%3E%3ClensSessionHandle%3E%3CpublicId%3E148b2164-69af-40a5-a5e3-55caa8f1c5f8%3C%2FpublicId%3E%3CsecretId%3E3659ed3d-776c-4301-a0d1-b988cf91962d%3C%2FsecretId%3E%3C%2FlensSessionHandle%3E
> 19 > accept: application/json
> 19 > connection: keep-alive
> 19 > host: 192.168.138.252:
> 19 > user-agent: Jersey/2.22.1 (HttpUrlConnection 1.8.0_91)
> 02 Aug 2016 10:45:07 [] [grizzly-http-server-2] INFO
> org.apache.lens.server.LensServer.request - 19 * Server responded with a
> response on thread grizzly-http-server-2
> 19 < 200
> 19 < Content-Type: application/json
> {
>"name" : "job1",
>"execution" : {
> "session" : {
> "db" : "exp"
> },
> "query" : {
> "query" : "cube select id,name from sample_dim where name != 'first'"
> }
>},
>"trigger" : {
> "frequency" : {
> "enum" : "DAILY"
> }
>},
>"start_time" : "2016-07-01T00:00:00.000+05:30",
>"end_time" : "2016-07-02T00:00:00.000+05:30"
> }
> {CODE}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1272) Checkstyle is failing after LENS-1265
[
https://issues.apache.org/jira/browse/LENS-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1272:
--
Status: Patch Available (was: Open)
> Checkstyle is failing after LENS-1265
> -
>
> Key: LENS-1272
> URL: https://issues.apache.org/jira/browse/LENS-1272
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Lavkesh Lahngir
>Assignee: Lavkesh Lahngir
>Priority: Blocker
> Attachments: checkstyle-fix.patch
>
>
> {code}
> [INFO] --- maven-checkstyle-plugin:2.9.1:check (checkstyle-check) @
> lens-server ---
> [INFO] Starting audit...
> /home/jenkins/jenkins-slave/workspace/Lens-Commit-Java8/lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerServiceImpl.java:100:
> 'if' construct must use '{}'s.
> /home/jenkins/jenkins-slave/workspace/Lens-Commit-Java8/lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerDAO.java:668:
> Line is longer than 120 characters.
> Audit done.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1272) Checkstyle is failing after LENS-1265
[ https://issues.apache.org/jira/browse/LENS-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1272: -- Summary: Checkstyle is failing after LENS-1265 (was: Checkstyle is failing) > Checkstyle is failing after LENS-1265 > - > > Key: LENS-1272 > URL: https://issues.apache.org/jira/browse/LENS-1272 > Project: Apache Lens > Issue Type: Bug >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir >Priority: Blocker > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LENS-1272) Checkstyle is failing
Lavkesh Lahngir created LENS-1272: - Summary: Checkstyle is failing Key: LENS-1272 URL: https://issues.apache.org/jira/browse/LENS-1272 Project: Apache Lens Issue Type: Bug Reporter: Lavkesh Lahngir Assignee: Lavkesh Lahngir Priority: Blocker -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1272) Checkstyle is failing after LENS-1265
[
https://issues.apache.org/jira/browse/LENS-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1272:
--
Attachment: checkstyle-fix.patch
> Checkstyle is failing after LENS-1265
> -
>
> Key: LENS-1272
> URL: https://issues.apache.org/jira/browse/LENS-1272
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Lavkesh Lahngir
>Assignee: Lavkesh Lahngir
>Priority: Blocker
> Attachments: checkstyle-fix.patch
>
>
> {code}
> [INFO] --- maven-checkstyle-plugin:2.9.1:check (checkstyle-check) @
> lens-server ---
> [INFO] Starting audit...
> /home/jenkins/jenkins-slave/workspace/Lens-Commit-Java8/lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerServiceImpl.java:100:
> 'if' construct must use '{}'s.
> /home/jenkins/jenkins-slave/workspace/Lens-Commit-Java8/lens-server/src/main/java/org/apache/lens/server/scheduler/SchedulerDAO.java:668:
> Line is longer than 120 characters.
> Audit done.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1206) Test Cases for SchedulerDAO
[ https://issues.apache.org/jira/browse/LENS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1206: -- Attachment: scheduler-store-test.patch > Test Cases for SchedulerDAO > --- > > Key: LENS-1206 > URL: https://issues.apache.org/jira/browse/LENS-1206 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: scheduler-store-test.patch, scheduler-store-test.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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 updated LENS-1267: -- Description: The Scheduler can not recover from restarting when it was in the middle of launching a query. (was: Scheduler can not recover from restarting when it was in the middle of launching a query. ) > 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-1263) Delete on scheduler job is failing with NPE
[
https://issues.apache.org/jira/browse/LENS-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1263:
--
Issue Type: Bug (was: Sub-task)
Parent: (was: LENS-1265)
> Delete on scheduler job is failing with NPE
> ---
>
> Key: LENS-1263
> URL: https://issues.apache.org/jira/browse/LENS-1263
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Archana H
>Assignee: Lavkesh Lahngir
>
> DELETE
> http://192.168.138.252:/lensapi/scheduler/jobs/74528d83-2ce4-4981-9ce0-53112a78f9cc?sessionid=%3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22+standalone%3D%22yes%22%3F%3E%3ClensSessionHandle%3E%3CpublicId%3E906d3244-1462-477e-bcb0-27814c7644e9%3C%2FpublicId%3E%3CsecretId%3Ef2e74b9a-d0f1-40e7-ae4c-9c6ed3e15e25%3C%2FsecretId%3E%3C%2FlensSessionHandle%3E
> 13 > accept: application/json
> 13 > connection: keep-alive
> 13 > host: 192.168.138.252:
> 13 > user-agent: Jersey/2.22.1 (HttpUrlConnection 1.8.0_91)
> 04 Aug 2016 15:31:30 [] [grizzly-http-server-5] INFO
> org.apache.lens.server.LensServer.request - 13 * Server responded with a
> response on thread grizzly-http-server-5
> 13 < 500
> 13 < Content-Type: application/json
> {
>"apiResult" : {
> "status" : "FAILED",
> "message" : "null"
>}
> }
> Error:
> {CODE}
> org.glassfish.jersey.server.internal.process.MappableException:
> java.lang.NullPointerException
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.mapTargetToRuntimeEx(AbstractJavaResourceMethodDispatcher.java:179)
> ~[jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.access$200(AbstractJavaResourceMethodDispatcher.java:72)
> ~[jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:149)
> ~[jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
> ~[jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)
> ~[jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
> ~[jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
> ~[jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
> ~[jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
> ~[jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
> ~[jersey-server-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> [jersey-common-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> [jersey-common-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> [jersey-common-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> [jersey-common-2.22.1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> [jersey-common-2.22.1.jar:na]
> at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
> [jersey-common-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
> [jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
> [jersey-server-2.22.1.jar:na]
> at
> org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service(GrizzlyHttpContainer.java:384)
> [jersey-container-grizzly2-http-2.22.1.jar:na]
> at
> org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:224)
> [grizzly-http-server-2.3.23.jar:2.3.23]
> at
> org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:591)
> [grizzly-framework-2.3.23.jar:2.3.23]
> at
> org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:571)
> [grizzly-framework-2.3.23.jar:2.3.23]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_40]
> Caused by: java.lang.NullPointerException: null
> at
> org.apache.lens.server.scheduler.AlarmService.checkExists(AlarmService.java:201)
> ~[classes/:na]
> at
>
[jira] [Updated] (LENS-1252) Scheduler's getJobDefinition api is giving response status 500, if accept media type is "application/xml"
[
https://issues.apache.org/jira/browse/LENS-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1252:
--
Issue Type: Bug (was: Sub-task)
Parent: (was: LENS-1265)
> Scheduler's getJobDefinition api is giving response status 500, if accept
> media type is "application/xml"
> -
>
> Key: LENS-1252
> URL: https://issues.apache.org/jira/browse/LENS-1252
> Project: Apache Lens
> Issue Type: Bug
>Reporter: Archana H
>Assignee: Lavkesh Lahngir
>
> xml:
> {CODE}
> 16 > GET
> http://192.168.138.252:/lensapi/scheduler/jobs/3a77f190-7656-499f-9a39-62e6ffce9044?sessionid=%3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22+standalone%3D%22yes%22%3F%3E%3ClensSessionHandle%3E%3CpublicId%3E1d79103e-b9d0-4f88-9de3-03f865c0d04f%3C%2FpublicId%3E%3CsecretId%3E3c0ca72c-6e63-47b9-96b8-9e5f571be700%3C%2FsecretId%3E%3C%2FlensSessionHandle%3E
> 16 > accept: application/xml
> 16 > connection: keep-alive
> 16 > host: 192.168.138.252:
> 16 > user-agent: Jersey/2.22.1 (HttpUrlConnection 1.8.0_91)
> 02 Aug 2016 10:40:20 [] [grizzly-http-server-7] INFO
> org.apache.lens.server.LensServer.request - 16 * Server responded with a
> response on thread grizzly-http-server-7
> 16 < 500
> 16 < Content-Type: application/xml
> HTTP 500 Internal Server Error
> {CODE}
> json:
> {CODE}
> 19 > GET
> http://192.168.138.252:/lensapi/scheduler/jobs/3a77f190-7656-499f-9a39-62e6ffce9044?sessionid=%3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22+standalone%3D%22yes%22%3F%3E%3ClensSessionHandle%3E%3CpublicId%3E148b2164-69af-40a5-a5e3-55caa8f1c5f8%3C%2FpublicId%3E%3CsecretId%3E3659ed3d-776c-4301-a0d1-b988cf91962d%3C%2FsecretId%3E%3C%2FlensSessionHandle%3E
> 19 > accept: application/json
> 19 > connection: keep-alive
> 19 > host: 192.168.138.252:
> 19 > user-agent: Jersey/2.22.1 (HttpUrlConnection 1.8.0_91)
> 02 Aug 2016 10:45:07 [] [grizzly-http-server-2] INFO
> org.apache.lens.server.LensServer.request - 19 * Server responded with a
> response on thread grizzly-http-server-2
> 19 < 200
> 19 < Content-Type: application/json
> {
>"name" : "job1",
>"execution" : {
> "session" : {
> "db" : "exp"
> },
> "query" : {
> "query" : "cube select id,name from sample_dim where name != 'first'"
> }
>},
>"trigger" : {
> "frequency" : {
> "enum" : "DAILY"
> }
>},
>"start_time" : "2016-07-01T00:00:00.000+05:30",
>"end_time" : "2016-07-02T00:00:00.000+05:30"
> }
> {CODE}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1255) Instance run result path is set NULL in job_instance_run_table
[ https://issues.apache.org/jira/browse/LENS-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1255: -- Issue Type: Sub-task (was: Bug) Parent: LENS-1265 > Instance run result path is set NULL in job_instance_run_table > --- > > Key: LENS-1255 > URL: https://issues.apache.org/jira/browse/LENS-1255 > Project: Apache Lens > Issue Type: Sub-task >Reporter: Archana H >Assignee: Lavkesh Lahngir > > mysql> select * from job_instance_run_table ; > | id | runid | sessionhandle > > > | starttime | endtime | resultpath > | > queryhandle | status| > | 515858df-a486-44a2-bb62-de659996842c | 1 | encoding="UTF-8" > standalone="yes"?>ea298134-24d1-4b93-b834-10ba971625fb1ff8129f-8d6e-45e5-b473-d77b841f1e3c > | 1470224250044 | 1470224250765 | NULL > | > 16cd5612-52c8-494f-8e1b-06431fc6cbef | SUCCEEDED | -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1252) Scheduler's getJobDefinition api is giving response status 500, if accept media type is "application/xml"
[
https://issues.apache.org/jira/browse/LENS-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavkesh Lahngir updated LENS-1252:
--
Issue Type: Sub-task (was: Bug)
Parent: LENS-1265
> Scheduler's getJobDefinition api is giving response status 500, if accept
> media type is "application/xml"
> -
>
> Key: LENS-1252
> URL: https://issues.apache.org/jira/browse/LENS-1252
> Project: Apache Lens
> Issue Type: Sub-task
>Reporter: Archana H
>Assignee: Lavkesh Lahngir
>
> xml:
> {CODE}
> 16 > GET
> http://192.168.138.252:/lensapi/scheduler/jobs/3a77f190-7656-499f-9a39-62e6ffce9044?sessionid=%3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22+standalone%3D%22yes%22%3F%3E%3ClensSessionHandle%3E%3CpublicId%3E1d79103e-b9d0-4f88-9de3-03f865c0d04f%3C%2FpublicId%3E%3CsecretId%3E3c0ca72c-6e63-47b9-96b8-9e5f571be700%3C%2FsecretId%3E%3C%2FlensSessionHandle%3E
> 16 > accept: application/xml
> 16 > connection: keep-alive
> 16 > host: 192.168.138.252:
> 16 > user-agent: Jersey/2.22.1 (HttpUrlConnection 1.8.0_91)
> 02 Aug 2016 10:40:20 [] [grizzly-http-server-7] INFO
> org.apache.lens.server.LensServer.request - 16 * Server responded with a
> response on thread grizzly-http-server-7
> 16 < 500
> 16 < Content-Type: application/xml
> HTTP 500 Internal Server Error
> {CODE}
> json:
> {CODE}
> 19 > GET
> http://192.168.138.252:/lensapi/scheduler/jobs/3a77f190-7656-499f-9a39-62e6ffce9044?sessionid=%3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22+standalone%3D%22yes%22%3F%3E%3ClensSessionHandle%3E%3CpublicId%3E148b2164-69af-40a5-a5e3-55caa8f1c5f8%3C%2FpublicId%3E%3CsecretId%3E3659ed3d-776c-4301-a0d1-b988cf91962d%3C%2FsecretId%3E%3C%2FlensSessionHandle%3E
> 19 > accept: application/json
> 19 > connection: keep-alive
> 19 > host: 192.168.138.252:
> 19 > user-agent: Jersey/2.22.1 (HttpUrlConnection 1.8.0_91)
> 02 Aug 2016 10:45:07 [] [grizzly-http-server-2] INFO
> org.apache.lens.server.LensServer.request - 19 * Server responded with a
> response on thread grizzly-http-server-2
> 19 < 200
> 19 < Content-Type: application/json
> {
>"name" : "job1",
>"execution" : {
> "session" : {
> "db" : "exp"
> },
> "query" : {
> "query" : "cube select id,name from sample_dim where name != 'first'"
> }
>},
>"trigger" : {
> "frequency" : {
> "enum" : "DAILY"
> }
>},
>"start_time" : "2016-07-01T00:00:00.000+05:30",
>"end_time" : "2016-07-02T00:00:00.000+05:30"
> }
> {CODE}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (LENS-1257) Serverside changes for getting session list
[ https://issues.apache.org/jira/browse/LENS-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1257: -- Attachment: Session-info-api.patch > Serverside changes for getting session list > --- > > Key: LENS-1257 > URL: https://issues.apache.org/jira/browse/LENS-1257 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > Attachments: 0001-Session-info-api.patch, Session-info-api.patch, > Session-info-api.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1258) len-ui changes for session list page.
[ https://issues.apache.org/jira/browse/LENS-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1258: -- Status: Patch Available (was: Open) > len-ui changes for session list page. > - > > Key: LENS-1258 > URL: https://issues.apache.org/jira/browse/LENS-1258 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > Attachments: Session-UI.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1258) len-ui changes for session list page.
[ https://issues.apache.org/jira/browse/LENS-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1258: -- Attachment: Session-UI.patch > len-ui changes for session list page. > - > > Key: LENS-1258 > URL: https://issues.apache.org/jira/browse/LENS-1258 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > Attachments: Session-UI.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1257) Serverside changes for getting session list
[ https://issues.apache.org/jira/browse/LENS-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1257: -- Attachment: Session-info-api.patch > Serverside changes for getting session list > --- > > Key: LENS-1257 > URL: https://issues.apache.org/jira/browse/LENS-1257 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Fix For: 2.7 > > Attachments: 0001-Session-info-api.patch, Session-info-api.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1265) Scheduler Bug fixes
[ https://issues.apache.org/jira/browse/LENS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1265: -- Attachment: Scheduler-bug-fixes.patch > Scheduler Bug fixes > --- > > Key: LENS-1265 > URL: https://issues.apache.org/jira/browse/LENS-1265 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-bug-fixes.patch, Scheduler-bug-fixes.patch, > Scheduler-bug-fixes.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1265) Scheduler Bug fixes
[ https://issues.apache.org/jira/browse/LENS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1265: -- Attachment: Scheduler-bug-fixes.patch > Scheduler Bug fixes > --- > > Key: LENS-1265 > URL: https://issues.apache.org/jira/browse/LENS-1265 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-bug-fixes.patch, Scheduler-bug-fixes.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1265) Scheduler Bug fixes
[ https://issues.apache.org/jira/browse/LENS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1265: -- Attachment: (was: Scheduler-bug-fixes.patch) > Scheduler Bug fixes > --- > > Key: LENS-1265 > URL: https://issues.apache.org/jira/browse/LENS-1265 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-bug-fixes.patch, Scheduler-bug-fixes.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1265) Scheduler Bug fixes
[ https://issues.apache.org/jira/browse/LENS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1265: -- Status: Patch Available (was: Open) > Scheduler Bug fixes > --- > > Key: LENS-1265 > URL: https://issues.apache.org/jira/browse/LENS-1265 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-bug-fixes.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1265) Scheduler Bug fixes
[ https://issues.apache.org/jira/browse/LENS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1265: -- Attachment: Scheduler-bug-fixes.patch > Scheduler Bug fixes > --- > > Key: LENS-1265 > URL: https://issues.apache.org/jira/browse/LENS-1265 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-bug-fixes.patch, Scheduler-bug-fixes.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1265) Scheduler Bug fixes
[ https://issues.apache.org/jira/browse/LENS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1265: -- Attachment: Scheduler-bug-fixes.patch > Scheduler Bug fixes > --- > > Key: LENS-1265 > URL: https://issues.apache.org/jira/browse/LENS-1265 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-bug-fixes.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1265) Scheduler Bug fixes
[ https://issues.apache.org/jira/browse/LENS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1265: -- Status: In Progress (was: Patch Available) > Scheduler Bug fixes > --- > > Key: LENS-1265 > URL: https://issues.apache.org/jira/browse/LENS-1265 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-bug-fixes.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1265) Scheduler Bug fixes
[ https://issues.apache.org/jira/browse/LENS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1265: -- Status: Patch Available (was: In Progress) > Scheduler Bug fixes > --- > > Key: LENS-1265 > URL: https://issues.apache.org/jira/browse/LENS-1265 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-bug-fixes.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-128: - Attachment: core-scheduler.patch > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > Attachments: core-scheduler.patch > > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-128: - Status: Patch Available (was: In Progress) > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > Attachments: core-scheduler.patch > > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-128: - Attachment: core-scheduler.patch > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > Attachments: core-scheduler.patch, core-scheduler.patch > > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-128 started by Lavkesh Lahngir. > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1206) Test Cases for SchedulerDAO
[ https://issues.apache.org/jira/browse/LENS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1206: -- Attachment: scheduler-store-test-1.patch > Test Cases for SchedulerDAO > --- > > Key: LENS-1206 > URL: https://issues.apache.org/jira/browse/LENS-1206 > Project: Apache Lens > Issue Type: Task >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: scheduler-store-test-1.patch, > scheduler-store-test.patch, scheduler-store-test.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-128: - Summary: SchedulerServiceImpl for scheduler. (was: Server side api for scheduler.) > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (LENS-128) SchedulerServiceImpl for scheduler.
[ https://issues.apache.org/jira/browse/LENS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir reassigned LENS-128: Assignee: Lavkesh Lahngir > SchedulerServiceImpl for scheduler. > --- > > Key: LENS-128 > URL: https://issues.apache.org/jira/browse/LENS-128 > Project: Apache Lens > Issue Type: Sub-task > Components: server >Reporter: Prashant Gupta >Assignee: Lavkesh Lahngir > > Server APIs will include the support for operations as specified at LENS-124. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LENS-1184) REST API for the scheduler
[
https://issues.apache.org/jira/browse/LENS-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360879#comment-15360879
]
Lavkesh Lahngir commented on LENS-1184:
---
{code}
SchedulerDAO schedulerDAO = new SchedulerDAO(hiveConf);
{code}
Above code is correct, however it should be called in the init() method, not in
constructor. Lens services has a order in which are thet are intialized.
Something like that.
{code}
public SchedulerServiceImpl(CLIService cliService) throws LensException {
super(NAME, cliService);
}
public synchronized void init(HiveConf hiveConf) {
super.init(hiveConf);
try {
schedulerDAO = new SchedulerDAO(hiveConf);
.
} catch (LensException e) {
log.error("Error Initialising Scheduler-service", e);
}
}
{code}
> REST API for the scheduler
> --
>
> Key: LENS-1184
> URL: https://issues.apache.org/jira/browse/LENS-1184
> Project: Apache Lens
> Issue Type: Sub-task
> Components: server
>Reporter: Ajay Yadava
>Assignee: Ajay Yadava
> Fix For: 2.6
>
> Attachments: LENS-1184.patch
>
>
> For the sake of breaking in smaller commits, will publish the REST API
> signatures with placeholders or dummy values being returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (LENS-1184) REST API for the scheduler
[
https://issues.apache.org/jira/browse/LENS-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360879#comment-15360879
]
Lavkesh Lahngir edited comment on LENS-1184 at 7/4/16 6:12 AM:
---
{code}
SchedulerDAO schedulerDAO = new SchedulerDAO(hiveConf);
{code}
Above code is correct, however it should be called in the init() method, not in
constructor. Lens services has a order in which they are intialized. Something
like that.
{code}
public SchedulerServiceImpl(CLIService cliService) throws LensException {
super(NAME, cliService);
}
public synchronized void init(HiveConf hiveConf) {
super.init(hiveConf);
try {
schedulerDAO = new SchedulerDAO(hiveConf);
.
} catch (LensException e) {
log.error("Error Initialising Scheduler-service", e);
}
}
{code}
was (Author: lavkesh):
{code}
SchedulerDAO schedulerDAO = new SchedulerDAO(hiveConf);
{code}
Above code is correct, however it should be called in the init() method, not in
constructor. Lens services has a order in which are thet are intialized.
Something like that.
{code}
public SchedulerServiceImpl(CLIService cliService) throws LensException {
super(NAME, cliService);
}
public synchronized void init(HiveConf hiveConf) {
super.init(hiveConf);
try {
schedulerDAO = new SchedulerDAO(hiveConf);
.
} catch (LensException e) {
log.error("Error Initialising Scheduler-service", e);
}
}
{code}
> REST API for the scheduler
> --
>
> Key: LENS-1184
> URL: https://issues.apache.org/jira/browse/LENS-1184
> Project: Apache Lens
> Issue Type: Sub-task
> Components: server
>Reporter: Ajay Yadava
>Assignee: Ajay Yadava
> Fix For: 2.6
>
> Attachments: LENS-1184.patch
>
>
> For the sake of breaking in smaller commits, will publish the REST API
> signatures with placeholders or dummy values being returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (LENS-1279) Improve Scheduler API messages
[ https://issues.apache.org/jira/browse/LENS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir reassigned LENS-1279: - Assignee: Lavkesh Lahngir > Improve Scheduler API messages > > > Key: LENS-1279 > URL: https://issues.apache.org/jira/browse/LENS-1279 > 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-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] [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] [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-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] [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-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-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-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) 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] [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-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] [Updated] (LENS-1279) Improve Scheduler API messages
[ https://issues.apache.org/jira/browse/LENS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1279: -- Description: This patch includes more clearer scheduler APIs. (was: This patch includes more clear scheduler APIs.) > Improve Scheduler API messages > > > Key: LENS-1279 > URL: https://issues.apache.org/jira/browse/LENS-1279 > Project: Apache Lens > Issue Type: Improvement >Reporter: Lavkesh Lahngir >Assignee: Lavkesh Lahngir > Attachments: Scheduler-API-fixes.patch > > > This patch includes more clearer scheduler APIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (LENS-1288) example-job.xml in example schema isn't up to date with recent xsd changes
[ https://issues.apache.org/jira/browse/LENS-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated LENS-1288: -- Attachment: example-xml.patch > example-job.xml in example schema isn't up to date with recent xsd changes > -- > > Key: LENS-1288 > URL: https://issues.apache.org/jira/browse/LENS-1288 > Project: Apache Lens > Issue Type: Bug >Reporter: Rajat Khandelwal >Assignee: Lavkesh Lahngir > Attachments: example-xml.patch, example-xml.patch > > -- 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-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] [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-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] [Created] (LENS-1306) Wrong hsql query is created when there are multiple facts and no dimension.
Lavkesh Lahngir created LENS-1306: - Summary: 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 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)
