Re: Can I build Eagle with Java 1.8?

Hi Kieth, Sorry for the version typo... I meant 0.4.x and 0.3.x. -Huizhi On Thu, Oct 13, 2016 at 1:05 PM, Huizhi Lu <ihuizhi...@gmail.com> wrote: > Hi Kieth, > > Eagle 4.0.x and 3.x don't support Java 1.8. > > The master branch supports Java 1.8. But it has not yet been

Re: Can I build Eagle with Java 1.8?

Hi Kieth, Eagle 4.0.x and 3.x don't support Java 1.8. The master branch supports Java 1.8. But it has not yet been released. Please use Eagle-4.x and Java 1.7 Best, Huizhi On Thu, Oct 13, 2016 at 1:00 PM, Keith Wiley wrote: > I see that the requirements indicate Java

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

[ 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

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

[ 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

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

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] [Updated] (EAGLE-522) Implement HOURLY_RULE for Absence Alert.

[ 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

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

[ 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

Re: EAGLE-517

<jhsonl...@gmail.com> wrote: > Hi Huizhi, > > is there a jira ticket for web UI development, or is there any planning > document ? > > Thanks > Jayesh > > On Fri, Sep 2, 2016 at 2:11 AM, Huizhi Lu <ihuizhi...@gmail.com> wrote: > > > Hi Jayesh, > &

[jira] [Comment Edited] (EAGLE-486) upgrade storm and kafka to a version which is consistent with HDP sandbox 2.4 and CDH 5.X

[ https://issues.apache.org/jira/browse/EAGLE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491733#comment-15491733 ] Huizhi Lu edited comment on EAGLE-486 at 9/14/16 11:25 PM: --- I am looking

[jira] [Commented] (EAGLE-486) upgrade storm and kafka to a version which is consistent with HDP sandbox 2.4 and CDH 5.X

[ https://issues.apache.org/jira/browse/EAGLE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491733#comment-15491733 ] Huizhi Lu commented on EAGLE-486: - I am looking into this. Solution: create 2 versions of modules for storm

Re: how to read stream from kafka

Hi, This example should help you. It only works for the current releases 0.3.x and 0.4.0. https://cwiki.apache.org/confluence/display/EAG/Monitor+Cassandra+audit+log On Mon, Sep 12, 2016 at 9:01 PM, Huizhi Lu <ihuizhi...@gmail.com> wrote: > Hi, > > This example should help you

Re: how to read stream from kafka

Hi, This example should help you. It only works for the current releases 0.3.x and 0.4.0. On Mon, Sep 12, 2016 at 1:54 AM, wrote: > > > Hi,I’m a newer to eagle. > > I want to set a stream from kafka, how should I configure it? Is there any > examples? Thanks a lot >

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

Huizhi Lu created EAGLE-522: --- Summary: Implement HOURLY_RULE for Absence Alert. Key: EAGLE-522 URL: https://issues.apache.org/jira/browse/EAGLE-522 Project: Eagle Issue Type: Improvement

Re: EAGLE-517

> Thanks for explaining. > Jayesh > > > On Fri, Sep 2, 2016 at 12:30 AM, Huizhi Lu <ihuizhi...@gmail.com> wrote: > > > Jayesh, > > > > The development guide in Intellij is not updated since current develop > > branch has replaced eagle-webservice wit

[jira] [Comment Edited] (EAGLE-517) develop branch is actually broken with missing dependencies

[ https://issues.apache.org/jira/browse/EAGLE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457823#comment-15457823 ] Huizhi Lu edited comment on EAGLE-517 at 9/2/16 7:46 AM: - Current develop branch

[jira] [Resolved] (EAGLE-511) Fix NullPointerException for spark history job

[ https://issues.apache.org/jira/browse/EAGLE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu resolved EAGLE-511. - Resolution: Fixed > Fix NullPointerException for spark history

[jira] [Resolved] (EAGLE-502) Always retry to parse spark history job when failure happens.

[ https://issues.apache.org/jira/browse/EAGLE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu resolved EAGLE-502. - Resolution: Fixed > Always retry to parse spark history job when failure happ

[jira] [Closed] (EAGLE-511) Fix NullPointerException for spark history job

[ https://issues.apache.org/jira/browse/EAGLE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-511. --- > Fix NullPointerException for spark history

[jira] [Closed] (EAGLE-502) Always retry to parse spark history job when failure happens.

[ https://issues.apache.org/jira/browse/EAGLE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-502. --- > Always retry to parse spark history job when failure happ

[jira] [Resolved] (EAGLE-521) Remove envContextConfig.env in SparkRunningJobAppConfig for SparkRunningJobApp.

[ https://issues.apache.org/jira/browse/EAGLE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu resolved EAGLE-521. - Resolution: Fixed > Remove envContextConfig.env in SparkRunningJobAppConfig for > SparkRunning

[jira] [Closed] (EAGLE-521) Remove envContextConfig.env in SparkRunningJobAppConfig for SparkRunningJobApp.

[ https://issues.apache.org/jira/browse/EAGLE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-521. --- > Remove envContextConfig.env in SparkRunningJobAppConfig for > SparkRunning

[jira] [Updated] (EAGLE-508) Fix NullPointerException when zookeeper is trying to shutdown in ZookeeperEmbedded.

[ https://issues.apache.org/jira/browse/EAGLE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-508: Summary: Fix NullPointerException when zookeeper is trying to shutdown in ZookeeperEmbedded. (was: Jenkins

[jira] [Created] (EAGLE-511) Fix NullPointerException for spark history job

Huizhi Lu created EAGLE-511: --- Summary: Fix NullPointerException for spark history job Key: EAGLE-511 URL: https://issues.apache.org/jira/browse/EAGLE-511 Project: Eagle Issue Type: Bug Affects

[jira] [Closed] (EAGLE-507) Jenkins building failed on build #71

[ https://issues.apache.org/jira/browse/EAGLE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-507. --- Resolution: Duplicate > Jenkins building failed on build

[jira] [Created] (EAGLE-508) Jenkins building failed on build #71

Huizhi Lu created EAGLE-508: --- Summary: Jenkins building failed on build #71 Key: EAGLE-508 URL: https://issues.apache.org/jira/browse/EAGLE-508 Project: Eagle Issue Type: Bug Affects Versions

[jira] [Created] (EAGLE-507) Jenkins building failed on build #71

Huizhi Lu created EAGLE-507: --- Summary: Jenkins building failed on build #71 Key: EAGLE-507 URL: https://issues.apache.org/jira/browse/EAGLE-507 Project: Eagle Issue Type: Bug Affects Versions

[jira] [Closed] (EAGLE-504) Fix warnings for getting json values in eagle-jpm-spark-history

[ https://issues.apache.org/jira/browse/EAGLE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-504. --- > Fix warnings for getting json values in eagle-jpm-spark-hist

[jira] [Resolved] (EAGLE-504) Fix warnings for getting json values in eagle-jpm-spark-history

[ https://issues.apache.org/jira/browse/EAGLE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu resolved EAGLE-504. - Resolution: Fixed > Fix warnings for getting json values in eagle-jpm-spark-hist

[jira] [Closed] (EAGLE-495) Convert spark history job using application framework

[ https://issues.apache.org/jira/browse/EAGLE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-495. --- > Convert spark history job using application framew

[jira] [Updated] (EAGLE-504) Fix warnings for getting json values in eagle-jpm

[ https://issues.apache.org/jira/browse/EAGLE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-504: Description: In JSONUTIL Class, if the key does not exist, null pointer exceptions would be thrown

[jira] [Updated] (EAGLE-504) Fix warnings for getting json values in eagle-jpm-spark-history

[ https://issues.apache.org/jira/browse/EAGLE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-504: Summary: Fix warnings for getting json values in eagle-jpm-spark-history (was: Fix warnings for getting

[jira] [Created] (EAGLE-504) Fix warnings for getting json values in eagle-jpm

Huizhi Lu created EAGLE-504: --- Summary: Fix warnings for getting json values in eagle-jpm Key: EAGLE-504 URL: https://issues.apache.org/jira/browse/EAGLE-504 Project: Eagle Issue Type: Bug

[jira] [Updated] (EAGLE-504) Fix warnings for getting json values in eagle-jpm

[ https://issues.apache.org/jira/browse/EAGLE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-504: Affects Version/s: v0.5.0 Fix Version/s: v0.5.0 > Fix warnings for getting json values in eagle-

[jira] [Updated] (EAGLE-381) Get resource manager version and improve app attempt id fetcher for spark job feeder

[ https://issues.apache.org/jira/browse/EAGLE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-381: Description: About the attempt_id, assuming attempt_id starting from 1 may not be completely correct

[jira] [Updated] (EAGLE-381) Get resource manager version and improve app attempt id fetcher for spark job feeder

[ https://issues.apache.org/jira/browse/EAGLE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-381: Summary: Get resource manager version and improve app attempt id fetcher for spark job feeder (was: Improve

[jira] [Closed] (EAGLE-492) Fix negative total execution time and make some code optimization for spark history job.

[ https://issues.apache.org/jira/browse/EAGLE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-492. --- > Fix negative total execution time and make some code optimization for spark > histo

[jira] [Resolved] (EAGLE-492) Fix negative total execution time and make some code optimization for spark history job.

[ https://issues.apache.org/jira/browse/EAGLE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu resolved EAGLE-492. - Resolution: Fixed > Fix negative total execution time and make some code optimization for spark > h

[jira] [Closed] (EAGLE-499) Fix flushing entities for spark history job.

[ https://issues.apache.org/jira/browse/EAGLE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-499. --- > Fix flushing entities for spark history

[jira] [Created] (EAGLE-502) Always retry to parse spark history job when failure happens.

Huizhi Lu created EAGLE-502: --- Summary: Always retry to parse spark history job when failure happens. Key: EAGLE-502 URL: https://issues.apache.org/jira/browse/EAGLE-502 Project: Eagle Issue Type

[jira] [Created] (EAGLE-499) Fix flushing entities for spark history job.

Huizhi Lu created EAGLE-499: --- Summary: Fix flushing entities for spark history job. Key: EAGLE-499 URL: https://issues.apache.org/jira/browse/EAGLE-499 Project: Eagle Issue Type: Bug Affects

[jira] [Closed] (EAGLE-483) Test email alert publisher

[ https://issues.apache.org/jira/browse/EAGLE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-483. --- > Test email alert publisher > -- > > Key: EAGLE-483 >

[jira] [Resolved] (EAGLE-483) Test email alert publisher

[ https://issues.apache.org/jira/browse/EAGLE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu resolved EAGLE-483. - Resolution: Fixed > Test email alert publisher > -- > >

[jira] [Updated] (EAGLE-495) Convert spark history job using application framework

[ https://issues.apache.org/jira/browse/EAGLE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-495: Remaining Estimate: 60h Original Estimate: 60h > Convert spark history job using application framew

[jira] [Created] (EAGLE-495) Convert spark history job using application framework

Huizhi Lu created EAGLE-495: --- Summary: Convert spark history job using application framework Key: EAGLE-495 URL: https://issues.apache.org/jira/browse/EAGLE-495 Project: Eagle Issue Type: Task

Re: metrics-core version problem

Hi, It looks like a Kafka/java version problem: Kafka in Eagle and CHD are not matched. 1) What version of Eagle are you using, 0.3.x, 0.4 or develop? 2) Eagle 0.3.x and 0.4 don't support Java 1.8. Can you give more environment details? On Tue, Aug 23, 2016 at 3:47 AM, 邱路平

[jira] [Updated] (EAGLE-492) Fix negative total execution time and make some code optimization for spark history job.

[ https://issues.apache.org/jira/browse/EAGLE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-492: Description: 1) negative total execution time It is because the app was killed or terminated unexpectedly

[jira] [Updated] (EAGLE-492) Fix negative total execution time and make some code optimization for spark history job.

[ https://issues.apache.org/jira/browse/EAGLE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-492: Affects Version/s: v0.5.0 Fix Version/s: v0.5.0 > Fix negative total execution time and make s

[jira] [Created] (EAGLE-492) Fix negative total execution time and make some code optimization for spark history job.

Huizhi Lu created EAGLE-492: --- Summary: Fix negative total execution time and make some code optimization for spark history job. Key: EAGLE-492 URL: https://issues.apache.org/jira/browse/EAGLE-492 Project

[jira] [Resolved] (EAGLE-347) Replace "v0.3.0" to "v0.3.1" in eagle-topology-init.sh

[ https://issues.apache.org/jira/browse/EAGLE-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu resolved EAGLE-347. - Resolution: Fixed > Replace "v0.3.0" to "v0.3.1" in

[jira] [Closed] (EAGLE-344) Fix broken alertDetailUrl and policyDetailUrl in alert emails.

[ https://issues.apache.org/jira/browse/EAGLE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-344. --- Resolution: Fixed > Fix broken alertDetailUrl and policyDetailUrl in alert ema

[jira] [Created] (EAGLE-483) Test email alert publisher

Huizhi Lu created EAGLE-483: --- Summary: Test email alert publisher Key: EAGLE-483 URL: https://issues.apache.org/jira/browse/EAGLE-483 Project: Eagle Issue Type: Test Affects Versions: v0.5.0

[jira] [Resolved] (EAGLE-475) Fix generic email publisher and publish emails for absence alert.

[ https://issues.apache.org/jira/browse/EAGLE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu resolved EAGLE-475. - Resolution: Fixed Resolved and merged. > Fix generic email publisher and publish emails for absence al

[jira] [Created] (EAGLE-475) Fix generic email publisher and publish emails for absence alert.

Huizhi Lu created EAGLE-475: --- Summary: Fix generic email publisher and publish emails for absence alert. Key: EAGLE-475 URL: https://issues.apache.org/jira/browse/EAGLE-475 Project: Eagle Issue

[jira] [Updated] (EAGLE-409) Automatically recognized eagle service url with http://

[ https://issues.apache.org/jira/browse/EAGLE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-409: Description: When setting eagle service to http://host.domain.com instead of host.domain.com, eagle can

[jira] [Created] (EAGLE-409) Automatically recognized eagle service url with http://

Huizhi Lu created EAGLE-409: --- Summary: Automatically recognized eagle service url with http:// Key: EAGLE-409 URL: https://issues.apache.org/jira/browse/EAGLE-409 Project: Eagle Issue Type

[jira] [Created] (EAGLE-381) Improve app attempt id fetcher for spark job feeder

Huizhi Lu created EAGLE-381: --- Summary: Improve app attempt id fetcher for spark job feeder Key: EAGLE-381 URL: https://issues.apache.org/jira/browse/EAGLE-381 Project: Eagle Issue Type: Bug

[jira] [Closed] (EAGLE-357) Building failed: at eagle-webservice app/public/feature/common/controller.js

[ https://issues.apache.org/jira/browse/EAGLE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-357. --- Resolution: Fixed Fix Version/s: (was: v0.4.0) v0.3.1 Fixed and merged

Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)

+1 (non-binding) * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X * Signature checked, md5, sha1 verified * Apache rat:check passed (mvn apache-rat:check) * Release matches tag. -Huizhi > On Jul 11, 2016, at 2:40 AM, Michael Wu wrote: > > Hi all, > >

[jira] [Created] (EAGLE-363) Read topologyName from application.conf for MR history job feeder.

Huizhi Lu created EAGLE-363: --- Summary: Read topologyName from application.conf for MR history job feeder. Key: EAGLE-363 URL: https://issues.apache.org/jira/browse/EAGLE-363 Project: Eagle Issue

[jira] [Updated] (EAGLE-357) Building failed: at eagle-webservice

[ https://issues.apache.org/jira/browse/EAGLE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-357: Summary: Building failed: at eagle-webservice (was: Building failed: ) > Building failed: at ea

[jira] [Updated] (EAGLE-357) Building failed: at eagle-webservice app/public/feature/common/controller.js

[ https://issues.apache.org/jira/browse/EAGLE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-357: Summary: Building failed: at eagle-webservice app/public/feature/common/controller.js (was: Building failed

Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 2)

+1 (non-binding) * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X * Signature checked, md5, sha1 verified * Apache rat:check passed * Release matches tag. Nice release! -Huizhi > On Jul 5, 2016, at 11:04 PM, Michael Wu wrote: > > Hi all, > > This is a

[jira] [Created] (EAGLE-357) Building failed:

Huizhi Lu created EAGLE-357: --- Summary: Building failed: Key: EAGLE-357 URL: https://issues.apache.org/jira/browse/EAGLE-357 Project: Eagle Issue Type: Bug Affects Versions: v0.4.0

[jira] [Closed] (EAGLE-303) Refactor message format in the email template.

[ https://issues.apache.org/jira/browse/EAGLE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-303. --- Resolution: Fixed > Refactor message format in the email templ

[jira] [Updated] (EAGLE-344) Fix broken alertDetailUrl and policyDetailUrl in alert emails.

[ https://issues.apache.org/jira/browse/EAGLE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-344: Summary: Fix broken alertDetailUrl and policyDetailUrl in alert emails. (was: Fix broken alertDetailUrl

[jira] [Created] (EAGLE-344) Fix broken alertDetailUrl and policyDetailUrl

Huizhi Lu created EAGLE-344: --- Summary: Fix broken alertDetailUrl and policyDetailUrl Key: EAGLE-344 URL: https://issues.apache.org/jira/browse/EAGLE-344 Project: Eagle Issue Type: Bug Affects

Re: Requirement for detailed document of eagle

Hi Qianqian, Here are some troubleshooting tips: 1) run the command: hdfs dfs -cat /tmp/private and use the following command to check kafka consumer if it is able to consume the message. Change the --zookeeper opts if needed. bin/kafka-console-consumer.sh --zookeeper localhost:2181 --topic

[jira] [Closed] (EAGLE-236) Change project version to "0.4.0-SNAPSHOT" since "v0.3.0" has been released.

[ https://issues.apache.org/jira/browse/EAGLE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-236. --- Resolution: Fixed Merged. > Change project version to "0.4.0-SNAPSHOT" since "v0.3.0&

[jira] [Closed] (EAGLE-297) Email with authentication can not be validated and sent out.

[ https://issues.apache.org/jira/browse/EAGLE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-297. --- Resolution: Fixed Merged. > Email with authentication can not be validated and sent

[jira] [Created] (EAGLE-303) Refactor message format in the email template.

Huizhi Lu created EAGLE-303: --- Summary: Refactor message format in the email template. Key: EAGLE-303 URL: https://issues.apache.org/jira/browse/EAGLE-303 Project: Eagle Issue Type: Improvement

[jira] [Commented] (EAGLE-236) Change project version to "0.4.0-SNAPSHOT" since "v0.3.0" has been released.

[ https://issues.apache.org/jira/browse/EAGLE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15279596#comment-15279596 ] Huizhi Lu commented on EAGLE-236: - No problem. > Change project version to "0.4.0-SNAPSHOT"

[jira] [Created] (EAGLE-294) If a policy metadata field is not set, null attributes can not be able to add into input stream for SiddhiCEP

Huizhi Lu created EAGLE-294: --- Summary: If a policy metadata field is not set, null attributes can not be able to add into input stream for SiddhiCEP Key: EAGLE-294 URL: https://issues.apache.org/jira/browse/EAGLE-294

[jira] [Updated] (EAGLE-287) Make EagleStore as the default notification method

[ https://issues.apache.org/jira/browse/EAGLE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-287: Description: Make EagleStore alerts as the default notification so that we can still get alerting

[jira] [Commented] (EAGLE-289) $elem["dataSource"] in alert email

[ https://issues.apache.org/jira/browse/EAGLE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268987#comment-15268987 ] Huizhi Lu commented on EAGLE-289: - Thanks for the tip, Qingwen! I'll merge your fix into master. > $e

[jira] [Updated] (EAGLE-287) Make EagleStore as the default notification method

[ https://issues.apache.org/jira/browse/EAGLE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-287: Description: Make EagleStore alerts as the default notification so that we can still get alerting

[jira] [Updated] (EAGLE-287) Make EagleStore as the default notification method

[ https://issues.apache.org/jira/browse/EAGLE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-287: Summary: Make EagleStore as the default notification method (was: Make EagleStore as the default

[jira] [Updated] (EAGLE-287) Make EagleStore as the default notification

[ https://issues.apache.org/jira/browse/EAGLE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-287: Summary: Make EagleStore as the default notification (was: Make dashboard alerts as the default

[jira] [Updated] (EAGLE-286) Failed to deserialize json

[ https://issues.apache.org/jira/browse/EAGLE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-286: Description: When Eagle detects one failed message such as invalid json, it may not ack the message back

Register to Dev Maillist

Hi, My name is Huizhi Lu. I am a developer with Apache Eagle Team and would like to join the mailing list. Can you please add me to the list? Thanks! Email address: ihuizhi.lu <http://ihuizhi.lu/>@gmail.com -Huizhi

[jira] [Commented] (EAGLE-98) Eagle Pipeline Scheduler

[ https://issues.apache.org/jira/browse/EAGLE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227322#comment-15227322 ] Huizhi Lu commented on EAGLE-98: Hello Guys! I am now open to accepting tickets :) > Eagle Pipel

[jira] [Commented] (EAGLE-181) HDFS topology alerts multiple time.

[ https://issues.apache.org/jira/browse/EAGLE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190559#comment-15190559 ] Huizhi Lu commented on EAGLE-181: - Not yet :) Two more weeks. > HDFS topology alerts multiple t

[jira] [Commented] (EAGLE-181) HDFS topology alerts multiple time.

[ https://issues.apache.org/jira/browse/EAGLE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189627#comment-15189627 ] Huizhi Lu commented on EAGLE-181: - I am following it! Hey, Guys! > HDFS topology alerts multiple t