[jira] [Work logged] (EAGLE-1104) Eagle 1.0 preparation
[ https://issues.apache.org/jira/browse/EAGLE-1104?focusedWorklogId=425137=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425137 ] ASF GitHub Bot logged work on EAGLE-1104: - Author: ASF GitHub Bot Created on: 19/Apr/20 20:35 Start Date: 19/Apr/20 20:35 Worklog Time Spent: 10m Work Description: yonzhang commented on pull request #1011: (DON'T MERGE) EAGLE-1104, Eagle 1.0 preparation URL: https://github.com/apache/eagle/pull/1011 Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 425137) Remaining Estimate: 167h 50m (was: 168h) Time Spent: 10m > Eagle 1.0 preparation > - > > Key: EAGLE-1104 > URL: https://issues.apache.org/jira/browse/EAGLE-1104 > Project: Eagle > Issue Type: New Feature > Components: Core::Eagle Server >Affects Versions: 1.0 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Major > Original Estimate: 168h > Time Spent: 10m > Remaining Estimate: 167h 50m > > Here I want to propose Eagle 1.0, which targets for decoupling eagle > applications from monitoring framework, which we had discussed long time ago. > This story is for preparation of Eagle 1.0 development. > - Create a small runnable application easily to start development from -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1102) Integrate CVE maven plugin
[ https://issues.apache.org/jira/browse/EAGLE-1102?focusedWorklogId=324872=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-324872 ] ASF GitHub Bot logged work on EAGLE-1102: - Author: ASF GitHub Bot Created on: 08/Oct/19 06:06 Start Date: 08/Oct/19 06:06 Worklog Time Spent: 10m Work Description: asfgit commented on pull request #1005: [EAGLE-1102] Integrate CVE maven plugin URL: https://github.com/apache/eagle/pull/1005 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 324872) Time Spent: 50m (was: 40m) > Integrate CVE maven plugin > -- > > Key: EAGLE-1102 > URL: https://issues.apache.org/jira/browse/EAGLE-1102 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Grainier Perera >Assignee: Grainier Perera >Priority: Critical > Labels: security > Time Spent: 50m > Remaining Estimate: 0h > > Integrate the CVE maven plugin [1] for eagle to check security during build > time. This will help to detect publicly disclosed vulnerabilities contained > within eagle's dependencies. > [1] https://github.com/jeremylong/DependencyCheck -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1102) Integrate CVE maven plugin
[ https://issues.apache.org/jira/browse/EAGLE-1102?focusedWorklogId=324871=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-324871 ] ASF GitHub Bot logged work on EAGLE-1102: - Author: ASF GitHub Bot Created on: 08/Oct/19 06:05 Start Date: 08/Oct/19 06:05 Worklog Time Spent: 10m Work Description: haoch commented on issue #1005: [EAGLE-1102] Integrate CVE maven plugin URL: https://github.com/apache/eagle/pull/1005#issuecomment-539350699 LGTM, thanks @grainier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 324871) Time Spent: 40m (was: 0.5h) > Integrate CVE maven plugin > -- > > Key: EAGLE-1102 > URL: https://issues.apache.org/jira/browse/EAGLE-1102 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Grainier Perera >Assignee: Grainier Perera >Priority: Critical > Labels: security > Time Spent: 40m > Remaining Estimate: 0h > > Integrate the CVE maven plugin [1] for eagle to check security during build > time. This will help to detect publicly disclosed vulnerabilities contained > within eagle's dependencies. > [1] https://github.com/jeremylong/DependencyCheck -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1102) Integrate CVE maven plugin
[ https://issues.apache.org/jira/browse/EAGLE-1102?focusedWorklogId=324008=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-324008 ] ASF GitHub Bot logged work on EAGLE-1102: - Author: ASF GitHub Bot Created on: 06/Oct/19 04:44 Start Date: 06/Oct/19 04:44 Worklog Time Spent: 10m Work Description: grainier commented on issue #1005: [EAGLE-1102] Integrate CVE maven plugin URL: https://github.com/apache/eagle/pull/1005#issuecomment-538711494 @haoch It's attached on the parent issue [1]. And the `dependency-check-report.html` can be found on [2]. [1] https://issues.apache.org/jira/browse/EAGLE-1100 [2] https://issues.apache.org/jira/secure/attachment/12982206/dependency-check-report.html This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 324008) Time Spent: 0.5h (was: 20m) > Integrate CVE maven plugin > -- > > Key: EAGLE-1102 > URL: https://issues.apache.org/jira/browse/EAGLE-1102 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Grainier Perera >Assignee: Grainier Perera >Priority: Critical > Labels: security > Time Spent: 0.5h > Remaining Estimate: 0h > > Integrate the CVE maven plugin [1] for eagle to check security during build > time. This will help to detect publicly disclosed vulnerabilities contained > within eagle's dependencies. > [1] https://github.com/jeremylong/DependencyCheck -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1102) Integrate CVE maven plugin
[ https://issues.apache.org/jira/browse/EAGLE-1102?focusedWorklogId=324007=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-324007 ] ASF GitHub Bot logged work on EAGLE-1102: - Author: ASF GitHub Bot Created on: 06/Oct/19 04:19 Start Date: 06/Oct/19 04:19 Worklog Time Spent: 10m Work Description: haoch commented on issue #1005: [EAGLE-1102] Integrate CVE maven plugin URL: https://github.com/apache/eagle/pull/1005#issuecomment-538710474 @grainier Could you please attach the CVE alerts on the jira/PR as well? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 324007) Time Spent: 20m (was: 10m) > Integrate CVE maven plugin > -- > > Key: EAGLE-1102 > URL: https://issues.apache.org/jira/browse/EAGLE-1102 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Grainier Perera >Assignee: Grainier Perera >Priority: Critical > Labels: security > Time Spent: 20m > Remaining Estimate: 0h > > Integrate the CVE maven plugin [1] for eagle to check security during build > time. This will help to detect publicly disclosed vulnerabilities contained > within eagle's dependencies. > [1] https://github.com/jeremylong/DependencyCheck -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1102) Integrate CVE maven plugin
[ https://issues.apache.org/jira/browse/EAGLE-1102?focusedWorklogId=323273=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-323273 ] ASF GitHub Bot logged work on EAGLE-1102: - Author: ASF GitHub Bot Created on: 04/Oct/19 08:28 Start Date: 04/Oct/19 08:28 Worklog Time Spent: 10m Work Description: grainier commented on pull request #1005: [EAGLE-1102] Integrate CVE maven plugin URL: https://github.com/apache/eagle/pull/1005 ## Purpose Purpose of this pull request is to integrate the CVE maven plugin for eagle to check security vulnerabilities in dependencies during build time. This will help to detect publicly disclosed vulnerabilities contained within eagle's dependencies (and the dependencies of all child modules). ## Usage This plugin configuration is attached to the `mvn verify` phase. Therefore, this will run automatically when we perform a `mvn clean verify`. Once the `mvn` process is completed, the plugin will create a `dependency-check-report.html` report in `target/` dir with the detect vulnerabilities. In case if you need to skip this plugin, use `owasp.check.skip=true` property (i.e `mvn clean verify -Dowasp.check.skip=true`). ## Remarks - Fixes https://issues.apache.org/jira/browse/EAGLE-1102 - https://issues.apache.org/jira/browse/EAGLE-1100 - https://github.com/jeremylong/DependencyCheck - https://jeremylong.github.io/DependencyCheck/dependency-check-maven/aggregate-mojo.html - https://jeremylong.github.io/DependencyCheck/general/suppression.html --- Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [x] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [x] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 323273) Remaining Estimate: 0h Time Spent: 10m > Integrate CVE maven plugin > -- > > Key: EAGLE-1102 > URL: https://issues.apache.org/jira/browse/EAGLE-1102 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Grainier Perera >Assignee: Grainier Perera >Priority: Critical > Labels: security > Time Spent: 10m > Remaining Estimate: 0h > > Integrate the CVE maven plugin [1] for eagle to check security during build > time. This will help to detect publicly disclosed vulnerabilities contained > within eagle's dependencies. > [1] https://github.com/jeremylong/DependencyCheck -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1101) Update merge-eagle-pr.py to support python 3.x
[ https://issues.apache.org/jira/browse/EAGLE-1101?focusedWorklogId=322343=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-322343 ] ASF GitHub Bot logged work on EAGLE-1101: - Author: ASF GitHub Bot Created on: 02/Oct/19 22:55 Start Date: 02/Oct/19 22:55 Worklog Time Spent: 10m Work Description: asfgit commented on pull request #1004: [EAGLE-1101] Update merge-eagle-pr.py to support python 3.x URL: https://github.com/apache/eagle/pull/1004 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 322343) Remaining Estimate: 0h Time Spent: 10m > Update merge-eagle-pr.py to support python 3.x > -- > > Key: EAGLE-1101 > URL: https://issues.apache.org/jira/browse/EAGLE-1101 > Project: Eagle > Issue Type: Improvement >Reporter: Hao Chen >Assignee: Hao Chen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > h1. Update merge-eagle-pr.py to support python 3.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1068) Upgrade siddhi dependency to v5.1.4
[ https://issues.apache.org/jira/browse/EAGLE-1068?focusedWorklogId=322339=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-322339 ] ASF GitHub Bot logged work on EAGLE-1068: - Author: ASF GitHub Bot Created on: 02/Oct/19 22:50 Start Date: 02/Oct/19 22:50 Worklog Time Spent: 10m Work Description: asfgit commented on pull request #1003: [EAGLE-1068] Upgrade Siddhi dependency to v5.1.4 URL: https://github.com/apache/eagle/pull/1003 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 322339) Time Spent: 1h 10m (was: 1h) > Upgrade siddhi dependency to v5.1.4 > --- > > Key: EAGLE-1068 > URL: https://issues.apache.org/jira/browse/EAGLE-1068 > Project: Eagle > Issue Type: Improvement > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Grainier Perera >Priority: Blocker > Fix For: v0.5.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1068) Upgrade siddhi dependency to v5.1.4
[ https://issues.apache.org/jira/browse/EAGLE-1068?focusedWorklogId=317242=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-317242 ] ASF GitHub Bot logged work on EAGLE-1068: - Author: ASF GitHub Bot Created on: 24/Sep/19 07:53 Start Date: 24/Sep/19 07:53 Worklog Time Spent: 10m Work Description: grainier commented on pull request #1003: [EAGLE-1068] Upgrade Siddhi dependency to v5.1.4 URL: https://github.com/apache/eagle/pull/1003#discussion_r327474090 ## File path: eagle-core/eagle-common/src/test/java/org/apache/eagle/common/TestDateTimeUtil.java ## @@ -49,7 +49,7 @@ public void testRound2() { cal.set(Calendar.MINUTE, 0); cal.set(Calendar.SECOND, 0); cal.set(Calendar.MILLISECOND, 0); -Assert.assertEquals(tsInHour, cal.getTimeInMillis()); +//Assert.assertEquals(tsInHour, cal.getTimeInMillis()); Review comment: @haoch, sorry, it was a mistake. When I tried to build, this failed intermittently (even with the master), so I commented it out. Reverted with 1240042 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 317242) Time Spent: 50m (was: 40m) > Upgrade siddhi dependency to v5.1.4 > --- > > Key: EAGLE-1068 > URL: https://issues.apache.org/jira/browse/EAGLE-1068 > Project: Eagle > Issue Type: Improvement > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Grainier Perera >Priority: Blocker > Fix For: v0.5.1 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1068) Upgrade siddhi dependency to v5.1.4
[ https://issues.apache.org/jira/browse/EAGLE-1068?focusedWorklogId=316945=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-316945 ] ASF GitHub Bot logged work on EAGLE-1068: - Author: ASF GitHub Bot Created on: 23/Sep/19 19:46 Start Date: 23/Sep/19 19:46 Worklog Time Spent: 10m Work Description: haoch commented on pull request #1003: [EAGLE-1068] Upgrade Siddhi dependency to v5.1.4 URL: https://github.com/apache/eagle/pull/1003#discussion_r327296261 ## File path: eagle-core/eagle-common/src/test/java/org/apache/eagle/common/TestDateTimeUtil.java ## @@ -49,7 +49,7 @@ public void testRound2() { cal.set(Calendar.MINUTE, 0); cal.set(Calendar.SECOND, 0); cal.set(Calendar.MILLISECOND, 0); -Assert.assertEquals(tsInHour, cal.getTimeInMillis()); +//Assert.assertEquals(tsInHour, cal.getTimeInMillis()); Review comment: @grainier Why remove this assertion? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 316945) Time Spent: 40m (was: 0.5h) > Upgrade siddhi dependency to v5.1.4 > --- > > Key: EAGLE-1068 > URL: https://issues.apache.org/jira/browse/EAGLE-1068 > Project: Eagle > Issue Type: Improvement > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Grainier Perera >Priority: Blocker > Fix For: v0.5.1 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1068) Upgrade siddhi dependency to v5.1.4
[ https://issues.apache.org/jira/browse/EAGLE-1068?focusedWorklogId=316944=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-316944 ] ASF GitHub Bot logged work on EAGLE-1068: - Author: ASF GitHub Bot Created on: 23/Sep/19 19:42 Start Date: 23/Sep/19 19:42 Worklog Time Spent: 10m Work Description: haoch commented on issue #1003: [EAGLE-1068] Upgrade Siddhi dependency to v5.1.4 URL: https://github.com/apache/eagle/pull/1003#issuecomment-534253270 LGTM This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 316944) Time Spent: 0.5h (was: 20m) > Upgrade siddhi dependency to v5.1.4 > --- > > Key: EAGLE-1068 > URL: https://issues.apache.org/jira/browse/EAGLE-1068 > Project: Eagle > Issue Type: Improvement > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Grainier Perera >Priority: Blocker > Fix For: v0.5.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (EAGLE-1068) Upgrade siddhi dependency to v5.1.4
[ https://issues.apache.org/jira/browse/EAGLE-1068?focusedWorklogId=312571=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-312571 ] ASF GitHub Bot logged work on EAGLE-1068: - Author: ASF GitHub Bot Created on: 14/Sep/19 17:12 Start Date: 14/Sep/19 17:12 Worklog Time Spent: 10m Work Description: jhsenjaliya commented on issue #1003: [EAGLE-1068] Upgrade Siddhi dependency to v5.1.4 URL: https://github.com/apache/eagle/pull/1003#issuecomment-531496811 looking at this PR, all siddhi extension code upgrade looks right, @haoch can u pls help review this PR as well since you have more insights into siddhi's execution engine. Thanks This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 312571) Time Spent: 20m (was: 10m) > Upgrade siddhi dependency to v5.1.4 > --- > > Key: EAGLE-1068 > URL: https://issues.apache.org/jira/browse/EAGLE-1068 > Project: Eagle > Issue Type: Improvement > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Grainier Perera >Priority: Blocker > Fix For: v0.5.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (EAGLE-1068) Upgrade siddhi dependency to v5.1.4
[ https://issues.apache.org/jira/browse/EAGLE-1068?focusedWorklogId=312082=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-312082 ] ASF GitHub Bot logged work on EAGLE-1068: - Author: ASF GitHub Bot Created on: 13/Sep/19 14:36 Start Date: 13/Sep/19 14:36 Worklog Time Spent: 10m Work Description: grainier commented on pull request #1003: [EAGLE-1068] Upgrade Siddhi dependency to v5.1.4 URL: https://github.com/apache/eagle/pull/1003 ## Purpose Purpose of this pull request is to upgrade the [Siddhi](https://mvnrepository.com/artifact/io.siddhi) dependency version to `v5.1.4`. With this, it'll also; - Fix `alert-core` and tests to support new Siddhi APIs. - Fix existing custom Siddhi extensions to support new Siddhi APIs. - Improve extension loading (use annotation support instead of `siddhiext`). - Add the following dependencies (since they are now separated from Siddhi core); ```xml io.siddhi.extension.execution.regex siddhi-execution-regex 5.0.5 io.siddhi.extension.execution.string siddhi-execution-string 5.0.5 ``` ## Remarks - Fixes https://issues.apache.org/jira/browse/EAGLE-1068 - https://issues.apache.org/jira/browse/EAGLE-1065 --- Contribution Tasks: - [x] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [x] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 312082) Remaining Estimate: 0h Time Spent: 10m > Upgrade siddhi dependency to v5.1.4 > --- > > Key: EAGLE-1068 > URL: https://issues.apache.org/jira/browse/EAGLE-1068 > Project: Eagle > Issue Type: Improvement > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Grainier Perera >Priority: Blocker > Fix For: v0.5.1 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (EAGLE-522) Implement HOURLY_RULE for Absence Alert.
[ https://issues.apache.org/jira/browse/EAGLE-522?focusedWorklogId=280726=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-280726 ] ASF GitHub Bot logged work on EAGLE-522: Author: ASF GitHub Bot Created on: 23/Jul/19 00:57 Start Date: 23/Jul/19 00:57 Worklog Time Spent: 10m Work Description: pkuwm commented on pull request #426: [EAGLE-522] Implement HOURLY_RULE for Absence Alert. URL: https://github.com/apache/eagle/pull/426 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 280726) Time Spent: 10m Remaining Estimate: 0h > Implement HOURLY_RULE for Absence Alert. > > > Key: EAGLE-522 > URL: https://issues.apache.org/jira/browse/EAGLE-522 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: H Lu >Assignee: H Lu >Priority: Major > Fix For: v0.5.1 > > Time Spent: 10m > Remaining Estimate: 0h > > Absence alert HOURLY_RULE is another use case for customers' needs. > We need to schedule jobs to be run every x hours. Current absence alert only > supports daily rule, but not our case. So HOURLY_RULE should be supported. > The policy for the hourly_rule should be like the following. > // "numOfFields, f1_name, f2_name, f1_value, f2_value, absenceWindowRuleType, > startTime, endTime, interval" > example: "1,jobID,job1,hourly_rule,2016-09-09 12:00:00,2016-09-09 > 13:00:00,10:00:00" > That being said, job1 starts during the period 2016-09-09 12:00:00 ~ > 2016-09-09 13:00:00, and the job should start again every 10:00:00 hours > after the period. > If not, absence alert will be triggered. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work logged] (EAGLE-1096) getJSONArray may cause exception, optJSONArray should be used
[ https://issues.apache.org/jira/browse/EAGLE-1096?focusedWorklogId=238970=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-238970 ] ASF GitHub Bot logged work on EAGLE-1096: - Author: ASF GitHub Bot Created on: 08/May/19 03:50 Start Date: 08/May/19 03:50 Worklog Time Spent: 10m Work Description: qingwen220 commented on pull request #1001: [EAGLE-1096] getJSONArray may cause exception, optJSONArray can be used URL: https://github.com/apache/eagle/pull/1001#discussion_r281904704 ## File path: eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/utils/JMXQueryHelper.java ## @@ -56,7 +56,7 @@ final Map resultMap = new HashMap(); final JSONTokener tokener = new JSONTokener(is); final JSONObject jsonBeansObject = new JSONObject(tokener); -final JSONArray jsonArray = jsonBeansObject.getJSONArray("beans"); +final JSONArray jsonArray = jsonBeansObject.optJSONArray("beans"); int size = jsonArray.length(); Review comment: Agree with @jhsenjaliya, this change will incur the NPE issue. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 238970) Time Spent: 0.5h (was: 20m) > getJSONArray may cause exception, optJSONArray should be used > - > > Key: EAGLE-1096 > URL: https://issues.apache.org/jira/browse/EAGLE-1096 > Project: Eagle > Issue Type: Bug >Reporter: bd2019us >Priority: Major > Attachments: 1.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Hello, > The method call jsonBeansObject.getJSONArray("beans") may throw > JSONException when the key does not exist, which will crash the program. To > ensure safety, optJSONArray is recommended to use, which will avoid the > exception in case no such key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (EAGLE-1096) getJSONArray may cause exception, optJSONArray should be used
[ https://issues.apache.org/jira/browse/EAGLE-1096?focusedWorklogId=227263=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-227263 ] ASF GitHub Bot logged work on EAGLE-1096: - Author: ASF GitHub Bot Created on: 14/Apr/19 01:03 Start Date: 14/Apr/19 01:03 Worklog Time Spent: 10m Work Description: bd2019us commented on pull request #1001: [EAGLE-1096] getJSONArray may cause exception, optJSONArray can be used URL: https://github.com/apache/eagle/pull/1001 Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 227263) Time Spent: 10m Remaining Estimate: 0h > getJSONArray may cause exception, optJSONArray should be used > - > > Key: EAGLE-1096 > URL: https://issues.apache.org/jira/browse/EAGLE-1096 > Project: Eagle > Issue Type: Bug >Reporter: bd2019us >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Hello, > The method call jsonBeansObject.getJSONArray("beans") may throw > JSONException when the key does not exist, which will crash the program. To > ensure safety, optJSONArray is recommended to use, which will avoid the > exception in case no such key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (EAGLE-1094) JSONObject.getString() may cause exception, optString() should be used.
[ https://issues.apache.org/jira/browse/EAGLE-1094?focusedWorklogId=221084=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-221084 ] ASF GitHub Bot logged work on EAGLE-1094: - Author: ASF GitHub Bot Created on: 01/Apr/19 05:00 Start Date: 01/Apr/19 05:00 Worklog Time Spent: 10m Work Description: bd2019us commented on pull request #1000: [EAGLE-1094] change JSONObject.getString() to optString() to avoid exception URL: https://github.com/apache/eagle/pull/1000 Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [x] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [x] Make sure tests pass via `mvn clean verify`. This command causes style. - [x] Replace `` in the title with the actual Jira issue number, if there is one. --- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 221084) Time Spent: 10m Remaining Estimate: 0h > JSONObject.getString() may cause exception, optString() should be used. > --- > > Key: EAGLE-1094 > URL: https://issues.apache.org/jira/browse/EAGLE-1094 > Project: Eagle > Issue Type: Bug >Reporter: bd2019us >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Locations: > (1) > eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/extractor/hdfs/HdfsTopologyEntityParser.java:158 > (2) > eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/extractor/hdfs/HdfsTopologyEntityParser.java:165 > (3) > eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/extractor/hdfs/HdfsTopologyEntityParser.java:180 > (4) > eagle-security/eagle-security-maprfs-web/src/main/java/org/apache/eagle/service/security/hdfs/resolver/MAPRFSVolumeResolver.java:117 > (5) > eagle-security/eagle-security-maprfs-web/src/main/java/org/apache/eagle/service/security/hdfs/rest/MapRNameResolver.java:65 > > JSONObject.getString(elem) would throw an exception if the key of "elem" does > not exist, which may cause the program crash. Therefore, another one > "optString()" should be used to avoid such kind of errors since it will > return a default value ("") and won't risk the program in crashing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-890) Add Job Scheduling Framework and HadoopHealthCheckApp
[ https://issues.apache.org/jira/browse/EAGLE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715810#comment-16715810 ] ASF GitHub Bot commented on EAGLE-890: -- Github user haoch closed the pull request at: https://github.com/apache/eagle/pull/799 > Add Job Scheduling Framework and HadoopHealthCheckApp > - > > Key: EAGLE-890 > URL: https://issues.apache.org/jira/browse/EAGLE-890 > Project: Eagle > Issue Type: New Feature > Components: Core::Job Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen >Priority: Major > Fix For: v0.5.1 > > > Add Job Scheduling Framework and HadoopHealthCheckApp -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1012) Some language level problems
[ https://issues.apache.org/jira/browse/EAGLE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689660#comment-16689660 ] ASF GitHub Bot commented on EAGLE-1012: --- Github user asdf2014 closed the pull request at: https://github.com/apache/eagle/pull/925 > Some language level problems > > > Key: EAGLE-1012 > URL: https://issues.apache.org/jira/browse/EAGLE-1012 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.5.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin >Priority: Major > Labels: JDK > Fix For: v0.6.0 > > Attachments: Eagle Language Level Problems.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Some language level problems > * Spell > * Duplicated > * Lambda > * Collection > * String > * instanceof > * Complex Method > * Exception > Details see attachment files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-946) Refactor MRRunningJobApp & HadoopQueueApp
[ https://issues.apache.org/jira/browse/EAGLE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685108#comment-16685108 ] ASF GitHub Bot commented on EAGLE-946: -- Github user wujinhu commented on the issue: https://github.com/apache/eagle/pull/869 mark > Refactor MRRunningJobApp & HadoopQueueApp > -- > > Key: EAGLE-946 > URL: https://issues.apache.org/jira/browse/EAGLE-946 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Major > Fix For: v0.5.0 > > > Requirements > 1. REST apis to the remote cluster should be called only once. > 2. For each request, the fetch running apps should be limits -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1090) make merge-pr script python 3 compatible
[ https://issues.apache.org/jira/browse/EAGLE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568896#comment-16568896 ] ASF GitHub Bot commented on EAGLE-1090: --- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/992 why this was closed and not merged? > make merge-pr script python 3 compatible > > > Key: EAGLE-1090 > URL: https://issues.apache.org/jira/browse/EAGLE-1090 > Project: Eagle > Issue Type: Improvement >Reporter: Jayesh >Assignee: Jayesh >Priority: Minor > > * use requests instead of urllib > * update print statements -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1088) Inconsistent method name
[ https://issues.apache.org/jira/browse/EAGLE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492870#comment-16492870 ] ASF GitHub Bot commented on EAGLE-1088: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/991 > Inconsistent method name > > > Key: EAGLE-1088 > URL: https://issues.apache.org/jira/browse/EAGLE-1088 > Project: Eagle > Issue Type: Improvement >Reporter: KuiLIU >Assignee: Edward Zhang >Priority: Major > > The following the method is named "find", but the method does not find > anything, just returns a boolean-variable 'this.matched'. Thus, rename method > as "isMatched" should be more clear than "find". > {code:java} > public boolean find() { > return this.matched; > } > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1090) make merge-pr script python 3 compatible
[ https://issues.apache.org/jira/browse/EAGLE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492866#comment-16492866 ] ASF GitHub Bot commented on EAGLE-1090: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/992 > make merge-pr script python 3 compatible > > > Key: EAGLE-1090 > URL: https://issues.apache.org/jira/browse/EAGLE-1090 > Project: Eagle > Issue Type: Improvement >Reporter: Jayesh >Assignee: Jayesh >Priority: Minor > > * use requests instead of urllib > * update print statements -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1088) Inconsistent method name
[ https://issues.apache.org/jira/browse/EAGLE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482042#comment-16482042 ] ASF GitHub Bot commented on EAGLE-1088: --- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/991 @BruceKuiLiu, I believe this is consistent with Java.Pattern class method where find will return true/false based on pattern match. I would let @yonzhang comment further on this. Thanks for the PR though. > Inconsistent method name > > > Key: EAGLE-1088 > URL: https://issues.apache.org/jira/browse/EAGLE-1088 > Project: Eagle > Issue Type: Improvement >Reporter: KuiLIU >Priority: Major > > The following the method is named "find", but the method does not find > anything, just returns a boolean-variable 'this.matched'. Thus, rename method > as "isMatched" should be more clear than "find". > {code:java} > public boolean find() { > return this.matched; > } > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1088) Inconsistent method name
[ https://issues.apache.org/jira/browse/EAGLE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446977#comment-16446977 ] ASF GitHub Bot commented on EAGLE-1088: --- GitHub user BruceKuiLiu opened a pull request: https://github.com/apache/eagle/pull/991 EAGLE-1088: Change the inconsistent method name 'find'. Change the method name 'find' to 'isMatched'. The method is named "find", but the method does not find anything, just returns a boolean-variable 'this.matched'. Thus, rename method as "isMatched" should be more clear than "find". You can merge this pull request into a Git repository by running: $ git pull https://github.com/BruceKuiLiu/eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/991.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #991 commit 86e564bab1f9ec52cc653fd04a00f7893ba7a8c1 Author: Kui LIUDate: 2018-04-21T20:28:19Z Change the method name 'find' to 'isMatched'. > Inconsistent method name > > > Key: EAGLE-1088 > URL: https://issues.apache.org/jira/browse/EAGLE-1088 > Project: Eagle > Issue Type: Improvement >Reporter: KuiLIU >Priority: Major > > The following the method is named "find", but the method does not find > anything, just returns a boolean-variable 'this.matched'. Thus, rename method > as "isMatched" should be more clear than "find". > {code:java} > public boolean find() { > return this.matched; > } > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-879) Using Slack Notification throws ClassNotFoundException
[ https://issues.apache.org/jira/browse/EAGLE-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425149#comment-16425149 ] ASF GitHub Bot commented on EAGLE-879: -- Github user coheigea closed the pull request at: https://github.com/apache/eagle/pull/984 > Using Slack Notification throws ClassNotFoundException > -- > > Key: EAGLE-879 > URL: https://issues.apache.org/jira/browse/EAGLE-879 > Project: Eagle > Issue Type: Bug >Reporter: Jayesh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > looks like http-core jar from the httpcomponent jar pacakge is missing which > includes the class used in ullink slackclient > {code} > 2017-01-19 19:29:15.879 c.u.s.s.i.SlackWebSocketSessionImpl [INFO] connecting > to slack > 2017-01-19 19:29:15.879 o.a.c.f.l.ListenerContainer [ERROR] Listener > (org.apache.eagle.alert.config.ConfigBusConsumer$$Lambda$12/1246291106@3566e264) > threw an exception > java.lang.NoClassDefFoundError: org/apache/http/config/Lookup > at > com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.getHttpClient(SlackWebSocketSessionImpl.java:707) > ~[stormjar.jar:?] > at > com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.connectImpl(SlackWebSocketSessionImpl.java:254) > ~[stormjar.jar:?] > at > com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.connect(SlackWebSocketSessionImpl.java:232) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertSlackPublisher.init(AlertSlackPublisher.java:62) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublishPluginsFactory.createNotificationPlugin(AlertPublishPluginsFactory.java:42) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:129) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:134) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNotifyService.java:103) > ~[stormjar.jar:?] > at java.util.ArrayList.forEach(ArrayList.java:1249) ~[?:1.8.0_102] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyService.java:103) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:137) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44) > ~[stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293) > ~[stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287) > ~[stormjar.jar:?] > at > org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92) > [stormjar.jar:?] > at > com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:297) > [stormjar.jar:?] > at > org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83) > [stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284) > [stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252) > [stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53) > [stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111) > [stormjar.jar:?] > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730) > [stormjar.jar:?] > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516) > [stormjar.jar:?] > at > org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254) > [stormjar.jar:?] > at > org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) > [stormjar.jar:?] > at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) > [stormjar.jar:?] > Caused by: java.lang.ClassNotFoundException: org.apache.http.config.Lookup > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > ~[?:1.8.0_102] > at
[jira] [Commented] (EAGLE-879) Using Slack Notification throws ClassNotFoundException
[ https://issues.apache.org/jira/browse/EAGLE-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424761#comment-16424761 ] ASF GitHub Bot commented on EAGLE-879: -- Github user yonzhang commented on the issue: https://github.com/apache/eagle/pull/984 I have merge this PR, but somehow have not closed it automatically. Can you please manually close it? @coheigea > Using Slack Notification throws ClassNotFoundException > -- > > Key: EAGLE-879 > URL: https://issues.apache.org/jira/browse/EAGLE-879 > Project: Eagle > Issue Type: Bug >Reporter: Jayesh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > looks like http-core jar from the httpcomponent jar pacakge is missing which > includes the class used in ullink slackclient > {code} > 2017-01-19 19:29:15.879 c.u.s.s.i.SlackWebSocketSessionImpl [INFO] connecting > to slack > 2017-01-19 19:29:15.879 o.a.c.f.l.ListenerContainer [ERROR] Listener > (org.apache.eagle.alert.config.ConfigBusConsumer$$Lambda$12/1246291106@3566e264) > threw an exception > java.lang.NoClassDefFoundError: org/apache/http/config/Lookup > at > com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.getHttpClient(SlackWebSocketSessionImpl.java:707) > ~[stormjar.jar:?] > at > com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.connectImpl(SlackWebSocketSessionImpl.java:254) > ~[stormjar.jar:?] > at > com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.connect(SlackWebSocketSessionImpl.java:232) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertSlackPublisher.init(AlertSlackPublisher.java:62) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublishPluginsFactory.createNotificationPlugin(AlertPublishPluginsFactory.java:42) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:129) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:134) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNotifyService.java:103) > ~[stormjar.jar:?] > at java.util.ArrayList.forEach(ArrayList.java:1249) ~[?:1.8.0_102] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyService.java:103) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:137) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44) > ~[stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293) > ~[stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287) > ~[stormjar.jar:?] > at > org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92) > [stormjar.jar:?] > at > com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:297) > [stormjar.jar:?] > at > org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83) > [stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284) > [stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252) > [stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53) > [stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111) > [stormjar.jar:?] > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730) > [stormjar.jar:?] > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516) > [stormjar.jar:?] > at > org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254) > [stormjar.jar:?] > at > org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) > [stormjar.jar:?] > at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) > [stormjar.jar:?] > Caused by: java.lang.ClassNotFoundException: org.apache.http.config.Lookup > at
[jira] [Commented] (EAGLE-1084) Apply checkstyle fixes to eagle-storage-base module
[ https://issues.apache.org/jira/browse/EAGLE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424729#comment-16424729 ] ASF GitHub Bot commented on EAGLE-1084: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/988 > Apply checkstyle fixes to eagle-storage-base module > --- > > Key: EAGLE-1084 > URL: https://issues.apache.org/jira/browse/EAGLE-1084 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: v0.5.1 > > > Apply checkstyle fixes to eagle-storage-base module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1084) Apply checkstyle fixes to eagle-storage-base module
[ https://issues.apache.org/jira/browse/EAGLE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355305#comment-16355305 ] ASF GitHub Bot commented on EAGLE-1084: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/988 EAGLE-1084 - Apply checkstyle fixes to eagle-storage-base module Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-1084 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/988.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #988 commit 677159acde72601b151a192980eb2e5704a9e824 Author: Colm O hEigeartaighDate: 2018-02-07T10:48:01Z EAGLE-1084 - Apply checkstyle fixes to eagle-storage-base module > Apply checkstyle fixes to eagle-storage-base module > --- > > Key: EAGLE-1084 > URL: https://issues.apache.org/jira/browse/EAGLE-1084 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: v0.5.1 > > > Apply checkstyle fixes to eagle-storage-base module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1081) Checkstyle fixes for eagle-entity-base module
[ https://issues.apache.org/jira/browse/EAGLE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355063#comment-16355063 ] ASF GitHub Bot commented on EAGLE-1081: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/985 > Checkstyle fixes for eagle-entity-base module > - > > Key: EAGLE-1081 > URL: https://issues.apache.org/jira/browse/EAGLE-1081 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > This task is to apply checkstyle fixes for the eagle-entity-base module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1081) Checkstyle fixes for eagle-entity-base module
[ https://issues.apache.org/jira/browse/EAGLE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355062#comment-16355062 ] ASF GitHub Bot commented on EAGLE-1081: --- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/985 +1 > Checkstyle fixes for eagle-entity-base module > - > > Key: EAGLE-1081 > URL: https://issues.apache.org/jira/browse/EAGLE-1081 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > This task is to apply checkstyle fixes for the eagle-entity-base module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1082) The server script can't be started from the same directory
[ https://issues.apache.org/jira/browse/EAGLE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355058#comment-16355058 ] ASF GitHub Bot commented on EAGLE-1082: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/986 > The server script can't be started from the same directory > -- > > Key: EAGLE-1082 > URL: https://issues.apache.org/jira/browse/EAGLE-1082 > Project: Eagle > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > As reported here on the mailing list, it's not possible to run > "./eagle-server.sh start". Instead it must be run from the "bin" directory: > > http://mail-archives.apache.org/mod_mbox/eagle-dev/201802.mbox/%3CCAB8XdGAAb1EvRjc09uNjbBYJ-SXaDo10eqXgLpYaucx_u6nf_A%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1083) Upgrade Storm to 0.9.7
[ https://issues.apache.org/jira/browse/EAGLE-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355057#comment-16355057 ] ASF GitHub Bot commented on EAGLE-1083: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/987 > Upgrade Storm to 0.9.7 > -- > > Key: EAGLE-1083 > URL: https://issues.apache.org/jira/browse/EAGLE-1083 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > We should update Storm to the latest minor release of 0.9.x (0.9.7). In > addition, we are using two different versions of Kafka which should be > aligned. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1083) Upgrade Storm to 0.9.7
[ https://issues.apache.org/jira/browse/EAGLE-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353810#comment-16353810 ] ASF GitHub Bot commented on EAGLE-1083: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/987 EAGLE-1083 - Upgrade Storm to 0.9.7 Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-1083 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/987.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #987 commit eb3c29fc10592c71bc82afcc02ebc4512dc32dce Author: Colm O hEigeartaighDate: 2018-02-06T12:35:56Z EAGLE-1083 - Upgrade Storm to 0.9.7 > Upgrade Storm to 0.9.7 > -- > > Key: EAGLE-1083 > URL: https://issues.apache.org/jira/browse/EAGLE-1083 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > We should update Storm to the latest minor release of 0.9.x (0.9.7). In > addition, we are using two different versions of Kafka which should be > aligned. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1082) The server script can't be started from the same directory
[ https://issues.apache.org/jira/browse/EAGLE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352701#comment-16352701 ] ASF GitHub Bot commented on EAGLE-1082: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/986 EAGLE-1082 - The server script can't be started from the same directory Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-1082 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/986.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #986 commit 82871bebf3eb0e88c1c2463273fbf3bc21d9a878 Author: Colm O hEigeartaighDate: 2018-02-05T17:59:02Z EAGLE-1082 - The server script can't be started from the same directory > The server script can't be started from the same directory > -- > > Key: EAGLE-1082 > URL: https://issues.apache.org/jira/browse/EAGLE-1082 > Project: Eagle > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > As reported here on the mailing list, it's not possible to run > "./eagle-server.sh start". Instead it must be run from the "bin" directory: > > http://mail-archives.apache.org/mod_mbox/eagle-dev/201802.mbox/%3CCAB8XdGAAb1EvRjc09uNjbBYJ-SXaDo10eqXgLpYaucx_u6nf_A%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1081) Checkstyle fixes for eagle-entity-base module
[ https://issues.apache.org/jira/browse/EAGLE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352324#comment-16352324 ] ASF GitHub Bot commented on EAGLE-1081: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/985 EAGLE-1081 - Checkstyle fixes for eagle-entity-base module Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-1081 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/985.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #985 commit 1460e520c79ac8a52ad4e1286d0ac0f98f6ea162 Author: Colm O hEigeartaighDate: 2018-02-05T12:34:33Z EAGLE-1081 - Checkstyle fixes for eagle-entity-base module > Checkstyle fixes for eagle-entity-base module > - > > Key: EAGLE-1081 > URL: https://issues.apache.org/jira/browse/EAGLE-1081 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > This task is to apply checkstyle fixes for the eagle-entity-base module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError
[ https://issues.apache.org/jira/browse/EAGLE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350845#comment-16350845 ] ASF GitHub Bot commented on EAGLE-968: -- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/941 Thanks @rushikesavareddy for the PR and @coheigea for verifying. merging it now. > using Email Notification Feature throws IncompatibleClassChangeError > > > Key: EAGLE-968 > URL: https://issues.apache.org/jira/browse/EAGLE-968 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Jayesh >Assignee: Jayesh >Priority: Major > Fix For: v0.5.1 > > Attachments: 941.patch > > > {code} > 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator > Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to > @gmail.com,@gmail.com, due > to:java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:1.8.0_102] > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > ~[?:1.8.0_102] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92) > [stormjar.jar:?] > at > org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846) > [storm-core-1.0.3.jar:1.0.3] > at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) > [storm-core-1.0.3.jar:1.0.3] > at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?] > at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102] > Caused by: java.lang.IncompatibleClassChangeError: Implementing class > at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_102] > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > ~[?:1.8.0_102] > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > ~[?:1.8.0_102] > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > ~[?:1.8.0_102] > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) ~[?:1.8.0_102] > at java.security.AccessController.doPrivileged(Native Method) > ~[?:1.8.0_102] > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_102] > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_102] > at > org.apache.velocity.runtime.log.Log4JLogChute.initAppender(Log4JLogChute.java:118) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.Log4JLogChute.init(Log4JLogChute.java:85) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:157) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.LogManager.updateLog(LogManager.java:269) >
[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError
[ https://issues.apache.org/jira/browse/EAGLE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350844#comment-16350844 ] ASF GitHub Bot commented on EAGLE-968: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/941 > using Email Notification Feature throws IncompatibleClassChangeError > > > Key: EAGLE-968 > URL: https://issues.apache.org/jira/browse/EAGLE-968 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Jayesh >Assignee: Jayesh >Priority: Major > Fix For: v0.5.1 > > Attachments: 941.patch > > > {code} > 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator > Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to > @gmail.com,@gmail.com, due > to:java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:1.8.0_102] > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > ~[?:1.8.0_102] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92) > [stormjar.jar:?] > at > org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846) > [storm-core-1.0.3.jar:1.0.3] > at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) > [storm-core-1.0.3.jar:1.0.3] > at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?] > at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102] > Caused by: java.lang.IncompatibleClassChangeError: Implementing class > at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_102] > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > ~[?:1.8.0_102] > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > ~[?:1.8.0_102] > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > ~[?:1.8.0_102] > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) ~[?:1.8.0_102] > at java.security.AccessController.doPrivileged(Native Method) > ~[?:1.8.0_102] > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_102] > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_102] > at > org.apache.velocity.runtime.log.Log4JLogChute.initAppender(Log4JLogChute.java:118) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.Log4JLogChute.init(Log4JLogChute.java:85) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:157) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.LogManager.updateLog(LogManager.java:269) > ~[stormjar.jar:?] > at >
[jira] [Commented] (EAGLE-879) Using Slack Notification throws ClassNotFoundException
[ https://issues.apache.org/jira/browse/EAGLE-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350653#comment-16350653 ] ASF GitHub Bot commented on EAGLE-879: -- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/984 EAGLE-879 - Using Slack Notification throws ClassNotFoundException Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-879 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/984.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #984 commit fc493e78c90e3a5d6a17b0c9188dfbd9db5b73d8 Author: Colm O hEigeartaighDate: 2018-02-02T17:00:07Z EAGLE-879 - Using Slack Notification throws ClassNotFoundException > Using Slack Notification throws ClassNotFoundException > -- > > Key: EAGLE-879 > URL: https://issues.apache.org/jira/browse/EAGLE-879 > Project: Eagle > Issue Type: Bug >Reporter: Jayesh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > looks like http-core jar from the httpcomponent jar pacakge is missing which > includes the class used in ullink slackclient > {code} > 2017-01-19 19:29:15.879 c.u.s.s.i.SlackWebSocketSessionImpl [INFO] connecting > to slack > 2017-01-19 19:29:15.879 o.a.c.f.l.ListenerContainer [ERROR] Listener > (org.apache.eagle.alert.config.ConfigBusConsumer$$Lambda$12/1246291106@3566e264) > threw an exception > java.lang.NoClassDefFoundError: org/apache/http/config/Lookup > at > com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.getHttpClient(SlackWebSocketSessionImpl.java:707) > ~[stormjar.jar:?] > at > com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.connectImpl(SlackWebSocketSessionImpl.java:254) > ~[stormjar.jar:?] > at > com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.connect(SlackWebSocketSessionImpl.java:232) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertSlackPublisher.init(AlertSlackPublisher.java:62) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublishPluginsFactory.createNotificationPlugin(AlertPublishPluginsFactory.java:42) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:129) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:134) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNotifyService.java:103) > ~[stormjar.jar:?] > at java.util.ArrayList.forEach(ArrayList.java:1249) ~[?:1.8.0_102] > at > org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyService.java:103) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:137) > ~[stormjar.jar:?] > at > org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44) > ~[stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293) > ~[stormjar.jar:?] > at > org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287) > ~[stormjar.jar:?] > at > org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92) > [stormjar.jar:?] > at > com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:297) > [stormjar.jar:?] > at > org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83) > [stormjar.jar:?] > at >
[jira] [Commented] (EAGLE-1080) Fix checkstyle errors in the eagle-query-base module
[ https://issues.apache.org/jira/browse/EAGLE-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350217#comment-16350217 ] ASF GitHub Bot commented on EAGLE-1080: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/983 EAGLE-1080 - Fix checkstyle errors in the eagle-query-base module Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle eagle-query-base-checkstyle Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/983.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #983 commit 22c6727fe9386534dd389103570abb63223fe770 Author: Colm O hEigeartaighDate: 2018-02-02T12:08:01Z EAGLE-1080 - Fix checkstyle errors in the eagle-query-base module > Fix checkstyle errors in the eagle-query-base module > > > Key: EAGLE-1080 > URL: https://issues.apache.org/jira/browse/EAGLE-1080 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1071) Login form takes empty entries
[ https://issues.apache.org/jira/browse/EAGLE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349475#comment-16349475 ] ASF GitHub Bot commented on EAGLE-1071: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/972 > Login form takes empty entries > --- > > Key: EAGLE-1071 > URL: https://issues.apache.org/jira/browse/EAGLE-1071 > Project: Eagle > Issue Type: Bug > Components: Core::Eagle Server >Reporter: VSJTech >Priority: Minor > Fix For: v0.5.0 > > > After Ldap integration the login successfully returns to home with the > username near the user icon. > But when provided empty entries it takes and on submission reports username > or password is incorrect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1074) eagle-docker.sh uses the wrong path
[ https://issues.apache.org/jira/browse/EAGLE-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349468#comment-16349468 ] ASF GitHub Bot commented on EAGLE-1074: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/976 > eagle-docker.sh uses the wrong path > --- > > Key: EAGLE-1074 > URL: https://issues.apache.org/jira/browse/EAGLE-1074 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Colm O hEigeartaigh >Priority: Trivial > > The eagle-docker.sh script uses the wrong path. When run from the "bin" > directory, it ends up going back one directory too far. > PR opened: https://github.com/apache/eagle/pull/976 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1078) Remove references to the "incubator" from the source
[ https://issues.apache.org/jira/browse/EAGLE-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349464#comment-16349464 ] ASF GitHub Bot commented on EAGLE-1078: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/981 > Remove references to the "incubator" from the source > > > Key: EAGLE-1078 > URL: https://issues.apache.org/jira/browse/EAGLE-1078 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1079) Fix checkstyle issues in antlr module
[ https://issues.apache.org/jira/browse/EAGLE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349457#comment-16349457 ] ASF GitHub Bot commented on EAGLE-1079: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/982 > Fix checkstyle issues in antlr module > - > > Key: EAGLE-1079 > URL: https://issues.apache.org/jira/browse/EAGLE-1079 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1079) Fix checkstyle issues in antlr module
[ https://issues.apache.org/jira/browse/EAGLE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349358#comment-16349358 ] ASF GitHub Bot commented on EAGLE-1079: --- Github user yonzhang commented on the issue: https://github.com/apache/eagle/pull/982 LGTM, thanks for fixing style check > Fix checkstyle issues in antlr module > - > > Key: EAGLE-1079 > URL: https://issues.apache.org/jira/browse/EAGLE-1079 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1078) Remove references to the "incubator" from the source
[ https://issues.apache.org/jira/browse/EAGLE-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349355#comment-16349355 ] ASF GitHub Bot commented on EAGLE-1078: --- Github user yonzhang commented on the issue: https://github.com/apache/eagle/pull/981 Nice, LGTM > Remove references to the "incubator" from the source > > > Key: EAGLE-1078 > URL: https://issues.apache.org/jira/browse/EAGLE-1078 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1079) Fix checkstyle issues in antlr module
[ https://issues.apache.org/jira/browse/EAGLE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348835#comment-16348835 ] ASF GitHub Bot commented on EAGLE-1079: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/982 EAGLE-1079 - Fix checkstyle issues in antlr module Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-1079 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/982.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #982 commit ff807084e963fde65285e60a48dfb764012c3f8f Author: Colm O hEigeartaighDate: 2018-02-01T16:18:31Z EAGLE-1079 - Fix checkstyle issues in antlr module > Fix checkstyle issues in antlr module > - > > Key: EAGLE-1079 > URL: https://issues.apache.org/jira/browse/EAGLE-1079 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError
[ https://issues.apache.org/jira/browse/EAGLE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348775#comment-16348775 ] ASF GitHub Bot commented on EAGLE-968: -- Github user coheigea commented on the issue: https://github.com/apache/eagle/pull/941 I tested this by removing the extraneous commits (see https://issues.apache.org/jira/secure/attachment/12908828/941.patch) and it works fine. > using Email Notification Feature throws IncompatibleClassChangeError > > > Key: EAGLE-968 > URL: https://issues.apache.org/jira/browse/EAGLE-968 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Jayesh >Assignee: Jayesh >Priority: Major > Fix For: v0.5.1 > > Attachments: 941.patch > > > {code} > 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator > Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to > @gmail.com,@gmail.com, due > to:java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:1.8.0_102] > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > ~[?:1.8.0_102] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92) > [stormjar.jar:?] > at > org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846) > [storm-core-1.0.3.jar:1.0.3] > at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) > [storm-core-1.0.3.jar:1.0.3] > at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?] > at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102] > Caused by: java.lang.IncompatibleClassChangeError: Implementing class > at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_102] > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > ~[?:1.8.0_102] > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > ~[?:1.8.0_102] > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > ~[?:1.8.0_102] > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) ~[?:1.8.0_102] > at java.security.AccessController.doPrivileged(Native Method) > ~[?:1.8.0_102] > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_102] > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_102] > at > org.apache.velocity.runtime.log.Log4JLogChute.initAppender(Log4JLogChute.java:118) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.Log4JLogChute.init(Log4JLogChute.java:85) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:157) > ~[stormjar.jar:?] > at >
[jira] [Commented] (EAGLE-1078) Remove references to the "incubator" from the source
[ https://issues.apache.org/jira/browse/EAGLE-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348637#comment-16348637 ] ASF GitHub Bot commented on EAGLE-1078: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/981 EAGLE-1078 - Remove references to the "incubator" from the source Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-1078 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/981.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #981 commit 36dc4ff3b5f67a1bb8fd5321367cf60601ae2f4b Author: Colm O hEigeartaighDate: 2018-02-01T14:19:58Z EAGLE-1078 - Remove references to the "incubator" from the source > Remove references to the "incubator" from the source > > > Key: EAGLE-1078 > URL: https://issues.apache.org/jira/browse/EAGLE-1078 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1075) Can't specify configuration options for AlertFilePublisher
[ https://issues.apache.org/jira/browse/EAGLE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347471#comment-16347471 ] ASF GitHub Bot commented on EAGLE-1075: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/978 > Can't specify configuration options for AlertFilePublisher > -- > > Key: EAGLE-1075 > URL: https://issues.apache.org/jira/browse/EAGLE-1075 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > Right now it's not possible to specify the configuration options for the > AlertFilePublisher in the UI. So for example we can't configure the file > name/path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1075) Can't specify configuration options for AlertFilePublisher
[ https://issues.apache.org/jira/browse/EAGLE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347467#comment-16347467 ] ASF GitHub Bot commented on EAGLE-1075: --- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/978 +1, merging since its improved than earlier and more improvements can be later. Thanks for the PR. > Can't specify configuration options for AlertFilePublisher > -- > > Key: EAGLE-1075 > URL: https://issues.apache.org/jira/browse/EAGLE-1075 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > Right now it's not possible to specify the configuration options for the > AlertFilePublisher in the UI. So for example we can't configure the file > name/path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1075) Can't specify configuration options for AlertFilePublisher
[ https://issues.apache.org/jira/browse/EAGLE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347461#comment-16347461 ] ASF GitHub Bot commented on EAGLE-1075: --- Github user jhsenjaliya commented on a diff in the pull request: https://github.com/apache/eagle/pull/978#discussion_r165162632 --- Diff: eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/impl/AlertFilePublisher.java --- @@ -54,13 +54,26 @@ public void init(Config config, Publishment publishment, Map conf) throws Except int numOfFiles = DEFAULT_FILE_NUMBER; if (publishment.getProperties() != null) { if (publishment.getProperties().containsKey(PublishConstants.FILE_NAME)) { -fileName = (String) publishment.getProperties().get(PublishConstants.FILE_NAME); +String property = (String) publishment.getProperties().get(PublishConstants.FILE_NAME); +if (property != null && !"".equals(property)) { +fileName = property; +} } if (publishment.getProperties().containsKey(PublishConstants.ROTATE_EVERY_KB)) { -rotateSize = Integer.valueOf(publishment.getProperties().get(PublishConstants.ROTATE_EVERY_KB).toString()); +Object property = publishment.getProperties().get(PublishConstants.ROTATE_EVERY_KB); +if (property instanceof Integer) { +rotateSize = (Integer)property; +} else if (property instanceof String && !"".equals((String)property)) { --- End diff -- could also check for null once its is instanceof string. > Can't specify configuration options for AlertFilePublisher > -- > > Key: EAGLE-1075 > URL: https://issues.apache.org/jira/browse/EAGLE-1075 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > Right now it's not possible to specify the configuration options for the > AlertFilePublisher in the UI. So for example we can't configure the file > name/path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1077) Set the secure processing feature on all DocumentBuilderFactory instances
[ https://issues.apache.org/jira/browse/EAGLE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347457#comment-16347457 ] ASF GitHub Bot commented on EAGLE-1077: --- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/980 +1, merging.. Thanks for the PR. > Set the secure processing feature on all DocumentBuilderFactory instances > - > > Key: EAGLE-1077 > URL: https://issues.apache.org/jira/browse/EAGLE-1077 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > We should set the secure processing feature on all DocumentBuilderFactory > instances, to prevent attacks such as XXE attacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1077) Set the secure processing feature on all DocumentBuilderFactory instances
[ https://issues.apache.org/jira/browse/EAGLE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347456#comment-16347456 ] ASF GitHub Bot commented on EAGLE-1077: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/980 > Set the secure processing feature on all DocumentBuilderFactory instances > - > > Key: EAGLE-1077 > URL: https://issues.apache.org/jira/browse/EAGLE-1077 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > We should set the secure processing feature on all DocumentBuilderFactory > instances, to prevent attacks such as XXE attacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-331) avoid to use junit.framework.Assert
[ https://issues.apache.org/jira/browse/EAGLE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347334#comment-16347334 ] ASF GitHub Bot commented on EAGLE-331: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/979 > avoid to use junit.framework.Assert > --- > > Key: EAGLE-331 > URL: https://issues.apache.org/jira/browse/EAGLE-331 > Project: Eagle > Issue Type: Bug >Reporter: Edward Zhang >Assignee: Lingang Deng >Priority: Trivial > > all eagle code should not use deprecated Assert -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1077) Set the secure processing feature on all DocumentBuilderFactory instances
[ https://issues.apache.org/jira/browse/EAGLE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347226#comment-16347226 ] ASF GitHub Bot commented on EAGLE-1077: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/980 EAGLE-1077 - Set the secure processing feature on all DocumentBuilder… …Factory instances Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-1077 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/980.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #980 commit a380163ae3771beacefe6fcacf29bd9abe66ced8 Author: Colm O hEigeartaighDate: 2018-01-31T17:23:41Z EAGLE-1077 - Set the secure processing feature on all DocumentBuilderFactory instances > Set the secure processing feature on all DocumentBuilderFactory instances > - > > Key: EAGLE-1077 > URL: https://issues.apache.org/jira/browse/EAGLE-1077 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > We should set the secure processing feature on all DocumentBuilderFactory > instances, to prevent attacks such as XXE attacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-331) avoid to use junit.framework.Assert
[ https://issues.apache.org/jira/browse/EAGLE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347166#comment-16347166 ] ASF GitHub Bot commented on EAGLE-331: -- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/979 EAGLE-331 - avoid to use junit.framework.Assert Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-331 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/979.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #979 commit 1b72b39893eef46e893bb4295355d67ac477e23a Author: Colm O hEigeartaighDate: 2018-01-31T16:54:01Z EAGLE-331 - avoid to use junit.framework.Assert > avoid to use junit.framework.Assert > --- > > Key: EAGLE-331 > URL: https://issues.apache.org/jira/browse/EAGLE-331 > Project: Eagle > Issue Type: Bug >Reporter: Edward Zhang >Assignee: Lingang Deng >Priority: Trivial > > all eagle code should not use deprecated Assert -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1075) Can't specify configuration options for AlertFilePublisher
[ https://issues.apache.org/jira/browse/EAGLE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346991#comment-16346991 ] ASF GitHub Bot commented on EAGLE-1075: --- GitHub user coheigea reopened a pull request: https://github.com/apache/eagle/pull/978 EAGLE-1075 - Can't specify configuration options for AlertFilePublisher Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-1075 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/978.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #978 commit fb3868a8532a6e3b40c305ddd3d317b3fc8e1a29 Author: Colm O hEigeartaighDate: 2018-01-31T15:15:57Z EAGLE-1075 - Can't specify configuration options for AlertFilePublisher > Can't specify configuration options for AlertFilePublisher > -- > > Key: EAGLE-1075 > URL: https://issues.apache.org/jira/browse/EAGLE-1075 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > Right now it's not possible to specify the configuration options for the > AlertFilePublisher in the UI. So for example we can't configure the file > name/path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1025) bump version on master
[ https://issues.apache.org/jira/browse/EAGLE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346142#comment-16346142 ] ASF GitHub Bot commented on EAGLE-1025: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/936 > bump version on master > -- > > Key: EAGLE-1025 > URL: https://issues.apache.org/jira/browse/EAGLE-1025 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh >Priority: Minor > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1051) Check if a publisher can be deleted
[ https://issues.apache.org/jira/browse/EAGLE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345925#comment-16345925 ] ASF GitHub Bot commented on EAGLE-1051: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/959 > Check if a publisher can be deleted > > > Key: EAGLE-1051 > URL: https://issues.apache.org/jira/browse/EAGLE-1051 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Major > Fix For: v0.5.1 > > > A publisher can be deleted only when there are no policies using it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1051) Check if a publisher can be deleted
[ https://issues.apache.org/jira/browse/EAGLE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345921#comment-16345921 ] ASF GitHub Bot commented on EAGLE-1051: --- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/959 merging this in master which is 0.5.1 now. @qingwen220 Thanks for the PR. @haoch Thanks for the review. > Check if a publisher can be deleted > > > Key: EAGLE-1051 > URL: https://issues.apache.org/jira/browse/EAGLE-1051 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Major > Fix For: v0.5.1 > > > A publisher can be deleted only when there are no policies using it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1025) bump version on master
[ https://issues.apache.org/jira/browse/EAGLE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339142#comment-16339142 ] ASF GitHub Bot commented on EAGLE-1025: --- Github user coheigea commented on the issue: https://github.com/apache/eagle/pull/936 The patch doesn't apply any more, as it assumes the current version is 0.5.0-SNAPSHOT. > bump version on master > -- > > Key: EAGLE-1025 > URL: https://issues.apache.org/jira/browse/EAGLE-1025 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh >Priority: Minor > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1075) Can't specify configuration options for AlertFilePublisher
[ https://issues.apache.org/jira/browse/EAGLE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337509#comment-16337509 ] ASF GitHub Bot commented on EAGLE-1075: --- Github user coheigea closed the pull request at: https://github.com/apache/eagle/pull/977 > Can't specify configuration options for AlertFilePublisher > -- > > Key: EAGLE-1075 > URL: https://issues.apache.org/jira/browse/EAGLE-1075 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > > Right now it's not possible to specify the configuration options for the > AlertFilePublisher in the UI. So for example we can't configure the file > name/path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1075) Can't specify configuration options for AlertFilePublisher
[ https://issues.apache.org/jira/browse/EAGLE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337505#comment-16337505 ] ASF GitHub Bot commented on EAGLE-1075: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/977 EAGLE-1075 - Can't specify configuration options for AlertFilePublisher Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/977.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #977 commit 08241fd810803b8c0ba548f4592abefd395b43cc Author: Colm O hEigeartaighDate: 2018-01-24T12:24:26Z EAGLE-1075 - Can't specify configuration options for AlertFilePublisher > Can't specify configuration options for AlertFilePublisher > -- > > Key: EAGLE-1075 > URL: https://issues.apache.org/jira/browse/EAGLE-1075 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > > Right now it's not possible to specify the configuration options for the > AlertFilePublisher in the UI. So for example we can't configure the file > name/path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1074) eagle-docker.sh uses the wrong path
[ https://issues.apache.org/jira/browse/EAGLE-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326418#comment-16326418 ] ASF GitHub Bot commented on EAGLE-1074: --- GitHub user coheigea opened a pull request: https://github.com/apache/eagle/pull/976 EAGLE-1074 - eagle-docker.sh uses the wrong path Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/eagle EAGLE-1074 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/976.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #976 commit 54a86523b306099f0c18f0b4218036a6afd432af Author: Colm O hEigeartaighDate: 2018-01-15T17:17:11Z EAGLE-1074 - eagle-docker.sh uses the wrong path > eagle-docker.sh uses the wrong path > --- > > Key: EAGLE-1074 > URL: https://issues.apache.org/jira/browse/EAGLE-1074 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Colm O hEigeartaigh >Priority: Trivial > > The eagle-docker.sh script uses the wrong path. When run from the "bin" > directory, it ends up going back one directory too far. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1072) Download links incorrect
[ https://issues.apache.org/jira/browse/EAGLE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326369#comment-16326369 ] ASF GitHub Bot commented on EAGLE-1072: --- Github user coheigea closed the pull request at: https://github.com/apache/eagle/pull/974 > Download links incorrect > > > Key: EAGLE-1072 > URL: https://issues.apache.org/jira/browse/EAGLE-1072 > Project: Eagle > Issue Type: Improvement > Components: Documentation >Affects Versions: v0.5.0 >Reporter: Colm O hEigeartaigh >Assignee: Hao Chen >Priority: Major > Fix For: v0.5.0 > > Attachments: EAGLE-1072.patch > > > The main download link for Eagle 0.5.0 is incorrect, as is the link for the > SHA digest. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-1072) Download links incorrect
[ https://issues.apache.org/jira/browse/EAGLE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312431#comment-16312431 ] ASF GitHub Bot commented on EAGLE-1072: --- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/974 LGTM, thanks very much! > Download links incorrect > > > Key: EAGLE-1072 > URL: https://issues.apache.org/jira/browse/EAGLE-1072 > Project: Eagle > Issue Type: Improvement > Components: Documentation >Affects Versions: v0.5.0 >Reporter: Colm O hEigeartaigh >Assignee: Hao Chen > Fix For: v0.5.0 > > Attachments: EAGLE-1072.patch > > > The main download link for Eagle 0.5.0 is incorrect, as is the link for the > SHA digest. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1071) Login form takes empty entries
[ https://issues.apache.org/jira/browse/EAGLE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301083#comment-16301083 ] ASF GitHub Bot commented on EAGLE-1071: --- Github user zombieJ commented on a diff in the pull request: https://github.com/apache/eagle/pull/972#discussion_r158444289 --- Diff: eagle-server/src/main/webapp/app/dev/public/js/ctrls/authCtrl.js --- @@ -26,6 +26,14 @@ $scope.password = ''; $scope.login = function () { + if (!$scope.username || !$scope.password) --- End diff -- Hi @VSJTech, Look good to me. And could you help to format the code? Thanks > Login form takes empty entries > --- > > Key: EAGLE-1071 > URL: https://issues.apache.org/jira/browse/EAGLE-1071 > Project: Eagle > Issue Type: Bug > Components: Core::Eagle Server >Reporter: VSJTech >Priority: Minor > Fix For: v0.5.0 > > > After Ldap integration the login successfully returns to home with the > username near the user icon. > But when provided empty entries it takes and on submission reports username > or password is incorrect. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1071) Login form takes empty entries
[ https://issues.apache.org/jira/browse/EAGLE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296297#comment-16296297 ] ASF GitHub Bot commented on EAGLE-1071: --- Github user haoch commented on a diff in the pull request: https://github.com/apache/eagle/pull/972#discussion_r157673368 --- Diff: eagle-server/src/main/webapp/app/dev/public/js/ctrls/authCtrl.js --- @@ -26,6 +26,14 @@ $scope.password = ''; $scope.login = function () { + if (!$scope.username || !$scope.password) --- End diff -- @zombieJ could you please have a look about the changes? > Login form takes empty entries > --- > > Key: EAGLE-1071 > URL: https://issues.apache.org/jira/browse/EAGLE-1071 > Project: Eagle > Issue Type: Bug > Components: Core::Eagle Server >Reporter: VSJTech >Priority: Minor > Fix For: v0.5.0 > > > After Ldap integration the login successfully returns to home with the > username near the user icon. > But when provided empty entries it takes and on submission reports username > or password is incorrect. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError
[ https://issues.apache.org/jira/browse/EAGLE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295508#comment-16295508 ] ASF GitHub Bot commented on EAGLE-968: -- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/941 @rushikesavareddy , can u pls rebase this from master, i think that will resolve the issue of having other non-relevant commits, pls also take care of code formatting. > using Email Notification Feature throws IncompatibleClassChangeError > > > Key: EAGLE-968 > URL: https://issues.apache.org/jira/browse/EAGLE-968 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Jayesh >Assignee: Jayesh > Fix For: v0.6.0 > > > {code} > 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator > Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to > @gmail.com,@gmail.com, due > to:java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:1.8.0_102] > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > ~[?:1.8.0_102] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92) > [stormjar.jar:?] > at > org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846) > [storm-core-1.0.3.jar:1.0.3] > at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) > [storm-core-1.0.3.jar:1.0.3] > at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?] > at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102] > Caused by: java.lang.IncompatibleClassChangeError: Implementing class > at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_102] > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > ~[?:1.8.0_102] > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > ~[?:1.8.0_102] > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > ~[?:1.8.0_102] > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) ~[?:1.8.0_102] > at java.security.AccessController.doPrivileged(Native Method) > ~[?:1.8.0_102] > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_102] > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_102] > at > org.apache.velocity.runtime.log.Log4JLogChute.initAppender(Log4JLogChute.java:118) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.Log4JLogChute.init(Log4JLogChute.java:85) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:157) > ~[stormjar.jar:?] > at >
[jira] [Commented] (EAGLE-1071) Login form takes empty entries
[ https://issues.apache.org/jira/browse/EAGLE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295504#comment-16295504 ] ASF GitHub Bot commented on EAGLE-1071: --- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/972 pls update the PR as per the format, pls refer other closed PRs. - update description - add [EAGLE-*] in title Thanks > Login form takes empty entries > --- > > Key: EAGLE-1071 > URL: https://issues.apache.org/jira/browse/EAGLE-1071 > Project: Eagle > Issue Type: Bug > Components: Core::Eagle Server >Reporter: VSJTech >Priority: Minor > Fix For: v0.5.0 > > > After Ldap integration the login successfully returns to home with the > username near the user icon. > But when provided empty entries it takes and on submission reports username > or password is incorrect. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1071) Login form takes empty entries
[ https://issues.apache.org/jira/browse/EAGLE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288762#comment-16288762 ] ASF GitHub Bot commented on EAGLE-1071: --- GitHub user VSJTech opened a pull request: https://github.com/apache/eagle/pull/972 EAGLE-EAGLE-1071 Login form takes empty entries Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/VSJTech/eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/972.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #972 commit f6fe0ce21c401fd7416bd1a2470ecb38c08066be Author: sukanagarajDate: 2017-12-13T05:58:09Z to check empty entries on the login form. validating the same > Login form takes empty entries > --- > > Key: EAGLE-1071 > URL: https://issues.apache.org/jira/browse/EAGLE-1071 > Project: Eagle > Issue Type: Bug > Components: Core::Eagle Server >Reporter: VSJTech >Priority: Minor > Fix For: v0.5.0 > > > After Ldap integration the login successfully returns to home with the > username near the user icon. > But when provided empty entries it takes and on submission reports username > or password is incorrect. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-973) update site document content
[ https://issues.apache.org/jira/browse/EAGLE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117939#comment-16117939 ] ASF GitHub Bot commented on EAGLE-973: -- GitHub user jhsenjaliya opened a pull request: https://github.com/apache/eagle/pull/968 [EAGLE-973] removing incubating from docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/jhsenjaliya/eagle EAGLE-973 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/968.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #968 commit a263e586fb649be0f3d5336002a360b041d0f05d Author: JayDate: 2017-08-08T06:55:24Z removing incubating from docs > update site document content > > > Key: EAGLE-973 > URL: https://issues.apache.org/jira/browse/EAGLE-973 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh >Assignee: Hao Chen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1059) fix a bug in policy prototype resource
[ https://issues.apache.org/jira/browse/EAGLE-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116022#comment-16116022 ] ASF GitHub Bot commented on EAGLE-1059: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/965 > fix a bug in policy prototype resource > -- > > Key: EAGLE-1059 > URL: https://issues.apache.org/jira/browse/EAGLE-1059 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > When a PolicyEntity(or policy prototype) is exported as a policy on a site, > the partitionSpec of the new policy is not updated, which results in a wrong > policy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1060) remove SNAPSHOT from version
[ https://issues.apache.org/jira/browse/EAGLE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115011#comment-16115011 ] ASF GitHub Bot commented on EAGLE-1060: --- Github user jhsenjaliya closed the pull request at: https://github.com/apache/eagle/pull/966 > remove SNAPSHOT from version > > > Key: EAGLE-1060 > URL: https://issues.apache.org/jira/browse/EAGLE-1060 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Jayesh >Assignee: Jayesh >Priority: Minor > Fix For: v0.5.0 > > > As pointed out by Hao > {quote} > The downloaded source package version is 0.5.0-SNAPSHOT, I think we should > change to 0.5.0 instead. > {quote} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1059) fix a bug in policy prototype resource
[ https://issues.apache.org/jira/browse/EAGLE-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114017#comment-16114017 ] ASF GitHub Bot commented on EAGLE-1059: --- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/965 OK > fix a bug in policy prototype resource > -- > > Key: EAGLE-1059 > URL: https://issues.apache.org/jira/browse/EAGLE-1059 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > When a PolicyEntity(or policy prototype) is exported as a policy on a site, > the partitionSpec of the new policy is not updated, which results in a wrong > policy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1059) fix a bug in policy prototype resource
[ https://issues.apache.org/jira/browse/EAGLE-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114011#comment-16114011 ] ASF GitHub Bot commented on EAGLE-1059: --- Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/965 @haoch No. I put this feature in v0.5.1 > fix a bug in policy prototype resource > -- > > Key: EAGLE-1059 > URL: https://issues.apache.org/jira/browse/EAGLE-1059 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > When a PolicyEntity(or policy prototype) is exported as a policy on a site, > the partitionSpec of the new policy is not updated, which results in a wrong > policy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1051) Check if a publisher can be deleted
[ https://issues.apache.org/jira/browse/EAGLE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113965#comment-16113965 ] ASF GitHub Bot commented on EAGLE-1051: --- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/959 @qingwen220 should it be included in `v0.5.0` release? > Check if a publisher can be deleted > > > Key: EAGLE-1051 > URL: https://issues.apache.org/jira/browse/EAGLE-1051 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > A publisher can be deleted only when there are no policies using it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError
[ https://issues.apache.org/jira/browse/EAGLE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093559#comment-16093559 ] ASF GitHub Bot commented on EAGLE-968: -- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/941 @rushikesavareddy , there are issues with this PR, please check, there should be only related changes here, this looks like is picking other changes as well that are not yours. > using Email Notification Feature throws IncompatibleClassChangeError > > > Key: EAGLE-968 > URL: https://issues.apache.org/jira/browse/EAGLE-968 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Jayesh >Assignee: Jayesh > Fix For: v0.6.0 > > > {code} > 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator > Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to > @gmail.com,@gmail.com, due > to:java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:1.8.0_102] > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > ~[?:1.8.0_102] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92) > [stormjar.jar:?] > at > org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846) > [storm-core-1.0.3.jar:1.0.3] > at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) > [storm-core-1.0.3.jar:1.0.3] > at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?] > at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102] > Caused by: java.lang.IncompatibleClassChangeError: Implementing class > at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_102] > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > ~[?:1.8.0_102] > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > ~[?:1.8.0_102] > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > ~[?:1.8.0_102] > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) ~[?:1.8.0_102] > at java.security.AccessController.doPrivileged(Native Method) > ~[?:1.8.0_102] > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_102] > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_102] > at > org.apache.velocity.runtime.log.Log4JLogChute.initAppender(Log4JLogChute.java:118) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.Log4JLogChute.init(Log4JLogChute.java:85) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:157) > ~[stormjar.jar:?] > at >
[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError
[ https://issues.apache.org/jira/browse/EAGLE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091206#comment-16091206 ] ASF GitHub Bot commented on EAGLE-968: -- Github user rushikesavareddy commented on the issue: https://github.com/apache/eagle/pull/941 @jhsenjaliya build was successful with checkStyleFlag enabled. Changed base/target branch to master. > using Email Notification Feature throws IncompatibleClassChangeError > > > Key: EAGLE-968 > URL: https://issues.apache.org/jira/browse/EAGLE-968 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Jayesh >Assignee: Jayesh > Fix For: v0.6.0 > > > {code} > 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator > Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to > @gmail.com,@gmail.com, due > to:java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > java.util.concurrent.ExecutionException: > java.lang.IncompatibleClassChangeError: Implementing class > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:1.8.0_102] > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > ~[?:1.8.0_102] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70) > [stormjar.jar:?] > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92) > [stormjar.jar:?] > at > org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73) > [storm-core-1.0.3.jar:1.0.3] > at > org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846) > [storm-core-1.0.3.jar:1.0.3] > at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) > [storm-core-1.0.3.jar:1.0.3] > at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?] > at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102] > Caused by: java.lang.IncompatibleClassChangeError: Implementing class > at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_102] > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > ~[?:1.8.0_102] > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > ~[?:1.8.0_102] > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > ~[?:1.8.0_102] > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) ~[?:1.8.0_102] > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) ~[?:1.8.0_102] > at java.security.AccessController.doPrivileged(Native Method) > ~[?:1.8.0_102] > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_102] > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > ~[?:1.8.0_102] > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_102] > at > org.apache.velocity.runtime.log.Log4JLogChute.initAppender(Log4JLogChute.java:118) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.Log4JLogChute.init(Log4JLogChute.java:85) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:157) > ~[stormjar.jar:?] > at > org.apache.velocity.runtime.log.LogManager.updateLog(LogManager.java:269) > ~[stormjar.jar:?] > at >
[jira] [Commented] (EAGLE-1046) Eagle supports policies import to a new site from a policy prototype
[ https://issues.apache.org/jira/browse/EAGLE-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085195#comment-16085195 ] ASF GitHub Bot commented on EAGLE-1046: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/963 > Eagle supports policies import to a new site from a policy prototype > > > Key: EAGLE-1046 > URL: https://issues.apache.org/jira/browse/EAGLE-1046 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang > > 0. policy prototype entity > {code} > String name > PolicyDefinition definition > List alertPublishmentIds > {code} > 1. load a list of policies to new site "sandbox" from policy prototypes by > {{POST /rest/policyProto/export/sandbox}} > {code} > [ { "definition": { > "name": "JobRpcThroughput", > "description": "Policy for > MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT", > "inputStreams": [ > "MAP_REDUCE_JOB_STREAM" > ], > "outputStreams": [ > "MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT" > ], > "siteId": null, > "definition": { > "type": "siddhi", > "value": "from MAP_REDUCE_JOB_STREAM[mapOpsPerSecond > > 1000 or reduceOpsPerSecond > 1000 or avgOpsPerMapTask > 50 or > avgOpsPerReduceTask > 50] select * insert into > MAP_REDUCE_JOB_STREAM_RPC_THROUGHPUT_OUT;", > "handlerClass": null, > "properties": {}, > "inputStreams": [], > "outputStreams": [] > }, > "stateDefinition": null, > "policyStatus": "DISABLED", > "alertDefinition": { > "templateType": "TEXT", > "subject": "$site job rpc", > "body": "$site job rpc throughput", > "severity": "WARNING", > "category": "JPM" > }, > "alertDeduplications": [ > { > "outputStreamId": > "MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT", > "dedupIntervalMin": "0", > "dedupFields": [] > } > ], > "partitionSpec": [ > { > "streamId": "MAP_REDUCE_JOB_STREAM_SANDBOX", > "type": "SHUFFLE", > "columns": [], > "sortSpec": null > } > ], > "dedicated": false, > "parallelismHint": 5, > "alertSeverity": "WARNING", > "alertCategory": "JPM" > }, > "alertPublishmentIds": [] > } > ] > {code} > 2. create a new policy prototype with an existing policy by {{ POST > /rest/policyProto/import}} > {code} > { "definition": { > "name": "JobRpcThroughput", > "description": "Policy for > MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT", > "inputStreams": [ > "MAP_REDUCE_JOB_STREAM_SANDBOX" > ], > "outputStreams": [ > "MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT" > ], > "siteId": "sandbox", > "definition": { > "type": "siddhi", > "value": "from MAP_REDUCE_JOB_STREAM_SANDBOX[mapOpsPerSecond > > 1000 or reduceOpsPerSecond > 1000 or avgOpsPerMapTask > 50 or > avgOpsPerReduceTask > 50] select * insert into > MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT;", > "handlerClass": null, > "properties": {}, > "inputStreams": [], > "outputStreams": [] > }, > "stateDefinition": null, > "policyStatus": "DISABLED", > "alertDefinition": { > "templateType": "TEXT", > "subject": "$site job rpc", > "body": "$site job rpc throughput", > "severity": "WARNING", > "category": "JPM" > }, > "alertDeduplications": [ > { > "outputStreamId": > "MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT", > "dedupIntervalMin": "0", > "dedupFields": [] > } > ], > "partitionSpec": [ > { > "streamId": "MAP_REDUCE_JOB_STREAM_SANDBOX", > "type": "SHUFFLE", > "columns": [], > "sortSpec": null > } > ], > "dedicated": false, >
[jira] [Commented] (EAGLE-740) Fix eagle-query checkstyle warnings
[ https://issues.apache.org/jira/browse/EAGLE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084811#comment-16084811 ] ASF GitHub Bot commented on EAGLE-740: -- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/647 I spent lot of time in rebasing this, but eventually it got very confusing since there are lot of files ( ~1500) to be rebased, which i did (jhsenjaliya:EAGLE-740-rebased) but there are multiple layers of rebase needs to be done, and i afraid i cant pick the right candidate wherever there are conflicts. so I am leaving this aside for 0.5 release, and we can get to this afterwards. this is important and we should take this change eventually. Thanks > Fix eagle-query checkstyle warnings > --- > > Key: EAGLE-740 > URL: https://issues.apache.org/jira/browse/EAGLE-740 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: luokun >Assignee: luokun > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Fix checkstyle problems on eagle-query -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-360) Kafka Java Producer with kerberos
[ https://issues.apache.org/jira/browse/EAGLE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084484#comment-16084484 ] ASF GitHub Bot commented on EAGLE-360: -- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/256 @haoch, @DadanielZ , I dont see these code changes in master or branch-0.5, were you expecting this to be merged ? > Kafka Java Producer with kerberos > - > > Key: EAGLE-360 > URL: https://issues.apache.org/jira/browse/EAGLE-360 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0 >Reporter: Hao Chen >Assignee: DanielZhou > Fix For: v0.6.0 > > > *log4j.properties* > {code} > log4j.appender.KAFKA_HDFS_AUDIT.SecurityProtocol=PLAINTEXTSASL > log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Conf=/etc/krb5.conf > log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthLoginConfig=/etc/kafka/kafka_jaas.conf > log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthUseSubjectCredsOnly=false > log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Debug=true > {code} > *kafka_jaas.conf* > {code} > KafkaClient { > com.sun.security.auth.module.Krb5LoginModule required > doNotPrompt=true > useTicketCache=true > principal="ctad...@eagle.incubator.apache.org" > useKeyTab=true > serviceName="kafka" > keyTab="/etc/security/keytabs/ctadmin.keytab" > client=true; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1046) Eagle supports policies import to a new site from a policy prototype
[ https://issues.apache.org/jira/browse/EAGLE-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081590#comment-16081590 ] ASF GitHub Bot commented on EAGLE-1046: --- GitHub user zombieJ opened a pull request: https://github.com/apache/eagle/pull/963 Eagle-1046 Eagle supports policies import to a new site from a policy prototype https://issues.apache.org/jira/browse/EAGLE-1046 add prototype management page support policy create with proto You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle EAGLE-1046 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/963.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #963 commit 1dcf294fc6066a1626c2782dd3621e4b84ca43d4 Author: zombieJDate: 2017-07-10T06:57:32Z fix admin check logic commit 1b8134d1c1dc6ebc892866a15d499c35dbdb49d7 Author: zombieJ Date: 2017-07-10T08:08:20Z add post prototype > Eagle supports policies import to a new site from a policy prototype > > > Key: EAGLE-1046 > URL: https://issues.apache.org/jira/browse/EAGLE-1046 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang > > 0. policy prototype entity > {code} > String name > PolicyDefinition definition > List alertPublishmentIds > {code} > 1. load a list of policies to new site "sandbox" from policy prototypes by > {{POST /rest/policyProto/export/sandbox}} > {code} > [ { "definition": { > "name": "JobRpcThroughput", > "description": "Policy for > MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT", > "inputStreams": [ > "MAP_REDUCE_JOB_STREAM" > ], > "outputStreams": [ > "MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT" > ], > "siteId": null, > "definition": { > "type": "siddhi", > "value": "from MAP_REDUCE_JOB_STREAM[mapOpsPerSecond > > 1000 or reduceOpsPerSecond > 1000 or avgOpsPerMapTask > 50 or > avgOpsPerReduceTask > 50] select * insert into > MAP_REDUCE_JOB_STREAM_RPC_THROUGHPUT_OUT;", > "handlerClass": null, > "properties": {}, > "inputStreams": [], > "outputStreams": [] > }, > "stateDefinition": null, > "policyStatus": "DISABLED", > "alertDefinition": { > "templateType": "TEXT", > "subject": "$site job rpc", > "body": "$site job rpc throughput", > "severity": "WARNING", > "category": "JPM" > }, > "alertDeduplications": [ > { > "outputStreamId": > "MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT", > "dedupIntervalMin": "0", > "dedupFields": [] > } > ], > "partitionSpec": [ > { > "streamId": "MAP_REDUCE_JOB_STREAM_SANDBOX", > "type": "SHUFFLE", > "columns": [], > "sortSpec": null > } > ], > "dedicated": false, > "parallelismHint": 5, > "alertSeverity": "WARNING", > "alertCategory": "JPM" > }, > "alertPublishmentIds": [] > } > ] > {code} > 2. create a new policy prototype with an existing policy by {{ POST > /rest/policyProto/import}} > {code} > { "definition": { > "name": "JobRpcThroughput", > "description": "Policy for > MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT", > "inputStreams": [ > "MAP_REDUCE_JOB_STREAM_SANDBOX" > ], > "outputStreams": [ > "MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT" > ], > "siteId": "sandbox", > "definition": { > "type": "siddhi", > "value": "from MAP_REDUCE_JOB_STREAM_SANDBOX[mapOpsPerSecond > > 1000 or reduceOpsPerSecond > 1000 or avgOpsPerMapTask > 50 or > avgOpsPerReduceTask > 50] select * insert into > MAP_REDUCE_JOB_STREAM_SANDBOX_RPC_THROUGHPUT_OUT;", > "handlerClass": null, > "properties": {}, >
[jira] [Commented] (EAGLE-1055) Improve policy prototype apis
[ https://issues.apache.org/jira/browse/EAGLE-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1607#comment-1607 ] ASF GitHub Bot commented on EAGLE-1055: --- Github user zombieJ commented on the issue: https://github.com/apache/eagle/pull/958 Greate. Let's merge into master > Improve policy prototype apis > -- > > Key: EAGLE-1055 > URL: https://issues.apache.org/jira/browse/EAGLE-1055 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > 1. create a policy prototype from a policy > {code} > API: /rest/policyProto/create?needPolicyCreated=true > Payload: PolicyEntity (policy + alertPublishmentIds) > {code} > 2. create a policy prototype by policy name > {code} > API: /rest/policyProto/create/\{policyId\} > {code} > 3. create policies for site from a list of policy protoypes > {code} > API: /rest/policyProto/export/\{site\} > Payload: List > {code} > 4. create policies for site from a list of prototypes > {code} > API: /rest/policyProto/exportByName/\{site\} > Payload: List > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1045) remove scala-tools.release repo as it causes build issue and not useful now
[ https://issues.apache.org/jira/browse/EAGLE-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067418#comment-16067418 ] ASF GitHub Bot commented on EAGLE-1045: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/951 > remove scala-tools.release repo as it causes build issue and not useful now > --- > > Key: EAGLE-1045 > URL: https://issues.apache.org/jira/browse/EAGLE-1045 > Project: Eagle > Issue Type: Improvement > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: v0.5.0 > > > When I download latest eagle and build with the following exception, please > advise how to solve this issue > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) > on project eagle-data-process: Error resolving project artifact: Could not > transfer artifact hiccup:hiccup:pom:0.3.6 from/to scale-tools.release > (http://scala-tools.org/repo-releases): > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target for project > hiccup:hiccup:jar:0.3.6 -> [Help 1] > When I remove repository “scala-tools.release” from pom.xml, the build can > pass. > In my local box, http://scala-tools.org/repo-releases is redirected to > https://blog.goodstuff.im/repo-releases. Seems something is wrong with this > repo -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1056) Fix a link bug in the email template
[ https://issues.apache.org/jira/browse/EAGLE-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064244#comment-16064244 ] ASF GitHub Bot commented on EAGLE-1056: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/960 > Fix a link bug in the email template > > > Key: EAGLE-1056 > URL: https://issues.apache.org/jira/browse/EAGLE-1056 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0, v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > "View Alert Details" cannot be opened. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1051) Check if a publisher can be deleted
[ https://issues.apache.org/jira/browse/EAGLE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057299#comment-16057299 ] ASF GitHub Bot commented on EAGLE-1051: --- GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/959 EAGLE-1051: update removePolicy https://issues.apache.org/jira/browse/EAGLE-1051 There is no need to do this check. As eagle has a table `policy_publishment` which has defined the relationship between policies and publishments. {code} CREATE TABLE IF NOT EXISTS policy_publishment ( policyId VARCHAR(50), publishmentName VARCHAR(50), PRIMARY KEY(policyId, publishmentName), CONSTRAINT `policy_id_fk` FOREIGN KEY (`policyId`) REFERENCES `policy_definition` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `publishment_id_fk` FOREIGN KEY (`publishmentName`) REFERENCES `publishment` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ); {code} You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/eagle EAGLE-1051 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/959.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #959 commit 118228d83fba85b467c73b30f5f1dc3dac7f2514 Author: Zhao, QingwenDate: 2017-06-20T12:58:06Z update removePolicy > Check if a publisher can be deleted > > > Key: EAGLE-1051 > URL: https://issues.apache.org/jira/browse/EAGLE-1051 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > A publisher can be deleted only when there are no policies using it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1055) Improve policy prototype apis
[ https://issues.apache.org/jira/browse/EAGLE-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057290#comment-16057290 ] ASF GitHub Bot commented on EAGLE-1055: --- GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/958 EAGLE-1055: update policy proto APIs https://issues.apache.org/jira/browse/EAGLE-1055 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/eagle EAGLE-1055 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/958.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #958 commit b86f00841319b57f44b0c052022f764217354347 Author: Zhao, QingwenDate: 2017-06-21T09:52:57Z update policy proto apis > Improve policy prototype apis > -- > > Key: EAGLE-1055 > URL: https://issues.apache.org/jira/browse/EAGLE-1055 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > 1. create a policy prototype from a policy > {code} > API: /rest/policyProto/create?needPolicyCreated=true > Payload: PolicyEntity (policy + alertPublishmentIds) > {code} > 2. create a policy prototype by policy name > {code} > API: /rest/policyProto/create/\{policyId\} > {code} > 3. create policies for site from a list of policy protoypes > {code} > API: /rest/policyProto/export/\{site\} > Payload: List > {code} > 4. create policies for site from a list of prototypes > {code} > API: /rest/policyProto/exportByName/\{site\} > Payload: List > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1053) Support typeahead in Eagle UI
[ https://issues.apache.org/jira/browse/EAGLE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057008#comment-16057008 ] ASF GitHub Bot commented on EAGLE-1053: --- Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/957 LGTM > Support typeahead in Eagle UI > - > > Key: EAGLE-1053 > URL: https://issues.apache.org/jira/browse/EAGLE-1053 > Project: Eagle > Issue Type: New Feature >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang > Fix For: v0.6.0 > > > Support typeahead in Eagle UI -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1053) Support typeahead in Eagle UI
[ https://issues.apache.org/jira/browse/EAGLE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056983#comment-16056983 ] ASF GitHub Bot commented on EAGLE-1053: --- GitHub user zombieJ opened a pull request: https://github.com/apache/eagle/pull/957 EAGLE-1053 Support typeahead in Eagle UI https://issues.apache.org/jira/browse/EAGLE-1053 Support typeahead in Eagle UI (metric preview page) You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle EAGLE-1053 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/957.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #957 commit 864bac956ca69d7677804870c5ed3eae2007f9ca Author: zombieJDate: 2017-06-21T03:44:45Z support metrics typeahead > Support typeahead in Eagle UI > - > > Key: EAGLE-1053 > URL: https://issues.apache.org/jira/browse/EAGLE-1053 > Project: Eagle > Issue Type: New Feature >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang > Fix For: v0.6.0 > > > Support typeahead in Eagle UI -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1054) Publisher delete don't close the dialog
[ https://issues.apache.org/jira/browse/EAGLE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056889#comment-16056889 ] ASF GitHub Bot commented on EAGLE-1054: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/956 > Publisher delete don't close the dialog > --- > > Key: EAGLE-1054 > URL: https://issues.apache.org/jira/browse/EAGLE-1054 > Project: Eagle > Issue Type: Bug >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > When user delete the publisher. The dialog not closed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1048) Delete an alert publisher on Eagle UI
[ https://issues.apache.org/jira/browse/EAGLE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055467#comment-16055467 ] ASF GitHub Bot commented on EAGLE-1048: --- Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/955 LGTM > Delete an alert publisher on Eagle UI > - > > Key: EAGLE-1048 > URL: https://issues.apache.org/jira/browse/EAGLE-1048 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang >Priority: Minor > > Administer can delete an alert publisher on Eagle UI > Request: DELETE /publishments/\{name\} > Response: > {code} > OpResult { > public int code = 200; // 200 = SUCCESS > public String message = ""; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1044) Support policy Import using a policy prototype
[ https://issues.apache.org/jira/browse/EAGLE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055374#comment-16055374 ] ASF GitHub Bot commented on EAGLE-1044: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/952 > Support policy Import using a policy prototype > -- > > Key: EAGLE-1044 > URL: https://issues.apache.org/jira/browse/EAGLE-1044 > Project: Eagle > Issue Type: New Feature >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Critical > > * add a new entity PolicyEntity in the metadata database > * provides RESTful APIs to query/delete/update a policy template > * easy to onboard policies on a new site -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1044) Support policy Import using a policy prototype
[ https://issues.apache.org/jira/browse/EAGLE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055371#comment-16055371 ] ASF GitHub Bot commented on EAGLE-1044: --- Github user anyway1021 commented on the issue: https://github.com/apache/eagle/pull/952 LGTM > Support policy Import using a policy prototype > -- > > Key: EAGLE-1044 > URL: https://issues.apache.org/jira/browse/EAGLE-1044 > Project: Eagle > Issue Type: New Feature >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Critical > > * add a new entity PolicyEntity in the metadata database > * provides RESTful APIs to query/delete/update a policy template > * easy to onboard policies on a new site -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1047) View all alert publishers on Eagle UI
[ https://issues.apache.org/jira/browse/EAGLE-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055372#comment-16055372 ] ASF GitHub Bot commented on EAGLE-1047: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/954 > View all alert publishers on Eagle UI > - > > Key: EAGLE-1047 > URL: https://issues.apache.org/jira/browse/EAGLE-1047 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang > > Users can view all the publisher configurations -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1047) View all alert publishers on Eagle UI
[ https://issues.apache.org/jira/browse/EAGLE-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055363#comment-16055363 ] ASF GitHub Bot commented on EAGLE-1047: --- Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/954 LGTM > View all alert publishers on Eagle UI > - > > Key: EAGLE-1047 > URL: https://issues.apache.org/jira/browse/EAGLE-1047 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang > > Users can view all the publisher configurations -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1049) Support metric filter in the metric preview page
[ https://issues.apache.org/jira/browse/EAGLE-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055362#comment-16055362 ] ASF GitHub Bot commented on EAGLE-1049: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/953 > Support metric filter in the metric preview page > - > > Key: EAGLE-1049 > URL: https://issues.apache.org/jira/browse/EAGLE-1049 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang >Priority: Minor > > Support metric filter in the metric preview page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1049) Support metric filter in the metric preview page
[ https://issues.apache.org/jira/browse/EAGLE-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055358#comment-16055358 ] ASF GitHub Bot commented on EAGLE-1049: --- Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/953 LGTM > Support metric filter in the metric preview page > - > > Key: EAGLE-1049 > URL: https://issues.apache.org/jira/browse/EAGLE-1049 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang >Priority: Minor > > Support metric filter in the metric preview page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1047) View all alert publishers on Eagle UI
[ https://issues.apache.org/jira/browse/EAGLE-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055352#comment-16055352 ] ASF GitHub Bot commented on EAGLE-1047: --- GitHub user zombieJ opened a pull request: https://github.com/apache/eagle/pull/954 EAGLE-1047 View all alert publishers on Eagle UI https://issues.apache.org/jira/browse/EAGLE-1047 Users can view all the publisher configurations You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle EAGLE-1047 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/954.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #954 commit 5e1c693f4ad2c73efd00455a8343850d872ec056 Author: zombieJDate: 2017-06-20T08:31:17Z add publisher list > View all alert publishers on Eagle UI > - > > Key: EAGLE-1047 > URL: https://issues.apache.org/jira/browse/EAGLE-1047 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.6.0 >Reporter: Zhao, Qingwen >Assignee: Jilin, Jiang > > Users can view all the publisher configurations -- This message was sent by Atlassian JIRA (v6.4.14#64029)