[jira] [Created] (EAGLE-465) Hive security monitoring refactor

[wujinhu (JIRA)]

wujinhu created EAGLE-465:
-

 Summary: Hive security monitoring refactor
 Key: EAGLE-465
 URL: https://issues.apache.org/jira/browse/EAGLE-465
 Project: Eagle
  Issue Type: Improvement
Reporter: wujinhu
Assignee: wujinhu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-135) Run Eagle in Spark Streaming

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420611#comment-15420611
 ] 

ASF GitHub Bot commented on EAGLE-135:
--

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/213
  
Branch-0.4 already released. And we have major change in v0.5. Looks this 
PR deprecated to me. Can we abandon and close this one? @yonzhang @haoch 


> Run Eagle in Spark Streaming
> 
>
> Key: EAGLE-135
> URL: https://issues.apache.org/jira/browse/EAGLE-135
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhaokun Qin
>Assignee: Zhaokun Qin
>Priority: Minor
>  Labels: new
>
> Eagle can run in Storm for now, to achieve Cross-platform feature, Eagle must 
> run in other streaming process platforms. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle issue #213: EAGLE-135 Run Eagle on Spark Streaming

[RalphSu]

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/213
  
Branch-0.4 already released. And we have major change in v0.5. Looks this 
PR deprecated to me. Can we abandon and close this one? @yonzhang @haoch 


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #322: [EAGLE-435] make coordiantor schedule ope...

[garrettlish]

Github user garrettlish closed the pull request at:

https://github.com/apache/incubator-eagle/pull/322


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-411) Refactor hbase related unit test cases with mockito and mini-hbase

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420606#comment-15420606
 ] 

ASF GitHub Bot commented on EAGLE-411:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/345
  
Thanks for the contribution, could you please make sure the changes could 
make other test cases using `EmbeddedHbase ` able to pass?


> Refactor hbase related unit test cases with mockito and mini-hbase
> --
>
> Key: EAGLE-411
> URL: https://issues.apache.org/jira/browse/EAGLE-411
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0, v0.4.0
>Reporter: Hao Chen
>Assignee: Chang chen
>  Labels: unit-test
> Fix For: v0.5.0
>
>
> Current implementation is really not stable which cause unit test like 
> TestHBaseLogReader2 unable to pass in meanful time, we need a better version.
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-embed/eagle-embed-hbase/src/main/java/org/apache/eagle/service/hbase/EmbeddedHbase.java
> http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle issue #345: EAGLE-411 Refactor hbase related unit test cases...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/345
  
Thanks for the contribution, could you please make sure the changes could 
make other test cases using `EmbeddedHbase ` able to pass?


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #343: clean eagle-data-process

[yonzhang]

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/343


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-411) Refactor hbase related unit test cases with mockito and mini-hbase

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420592#comment-15420592
 ] 

ASF GitHub Bot commented on EAGLE-411:
--

Github user chitin closed the pull request at:

https://github.com/apache/incubator-eagle/pull/345


> Refactor hbase related unit test cases with mockito and mini-hbase
> --
>
> Key: EAGLE-411
> URL: https://issues.apache.org/jira/browse/EAGLE-411
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0, v0.4.0
>Reporter: Hao Chen
>Assignee: Chang chen
>  Labels: unit-test
> Fix For: v0.5.0
>
>
> Current implementation is really not stable which cause unit test like 
> TestHBaseLogReader2 unable to pass in meanful time, we need a better version.
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-embed/eagle-embed-hbase/src/main/java/org/apache/eagle/service/hbase/EmbeddedHbase.java
> http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #345: EAGLE-411 Refactor hbase related unit tes...

[chitin]

Github user chitin closed the pull request at:

https://github.com/apache/incubator-eagle/pull/345


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-411) Refactor hbase related unit test cases with mockito and mini-hbase

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420587#comment-15420587
 ] 

ASF GitHub Bot commented on EAGLE-411:
--

GitHub user chitin opened a pull request:

https://github.com/apache/incubator-eagle/pull/345

EAGLE-411 Refactor hbase related unit test cases with mockito and min…

- Delete "zookeeper.znode.parent" and "hbase.master.ipc.address" in 
HbaseTestingUtility configuration.
- Support the Hbase UT which based the class to pass in meanful time

https://issues.apache.org/jira/browse/EAGLE-411

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chitin/incubator-eagle hbasetest-EAGLE411

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/345.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 #345


commit 7ba676a117c03c39d0bd1db759574a53a07eb06e
Author: chitin 
Date:   2016-08-15T03:31:42Z

EAGLE-411 Refactor hbase related unit test cases with mockito and mini-hbase
-Delete "zookeeper.znode.parent" and "hbase.master.ipc.address" in 
HbaseTestingUtility configuration.
-Support the Hbase UT which based the class to pass in meanful time

