[jira] [Updated] (EAGLE-581) Generate a build number when building the project.

2016-09-29 Thread Huizhi Lu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-581: Description: Use case: we need to know what version(latest commit revision) of source code we are using for

[jira] [Created] (EAGLE-581) Generate a build number when building the project.

2016-09-29 Thread Huizhi Lu (JIRA)
Huizhi Lu created EAGLE-581: --- Summary: Generate a build number when building the project. Key: EAGLE-581 URL: https://issues.apache.org/jira/browse/EAGLE-581 Project: Eagle Issue Type: New Feature

[jira] [Commented] (EAGLE-522) Implement HOURLY_RULE for Absence Alert.

2016-09-29 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15534256#comment-15534256 ] ASF GitHub Bot commented on EAGLE-522: -- Github user pkuwm commented on the issue:

[GitHub] incubator-eagle issue #426: [EAGLE-522] Implement HOURLY_RULE for Absence Al...

2016-09-29 Thread pkuwm
Github user pkuwm commented on the issue: https://github.com/apache/incubator-eagle/pull/426 Updated description. Merged with the newest commits. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

[jira] [Updated] (EAGLE-522) Implement HOURLY_RULE for Absence Alert.

2016-09-29 Thread Huizhi Lu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-522: Description: Absence alert HOURLY_RULE is another use case for customers' needs. We need to schedule jobs to

[jira] [Updated] (EAGLE-522) Implement HOURLY_RULE for Absence Alert.

2016-09-29 Thread Huizhi Lu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-522: Description: Absence alert HOURLY_RULE is another use case for customers' needs. We need to schedule jobs to

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #146

2016-09-29 Thread Apache Jenkins Server
The Apache Jenkins build system has built incubator-eagle-main (build #146) Status: Still Failing Check console output at https://builds.apache.org/job/incubator-eagle-main/146/ to view the results. Test Report is at: Test Result

[GitHub] incubator-eagle pull request #467: fix spoutSpecs load met invalid FieldName...

2016-09-29 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/467 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] incubator-eagle issue #467: fix spoutSpecs load met invalid FieldName(Dot) e...

2016-09-29 Thread RalphSu
Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/467 This is for https://issues.apache.org/jira/browse/EAGLE-580. Please update the title according to eagle community convention. --- If your project is set up for it, you can reply to

[jira] [Updated] (EAGLE-580) MongodbMetadata: kafka have dot in topic name cause spec store failed

2016-09-29 Thread Su Ralph (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Ralph updated EAGLE-580: --- Description: It's possible that user have DOT in topic names. In this case, mongodb metadata store of

[jira] [Commented] (EAGLE-580) MongodbMetadata: kafka have dot in topic name cause spec store failed

2016-09-29 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15533390#comment-15533390 ] ASF GitHub Bot commented on EAGLE-580: -- Github user RalphSu commented on the issue:

[jira] [Created] (EAGLE-580) MongodbMetadata: kafka have dot in topic name cause spec store failed

2016-09-29 Thread Su Ralph (JIRA)
Su Ralph created EAGLE-580: -- Summary: MongodbMetadata: kafka have dot in topic name cause spec store failed Key: EAGLE-580 URL: https://issues.apache.org/jira/browse/EAGLE-580 Project: Eagle Issue

[jira] [Commented] (EAGLE-579) Cloned stream alert event missed stream name

2016-09-29 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15533375#comment-15533375 ] ASF GitHub Bot commented on EAGLE-579: -- Github user asfgit closed the pull request at:

[GitHub] incubator-eagle pull request #467: fix spoutSpecs load met invalid FieldName...

2016-09-29 Thread mizeng
GitHub user mizeng opened a pull request: https://github.com/apache/incubator-eagle/pull/467 fix spoutSpecs load met invalid FieldName(Dot) exception Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make

[jira] [Commented] (EAGLE-579) Cloned stream alert event missed stream name

2016-09-29 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532732#comment-15532732 ] ASF GitHub Bot commented on EAGLE-579: -- GitHub user garrettlish opened a pull request:

[GitHub] incubator-eagle pull request #466: EAGLE-579: Cloned stream alert event miss...

2016-09-29 Thread garrettlish
GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/466 EAGLE-579: Cloned stream alert event missed stream name We are trying to clone stream alert event if there is a state transition (we need to update last state dedup count and first

[jira] [Created] (EAGLE-579) Cloned stream alert event missed stream name

2016-09-29 Thread Garrett Li (JIRA)
Garrett Li created EAGLE-579: Summary: Cloned stream alert event missed stream name Key: EAGLE-579 URL: https://issues.apache.org/jira/browse/EAGLE-579 Project: Eagle Issue Type: Bug

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #145

2016-09-29 Thread Apache Jenkins Server
The Apache Jenkins build system has built incubator-eagle-main (build #145) Status: Still Failing Check console output at https://builds.apache.org/job/incubator-eagle-main/145/ to view the results. Test Report is at: Test Result