https://issues.apache.org/jira/browse/EAGLE-411




> Refactor hbase related unit test cases with mockito and mini-hbase
> --
>
> Key: EAGLE-411
> URL: https://issues.apache.org/jira/browse/EAGLE-411
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0, v0.4.0
>Reporter: Hao Chen
>Assignee: Chang chen
>  Labels: unit-test
> Fix For: v0.5.0
>
>
> Current implementation is really not stable which cause unit test like 
> TestHBaseLogReader2 unable to pass in meanful time, we need a better version.
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-embed/eagle-embed-hbase/src/main/java/org/apache/eagle/service/hbase/EmbeddedHbase.java
> http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #345: EAGLE-411 Refactor hbase related unit tes...

[chitin]

GitHub user chitin opened a pull request:

https://github.com/apache/incubator-eagle/pull/345

EAGLE-411 Refactor hbase related unit test cases with mockito and min…

- Delete "zookeeper.znode.parent" and "hbase.master.ipc.address" in 
HbaseTestingUtility configuration.
- Support the Hbase UT which based the class to pass in meanful time

https://issues.apache.org/jira/browse/EAGLE-411

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chitin/incubator-eagle hbasetest-EAGLE411

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/345.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 #345


commit 7ba676a117c03c39d0bd1db759574a53a07eb06e
Author: chitin 
Date:   2016-08-15T03:31:42Z

EAGLE-411 Refactor hbase related unit test cases with mockito and mini-hbase
-Delete "zookeeper.znode.parent" and "hbase.master.ipc.address" in 
HbaseTestingUtility configuration.
-Support the Hbase UT which based the class to pass in meanful time

https://issues.apache.org/jira/browse/EAGLE-411




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-464) StateCheck: multiple stage of definition in single policy

[Su Ralph (JIRA)]

Su Ralph created EAGLE-464:
--

 Summary: StateCheck: multiple stage of definition in single policy
 Key: EAGLE-464
 URL: https://issues.apache.org/jira/browse/EAGLE-464
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.5.0
Reporter: Su Ralph
Assignee: Su Ralph
 Fix For: v0.5.0


The requirement of alert state and transition comes from two real customer 
needs.
Alert de-duplication
"IMO, eagle should do state checks for all services. Eagle should not alert in 
the first attempt itself. Instead it should change the state to SOFT for 2 
tries and then if it is the same state, change the state to HARD and then send 
the alert." - Aroop
Currently, eagle's alert engine(and also that of UMP) use a simple 
deduplication spec of time based redundancy check(dedupIntervalMin of 
Publishment). This deduplication is not flexible to reflect the need of alerts. 
There are common requests like to hold a alert/policy state (basically a alert 
state is policy state on given partition value, more in latter), and trigger 
alert when the state changed. This state change manner could be 
> Same alert trigger again in M time interval
> N alerts in given M time interval.
NOTE: on here, in this de-duplication mode, there is no required change of the 
policy itself.
Alert policy define on transition
One example of the missingblock policy we met(only alert when missingblock 
number changes). There is more general case with minor difference, given a 
metric (or a field of a given stream), define value range, where each range 
indicate different state. Etc. for perfmon.latency.avg.perpool, define value 
range state as
metric
value range
state
alert trigger
perfmon.latency.avg.perpool.5min3000 - UnlimitedFATAL   always 
(every 5min until FATAL fixed or alert muted explictly)
1000 - 3000 CRITICALon dual transition
100 - 1000  WARNon dual transition
10 - 50 NORMAL  on worse transition
0-10GOODon worse transition
Then the alert should be trigger during the state changed expect for FATAL.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-421) JMX Metric APP use new application framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420583#comment-15420583
 ] 

ASF GitHub Bot commented on EAGLE-421:
--

GitHub user RalphSu opened a pull request:

https://github.com/apache/incubator-eagle/pull/344

EAGLE-421: JMX Metric APP use new application framework

Remove the topology code since JMX app could be done in new alert engine 
directly.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/RalphSu/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/344.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 #344


commit 1517c132658408952e790e27565496b9587da06b
Author: Ralph, Su 
Date:   2016-08-15T03:28:56Z

EAGLE-421: JMX Metric APP use new application framework

Remove the topology code since JMX app could be done in new alert engine 
directly.




> JMX Metric APP use new application framework
> 
>
> Key: EAGLE-421
> URL: https://issues.apache.org/jira/browse/EAGLE-421
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #344: EAGLE-421: JMX Metric APP use new applica...

[RalphSu]

GitHub user RalphSu opened a pull request:

https://github.com/apache/incubator-eagle/pull/344

EAGLE-421: JMX Metric APP use new application framework

Remove the topology code since JMX app could be done in new alert engine 
directly.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/RalphSu/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/344.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 #344


commit 1517c132658408952e790e27565496b9587da06b
Author: Ralph, Su 
Date:   2016-08-15T03:28:56Z

EAGLE-421: JMX Metric APP use new application framework

Remove the topology code since JMX app could be done in new alert engine 
directly.




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Could you grant me the access to upload eagle's artifacts to maven repository?

[John D. Ament]

Michael,

Your best bet is to ping infra.  If email doesn't work, hopping on to
hipchat with them may work.
http://www.apache.org/dev/infra-contact

John

On Sun, Aug 14, 2016 at 10:15 PM Michael Wu  wrote:

> Hi Jake,
>
> Could you please help on this case? There are some required dependencies
> blocked. Thanks.
>
> Michael
>
> On Thu, Aug 11, 2016 at 11:20 AM, Michael Wu  wrote:
>
> > Hi Jake,
> >
> > Tickets created:
> > https://issues.apache.org/jira/browse/INFRA-12409
> > https://issues.apache.org/jira/browse/INFRA-12410
> >
> > Thanks for helping it out.
> >
> > Michael
> >
> >
> > On Tue, Aug 9, 2016 at 12:00 AM, Jake Farrell 
> wrote:
> >
> >> Your user will have to get added to nexus, can you please put in an
> infra
> >> ticket for this
> >>
> >> -Jake
> >>
> >> On Sun, Aug 7, 2016 at 11:35 PM, Michael Wu  wrote:
> >>
> >> > Hi there,
> >> >
> >> > My apache account is "mw".
> >> >
> >> > I was trying to use
> >> >
> >> > $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_PASSPHR
> >> ASE}
> >> > deploy
> >> >
> >> > to upload eagle's jars to https://repository.apache.org/
> >> > service/local/staging/deploy/maven2, but it always returned 400 error,
> >> as
> >> > below fragment:
> >> > 
> >> > [ERROR] Failed to execute goal org.apache.maven.plugins:
> >> > maven-deploy-plugin:2.8.1:deploy (default-deploy) on project
> >> eagle-parent:
> >> > Failed to deploy artifacts: Could not transfer artifact
> >> > org.apache.eagle:eagle-parent:pom:0.4.0-incubating from/to
> >> > apache.releases.https (https://repository.apache.
> >> > org/service/local/staging/
> >> > deploy/maven2): Failed to transfer file:
> https://repository.apache.org/
> >> > service/local/staging/deploy/maven2/org/apache/eagle/eagle-
> >> > parent/0.4.0-incubating/eagle-parent-0.4.0-incubating.pom. Return code
> >> is:
> >> > 400, ReasonPhrase: Bad Request. -> [Help 1]
> >> > 
> >> >
> >> > Could you instruct me, whether it's caused by the lack of access to
> the
> >> > repository and could anyone help grant me the access? Thanks.
> >> >
> >> > Michael
> >> >
> >>
> >
> >
>

Re: Could you grant me the access to upload eagle's artifacts to maven repository?

[Michael Wu]

Hi Jake,

Could you please help on this case? There are some required dependencies
blocked. Thanks.

Michael

On Thu, Aug 11, 2016 at 11:20 AM, Michael Wu  wrote:

> Hi Jake,
>
> Tickets created:
> https://issues.apache.org/jira/browse/INFRA-12409
> https://issues.apache.org/jira/browse/INFRA-12410
>
> Thanks for helping it out.
>
> Michael
>
>
> On Tue, Aug 9, 2016 at 12:00 AM, Jake Farrell  wrote:
>
>> Your user will have to get added to nexus, can you please put in an infra
>> ticket for this
>>
>> -Jake
>>
>> On Sun, Aug 7, 2016 at 11:35 PM, Michael Wu  wrote:
>>
>> > Hi there,
>> >
>> > My apache account is "mw".
>> >
>> > I was trying to use
>> >
>> > $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_PASSPHR
>> ASE}
>> > deploy
>> >
>> > to upload eagle's jars to https://repository.apache.org/
>> > service/local/staging/deploy/maven2, but it always returned 400 error,
>> as
>> > below fragment:
>> > 
>> > [ERROR] Failed to execute goal org.apache.maven.plugins:
>> > maven-deploy-plugin:2.8.1:deploy (default-deploy) on project
>> eagle-parent:
>> > Failed to deploy artifacts: Could not transfer artifact
>> > org.apache.eagle:eagle-parent:pom:0.4.0-incubating from/to
>> > apache.releases.https (https://repository.apache.
>> > org/service/local/staging/
>> > deploy/maven2): Failed to transfer file: https://repository.apache.org/
>> > service/local/staging/deploy/maven2/org/apache/eagle/eagle-
>> > parent/0.4.0-incubating/eagle-parent-0.4.0-incubating.pom. Return code
>> is:
>> > 400, ReasonPhrase: Bad Request. -> [Help 1]
>> > 
>> >
>> > Could you instruct me, whether it's caused by the lack of access to the
>> > repository and could anyone help grant me the access? Thanks.
>> >
>> > Michael
>> >
>>
>
>

[GitHub] incubator-eagle pull request #343: clean eagle-data-process

[yonzhang]

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/343

clean eagle-data-process

clean unused classes in favor of new app framework

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/343.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 #343


commit e58d3b71749454bb6aa8e908931f4900fb9ef23c
Author: yonzhang 
Date:   2016-08-14T07:17:17Z

clean up eagle-policy-base

commit d5a1827109ba12d2e682917f7b452250ddb88eeb
Author: yonzhang 
Date:   2016-08-14T23:53:08Z

clean eagle-data-process




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-463) One App type may be run as multiple instances in one site

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-463:
--

 Summary: One App type may be run as multiple instances in one site
 Key: EAGLE-463
 URL: https://issues.apache.org/jira/browse/EAGLE-463
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Today in one site, one app type can be run only as one instance. In some 
scenarios, one application code can be run with multiple instances, for example 
to deal with different topics.

One typical example is JMX metric application can be for namenode, datanode , 
resource manager etc. They are all the same type of applications, i.e. code 
logic with different configurations for example topic for data sources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #342: fix build issue because of PR missing fil...

[yonzhang]

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/342


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-449) clean inner process alert engine code

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420236#comment-15420236
 ] 

ASF GitHub Bot commented on EAGLE-449:
--

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/341


> clean inner process alert engine code
> -
>
> Key: EAGLE-449
> URL: https://issues.apache.org/jira/browse/EAGLE-449
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> alert engine now is separated into a standalone storm topology, it is not 
> necessary to keep inner process alert engine



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-449) clean inner process alert engine code

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420234#comment-15420234
 ] 

ASF GitHub Bot commented on EAGLE-449:
--

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/341

clean inner process alert engine code

https://issues.apache.org/jira/browse/EAGLE-449

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/341.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 #341


commit 3d8974ea5f759a59f5361e2252a0c9ee37b7f8c8
Author: yonzhang 
Date:   2016-08-13T18:10:23Z

fix HdfsUserCommandReassembler which uses old data process api

commit 50b35b91f785f9983adeb36a279e7f98b227f256
Author: yonzhang 
Date:   2016-08-13T21:15:47Z

clean eagle example and data process

commit 0bae77072234deb7a19f413093f4b08ae70fef6a
Author: yonzhang 
Date:   2016-08-13T21:43:44Z

start clean eagle-stream-pipeline

commit 6ff8428527fabbce675344e84b210816e0ab3ae2
Author: yonzhang 
Date:   2016-08-13T21:50:40Z

clean eagle-stream-pipelin

commit a618aecf51288120e5794563f23bcbfc2195ccf7
Author: yonzhang 
Date:   2016-08-13T22:09:04Z

clean eagle-stream-application-manager

commit fdfd3e62413520ea8c7e77d3e715c7b036c46ff5
Author: yonzhang 
Date:   2016-08-13T22:17:43Z

clean application stream manager

commit 479dea9d4d7373f66b1783bde1950ed2c1addc97
Author: yonzhang 
Date:   2016-08-13T22:43:35Z

clean eagle-stream-process-api

commit 4c211bda5dbb9ce9475a040ac0d02c9bde99b679
Author: yonzhang 
Date:   2016-08-13T22:56:10Z

clean eagle-stream-process-api

commit 0871882f4303b7ecf166987f60c7243d0b1fe99f
Author: yonzhang 
Date:   2016-08-13T23:24:21Z

clean eagle-alert-process

commit d78505018a1155dc852d08650336398591cc5a66
Author: yonzhang 
Date:   2016-08-13T23:53:23Z

clean eagle-policy-base

commit 797c88028331859f1640e7b5b8e12e0961e82673
Author: yonzhang 
Date:   2016-08-14T00:11:52Z

clean eagle-alert-base

commit c60f8e6a93bddc3106f34aa1d2f18fc0403c2a4c
Author: yonzhang 
Date:   2016-08-14T06:13:03Z

clean eagle-policy-base

commit 354cd536321c9bc0406d18e237072974f729df11
Author: yonzhang 
Date:   2016-08-14T06:22:07Z

clean java mapper




> clean inner process alert engine code
> -
>
> Key: EAGLE-449
> URL: https://issues.apache.org/jira/browse/EAGLE-449
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> alert engine now is separated into a standalone storm topology, it is not 
> necessary to keep inner process alert engine



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)