[GitHub] incubator-eagle pull request #522: [EAGLE-632] clean up configuration for MR...

[wujinhu]

GitHub user wujinhu opened a pull request:

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

[EAGLE-632] clean up configuration for MR history feeder



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-632

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

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


commit ae37aba31d81c2ba5514aa3b8108b09595748c42
Author: wujinhu 
Date:   2016-10-18T03:34:30Z

clean up configuration for MR feeders

commit dc75dfb5a7bd8518421134b4b9aa9af26e88abbf
Author: wujinhu 
Date:   2016-10-18T07:18:52Z

clean up configuration for MR feeders




---
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-632) clean up configuration for MR history feeder

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-632:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-632] clean up configuration for MR history feeder



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-632

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

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


commit ae37aba31d81c2ba5514aa3b8108b09595748c42
Author: wujinhu 
Date:   2016-10-18T03:34:30Z

clean up configuration for MR feeders

commit dc75dfb5a7bd8518421134b4b9aa9af26e88abbf
Author: wujinhu 
Date:   2016-10-18T07:18:52Z

clean up configuration for MR feeders




> clean up configuration for MR history feeder
> 
>
> Key: EAGLE-632
> URL: https://issues.apache.org/jira/browse/EAGLE-632
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



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

[GitHub] incubator-eagle pull request #523: [CI] Integrate coveralls to track eagle c...

[haoch]

GitHub user haoch opened a pull request:

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

[CI] Integrate coveralls to track eagle code coverage

## CI Building Command

mvn clean test cobertura:cobertura coveralls:report 
-DrepoToken=$COVERALLS_EAGLE_TOKEN -Dmaven.javadoc.skip=true -P!ui

Check report at https://coveralls.io/github/apache/incubator-eagle


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

$ git pull https://github.com/haoch/incubator-eagle integrate_coveralls

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

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


commit ec07c09e874b8928b79f90fff7f0756911156765
Author: Hao Chen 
Date:   2016-10-18T05:44:53Z

Integrate with cobertura and coveralls

commit 224a93e5303e0fb0d136736f418d987b7d3b44a2
Author: Hao Chen 
Date:   2016-10-18T05:48:39Z

Add build and coverage badge

commit a9fb5cf82a02b1cd3a082735b829753a996e2e95
Author: Hao Chen 
Date:   2016-10-18T06:14:55Z

Disable EmbeddedHbaseTest

commit 153b599e03536d11f29a7bea19fba50f3eaeeb97
Author: Hao Chen 
Date:   2016-10-18T06:28:24Z

Add .gitattributes




---
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 issue #522: [EAGLE-632] clean up configuration for MR histor...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/522
  
LGTM


---
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-632) clean up configuration for MR history feeder

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-632:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/522
  
LGTM


> clean up configuration for MR history feeder
> 
>
> Key: EAGLE-632
> URL: https://issues.apache.org/jira/browse/EAGLE-632
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



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

[GitHub] incubator-eagle pull request #522: [EAGLE-632] clean up configuration for MR...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-632) clean up configuration for MR history feeder

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-632:
--

Github user asfgit closed the pull request at:

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


> clean up configuration for MR history feeder
> 
>
> Key: EAGLE-632
> URL: https://issues.apache.org/jira/browse/EAGLE-632
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



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

[jira] [Created] (EAGLE-633) applications read some configurations from eagle server

[wujinhu (JIRA)]

wujinhu created EAGLE-633:
-

 Summary: applications read some configurations from eagle server
 Key: EAGLE-633
 URL: https://issues.apache.org/jira/browse/EAGLE-633
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


application can read some configurations from eagle server like 
service/zookeeper so that user does not need read from configure file



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

[GitHub] incubator-eagle pull request #524: [UI] Improve integeration page

[haoch]

GitHub user haoch opened a pull request:

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

[UI] Improve integeration page



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/haoch/incubator-eagle ImproveIntegerationPage

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

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


commit 5153fca9c36f3854f858ab2a1503c20eb57d190a
Author: Hao Chen 
Date:   2016-10-17T13:01:43Z

Improve settings page

commit 867d15d9e053ee53d3e5441a7969c11879f191ad
Author: Hao Chen 
Date:   2016-10-17T15:27:15Z

Merge branch 'ImproveIntegerationPage' of 
https://github.com/haoch/incubator-eagle into ImproveIntegerationPage

commit 30ab9d5c490807edc09528d09e0613d9e395a487
Author: Hao Chen 
Date:   2016-10-17T15:28:13Z

Make ui-build.sh executable

commit 38b3d76fc6e2994259cee4298dcf9ac1030b7dff
Author: Hao Chen 
Date:   2016-10-18T03:51:49Z

Change Introduction to Summary

commit 485d0f633547a4099e8e58026a1e8f27041cddf8
Author: Hao Chen 
Date:   2016-10-18T08:30:33Z

Cleanup alert engine configuration descriptor




---
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] [Updated] (EAGLE-633) MR history feeder read some configurations from eagle server

[wujinhu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wujinhu updated EAGLE-633:
--
Summary: MR history feeder read some configurations from eagle server  
(was: applications read some configurations from eagle server)

> MR history feeder read some configurations from eagle server
> 
>
> Key: EAGLE-633
> URL: https://issues.apache.org/jira/browse/EAGLE-633
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> application can read some configurations from eagle server like 
> service/zookeeper so that user does not need read from configure file



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

[GitHub] incubator-eagle pull request #523: [CI] Integrate coveralls to track eagle c...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #525: [EAGLE-633] MR history feeder read some c...

[wujinhu]

GitHub user wujinhu opened a pull request:

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

[EAGLE-633] MR history feeder read some configurations from eagle server



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-633

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

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


commit f2e1c52c8adaf55db16370ab916c467b15cff394
Author: wujinhu 
Date:   2016-10-18T08:58:15Z

MR history feeder read some configurations from eagle server




---
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-633) MR history feeder read some configurations from eagle server

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-633:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-633] MR history feeder read some configurations from eagle server



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-633

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

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


commit f2e1c52c8adaf55db16370ab916c467b15cff394
Author: wujinhu 
Date:   2016-10-18T08:58:15Z

MR history feeder read some configurations from eagle server




> MR history feeder read some configurations from eagle server
> 
>
> Key: EAGLE-633
> URL: https://issues.apache.org/jira/browse/EAGLE-633
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> application can read some configurations from eagle server like 
> service/zookeeper so that user does not need read from configure file



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

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

[Apache Jenkins Server]

The Apache Jenkins build system has built incubator-eagle-main (build #206) 
Status: Failure Check console output at 
https://builds.apache.org/job/incubator-eagle-main/206/ to view the 
results. Test Report is at: Test Result

[jira] [Closed] (EAGLE-632) clean up configuration for MR history feeder

[wujinhu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wujinhu closed EAGLE-632.
-
Resolution: Resolved

> clean up configuration for MR history feeder
> 
>
> Key: EAGLE-632
> URL: https://issues.apache.org/jira/browse/EAGLE-632
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



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

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

[Apache Jenkins Server]

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

[GitHub] incubator-eagle pull request #526: [MINOR] Fix end of line conflict caused b...

[haoch]

GitHub user haoch opened a pull request:

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

[MINOR] Fix end of line conflict caused by .gitattributes



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/haoch/incubator-eagle FixEOL

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

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


commit 2479d32791dd1a424af7513279ba28543baf6af4
Author: wujinhu 
Date:   2016-10-18T09:20:37Z

[EAGLE-633] MR history feeder read some configurations from eagle server

Author: wujinhu 

Closes #525 from wujinhu/EAGLE-633.

commit a4cd8248f11226538fad217d265ac1a0b5bd8190
Author: Hao Chen 
Date:   2016-10-18T09:46:44Z

[MINOR] Fix CRLF to LF as default eol

commit b8d41cdc2cc8ee8e601ab3147d2339fe6e70dade
Author: Hao Chen 
Date:   2016-10-18T09:50:49Z

Merge conflict




---
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 #525: [EAGLE-633] MR history feeder read some c...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-633) MR history feeder read some configurations from eagle server

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-633:
--

Github user asfgit closed the pull request at:

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


> MR history feeder read some configurations from eagle server
> 
>
> Key: EAGLE-633
> URL: https://issues.apache.org/jira/browse/EAGLE-633
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> application can read some configurations from eagle server like 
> service/zookeeper so that user does not need read from configure file



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

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

[Apache Jenkins Server]

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

[jira] [Closed] (EAGLE-633) MR history feeder read some configurations from eagle server

[wujinhu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wujinhu closed EAGLE-633.
-
Resolution: Resolved

> MR history feeder read some configurations from eagle server
> 
>
> Key: EAGLE-633
> URL: https://issues.apache.org/jira/browse/EAGLE-633
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> application can read some configurations from eagle server like 
> service/zookeeper so that user does not need read from configure file



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

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

[Apache Jenkins Server]

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

[GitHub] incubator-eagle pull request #526: [MINOR] Fix end of line conflict caused b...

[haoch]

Github user haoch closed the pull request at:

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


---
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 #527: Minor: set task number of UnitTopologyRun...

[qingwen220]

GitHub user qingwen220 opened a pull request:

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

Minor: set task number of UnitTopologyRunner



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

$ git pull https://github.com/qingwen220/incubator-eagle quickFix

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

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


commit 22519845d21f44a87a20f6e5aad707b91a4c2e2d
Author: Zhao, Qingwen 
Date:   2016-10-18T11:30:20Z

set task number of UnitTopologyRunner




---
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 #524: [UI] Improve integeration page

[asfgit]

Github user asfgit closed the pull request at:

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


---
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.
---

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

[Apache Jenkins Server]

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

[jira] [Created] (EAGLE-634) clean up configuration for MR running feeder

[wujinhu (JIRA)]

wujinhu created EAGLE-634:
-

 Summary: clean up configuration for MR running feeder
 Key: EAGLE-634
 URL: https://issues.apache.org/jira/browse/EAGLE-634
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0






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

[jira] [Updated] (EAGLE-634) clean up configuration for MR running feeder

[wujinhu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wujinhu updated EAGLE-634:
--
Description: 
1. remove useless configure
2. add required field to application provider.xml
3. add description to application provider.xml

> clean up configuration for MR running feeder
> 
>
> Key: EAGLE-634
> URL: https://issues.apache.org/jira/browse/EAGLE-634
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



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

[EAGLE TEST FAILED] incubator-eagle-main failed in testing phase on build #211

[Apache Jenkins Server]

The Apache Jenkins build system has built incubator-eagle-main (build #211) 
Status: Unstable Check console output at 
https://builds.apache.org/job/incubator-eagle-main/211/ to view the 
results. Test Report is at: Test Result

[GitHub] incubator-eagle pull request #528: [EAGLE-563] migrate eagle-hadoop-queue to...

[anyway1021]

GitHub user anyway1021 opened a pull request:

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

[EAGLE-563] migrate eagle-hadoop-queue to use application framework

Migrate eagle-hadoop-queue to use application framework.

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

$ git pull https://github.com/anyway1021/incubator-eagle EAGLE-563

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

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


commit 5b90820bf4a75fbb29f24f5f21c64a78c4ff9757
Author: anyway1021 
Date:   2016-10-17T02:19:45Z

migrate eagle-hadoop-queue to use application framework




---
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-563) Refactor Hadoop queue feeder using application framework

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-563:
--

GitHub user anyway1021 opened a pull request:

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

[EAGLE-563] migrate eagle-hadoop-queue to use application framework

Migrate eagle-hadoop-queue to use application framework.

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

$ git pull https://github.com/anyway1021/incubator-eagle EAGLE-563

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

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


commit 5b90820bf4a75fbb29f24f5f21c64a78c4ff9757
Author: anyway1021 
Date:   2016-10-17T02:19:45Z

migrate eagle-hadoop-queue to use application framework




> Refactor Hadoop queue feeder using application framework
> 
>
> Key: EAGLE-563
> URL: https://issues.apache.org/jira/browse/EAGLE-563
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Michael Wu
>
> Currently hadoop queue feeder is developed as independent storm application. 
> In order to make sure hadoop queue feeder could be well managed by 
> application framework and service



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

[GitHub] incubator-eagle issue #528: [EAGLE-563] migrate eagle-hadoop-queue to use ap...

[qingwen220]

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/528
  
LGTM


---
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-563) Refactor Hadoop queue feeder using application framework

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-563:
--

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/528
  
LGTM


> Refactor Hadoop queue feeder using application framework
> 
>
> Key: EAGLE-563
> URL: https://issues.apache.org/jira/browse/EAGLE-563
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Michael Wu
>
> Currently hadoop queue feeder is developed as independent storm application. 
> In order to make sure hadoop queue feeder could be well managed by 
> application framework and service



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

[GitHub] incubator-eagle issue #527: Minor: set task number of UnitTopologyRunner

[wujinhu]

Github user wujinhu commented on the issue:

https://github.com/apache/incubator-eagle/pull/527
  
LGTM


---
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 #529: [EAGLE-635] Refactor policy parser and va...

[haoch]

GitHub user haoch opened a pull request:

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

[EAGLE-635] Refactor policy parser and validator for richer plan details 
and better performance

- Refactor policy parser and validator for richer plan details and better 
performance
- Decouple PolicyExecutionPlan and PolicyValidation

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

$ git pull https://github.com/haoch/incubator-eagle RefactorPolicyValidator

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

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






---
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-635) Refactor policy parser and validator for richer plan details and better performance

[Hao Chen (JIRA)]

Hao Chen created EAGLE-635:
--

 Summary: Refactor policy parser and validator for richer plan 
details and better performance
 Key: EAGLE-635
 URL: https://issues.apache.org/jira/browse/EAGLE-635
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


* Refactor policy parser and validator for richer plan details and better 
performance
* Decouple PolicyExecutionPlan and PolicyValidation



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

[jira] [Commented] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-635:
--

GitHub user haoch opened a pull request:

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

[EAGLE-635] Refactor policy parser and validator for richer plan details 
and better performance

- Refactor policy parser and validator for richer plan details and better 
performance
- Decouple PolicyExecutionPlan and PolicyValidation

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

$ git pull https://github.com/haoch/incubator-eagle RefactorPolicyValidator

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

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






> Refactor policy parser and validator for richer plan details and better 
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Refactor policy parser and validator for richer plan details and better 
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation



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

[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-635:
---
Issue Type: Improvement  (was: Bug)

> Refactor policy parser and validator for richer plan details and better 
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Refactor policy parser and validator for richer plan details and better 
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation



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

[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-635:
---
Description: 
h2. Changes

* Refactor policy parser and validator for richer plan details and better 
performance
* Decouple PolicyExecutionPlan and PolicyValidation

h2. API
* Parse API

{code}
POST /metadata/policies/parse 
Accept-Type: text

from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}

* Validation API
{code}
POST /metadata/policies/validate 
Accept-Type: application/json

{
   "name": "hdfsPolicy",
   "description": "hdfsPolicy",
   "inputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
   ],
   "outputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
   ],
   "definition": {
  "type": "siddhi",
  "value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 
min) select cmd, user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
   },
   "partitionSpec": [
  {
 "streamId": "hdfs_audit_log_enriched_stream",
 "type": "GROUPBY",
 "columns" : [
"cmd"
 ]
  }
   ],
   "parallelismHint": 2
}

{code}

  was:
## Changes

* Refactor policy parser and validator for richer plan details and better 
performance
* Decouple PolicyExecutionPlan and PolicyValidation

## API
* Parse API
{code}
POST /metadata/policies/parse 
Accept-Type: text

from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}

* Validation API
{code}
POST /metadata/policies/validate 
Accept-Type: application/json

{
   "name": "hdfsPolicy",
   "description": "hdfsPolicy",
   "inputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
   ],
   "outputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
   ],
   "definition": {
  "type": "siddhi",
  "value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 
min) select cmd, user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
   },
   "partitionSpec": [
  {
 "streamId": "hdfs_audit_log_enriched_stream",
 "type": "GROUPBY",
 "columns" : [
"cmd"
 ]
  }
   ],
   "parallelismHint": 2
}

{code}


> Refactor policy parser and validator for richer plan details and better 
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> h2. Changes
> * Refactor policy parser and validator for richer plan details and better 
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> h2. API
> * Parse API
> {code}
> POST /metadata/policies/parse 
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select 
> cmd, user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate 
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
>   "type": "siddhi",
>   "value": "from 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
> user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
>   {
>  "streamId": "hdfs_audit_log_enriched_stream",
>  "type": "GROUPBY",
>  "columns" : [
> "cmd"
>  ]
>   }
>],
>"parallelismHint": 2
> }
> {code}



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

[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-635:
---
Description: 
## Changes

* Refactor policy parser and validator for richer plan details and better 
performance
* Decouple PolicyExecutionPlan and PolicyValidation

## API
* Parse API
{code}
POST /metadata/policies/parse 
Accept-Type: text

from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}

* Validation API
{code}
POST /metadata/policies/validate 
Accept-Type: application/json

{
   "name": "hdfsPolicy",
   "description": "hdfsPolicy",
   "inputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
   ],
   "outputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
   ],
   "definition": {
  "type": "siddhi",
  "value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 
min) select cmd, user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
   },
   "partitionSpec": [
  {
 "streamId": "hdfs_audit_log_enriched_stream",
 "type": "GROUPBY",
 "columns" : [
"cmd"
 ]
  }
   ],
   "parallelismHint": 2
}

{code}

  was:
* Refactor policy parser and validator for richer plan details and better 
performance
* Decouple PolicyExecutionPlan and PolicyValidation


> Refactor policy parser and validator for richer plan details and better 
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> ## Changes
> * Refactor policy parser and validator for richer plan details and better 
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> ## API
> * Parse API
> {code}
> POST /metadata/policies/parse 
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select 
> cmd, user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate 
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
>   "type": "siddhi",
>   "value": "from 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
> user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
>   {
>  "streamId": "hdfs_audit_log_enriched_stream",
>  "type": "GROUPBY",
>  "columns" : [
> "cmd"
>  ]
>   }
>],
>"parallelismHint": 2
> }
> {code}



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

Re: [DISCUSS] restart Eagle graduate discussion

[Zhao Qingwen]

+1

Since last Oct, Eagle has grown a lot in all aspects described in Apache
Project Maturity Model. It also accepts 4+ new committers and multiple
other organizations also actively participate in the new feature
development.


Best Regards,
Qingwen Zhao | 赵晴雯




2016-10-18 11:53 GMT+08:00 Jilin :

> +1
>
> Eagle have a great process during this year. And it's also important to the
> Hadoop ecosphere.
> - Committer well follow the jira & PR process.
> - Release the stable version.
> - Keep updating the project.
>
> I think it's time for graduation.
>
> 2016-10-18 11:34 GMT+08:00 Hao Chen :
>
> > +1
> >
> > Very glad to hear that Eagle is infinitely closing to graduate at a
> > top-level project since entering incubator at Oct 26th, 2016.
> >
> > In the past one year, the eagle community has always keep learning,
> growing
> > and practicing apache way every where and every day:
> >
> >- Meritocracy
> >- Peer to Peer
> >- Consensus decision making
> >- Open, online communication
> >- Responsible oversight
> >
> > Until now (10/26/2015 ~ 10/18/2016), eagle community has grown very fast
> in
> > features, code quality, community, consensus building etc.
> >
> >- Reached a very high maturity level: https://cwiki.apache.org/
> >confluence/display/EAG/Eagle+Podling+Maturity+Assessment
> > > Podling+Maturity+Assessment>
> >- Added *4+* new committers and *20+* contributors from different
> >organizations around the world side
> >- Successfully released *2* major versions and some minor versions,
> >resolved *632+* jira tickets and *577+* pull requests.
> >- *5+* public originations (e.g. eBay, Paypal, Yihaodian, Dataguise,
> >etc.) are using or adopting eagle to monitor their hadoop clusters.
> >- Shared eagle and apache way in *10+* tech conferences in* 8+
> > *different
> >cities around the world (e.g. Hadoop Summit, Hadoop Stratus, QCon,
> etc.)
> >
> > - Hao
> >
> > On Tue, Oct 18, 2016 at 10:24 AM, Michael Wu  wrote:
> >
> > > +1
> > >
> > >  - 2 releases have been made and committers have summed lots of
> > experience
> > > of the releasing process.
> > >  - More and more contributions are received from the community.
> > >  - JIRA tickets are all with detailed descriptions.
> > >  - PRs follow a good way of collaboration.
> > >  - The project is being established in the industry.
> > >  - Responses are made timely to requesters.
> > >
> > >
> > > On Tue, Oct 18, 2016 at 8:04 AM, Liangfei.Su 
> > wrote:
> > >
> > > > +1
> > > >
> > > > Eagle Maturity Assessment clear listed and completed.
> > > > JIRA with clear comments.
> > > > PRs follow the convention that point to given JIRA by apache naming.
> > This
> > > > keeps clear commit history and friendly comments.
> > > > Very happy to see more contributors other than originators to join
> in.
> > > > Documentation, these are continuing improved to help community easier
> > to
> > > > involve in.
> > > >
> > > > Thanks,
> > > > Ralph
> > > >
> > > >
> > > > On Mon, Oct 17, 2016 at 8:16 PM, Jinhu Wu 
> > > wrote:
> > > >
> > > > > Vote +1.
> > > > >
> > > > > There are more and more contributors and they are making great
> > > > > contributions to Apache Eagle.
> > > > > Eagle codes are more stable and documents are more helpful to use
> > eagle
> > > > > system.
> > > > >
> > > > > Besides, Eagle team are working with other developers in other
> > > > corporations
> > > > > to discuss some features and optimizations to make eagle more
> > powerful.
> > > > >
> > > > > I am also happy to become an Eagle committer and hope Eagle will be
> > > > better.
> > > > >
> > > > > Thanks
> > > > > Jinhu
> > > > >
> > > > > On Fri, Oct 14, 2016 at 5:29 AM, Da Zhou 
> > > > wrote:
> > > > >
> > > > > > Vote +1.
> > > > > >  "Eagle Maturity Assessment" looks good to me. Great process has
> > been
> > > > > made
> > > > > > since last discussion:
> > > > > >
> > > > > > - Lots of new features have been introduced, now Apache Eagle has
> > > > become
> > > > > > more powerful and user-friendly.(eg,  Application Management
> > through
> > > > > Eagle
> > > > > > UI.)
> > > > > > - Also many fixes have been checked in, which makes Eagle more
> > stable
> > > > and
> > > > > > robust.
> > > > > > - Community is getting more active, we can tell this based on
> daily
> > > > > > discussion happened in the emails.
> > > > > > - Apache Eagle is getting more attention by different
> corporations
> > > and
> > > > > > organizations,  their cooperation has been reported online (eg,
> > Yahoo
> > > > > News)
> > > > > >
> > > > > > Regards,
> > > > > > Da
> > > > > >
> > > > > > On Wed, Oct 12, 2016 at 8:12 PM, Edward Zhang <
> > > yonzhang2...@apache.org
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Eagle Community,
> > > > > > >
> > > > > > > It's been more than 2 months and a lot have been improved since
> > we
> > > > last
> > > > > > > time discuss

[GitHub] incubator-eagle pull request #529: [EAGLE-635] Refactor policy parser and va...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #527: Minor: set task number of UnitTopologyRun...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-635) Refactor policy parser and validator for richer plan details and better performance

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-635:
--

Github user asfgit closed the pull request at:

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


> Refactor policy parser and validator for richer plan details and better 
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> h2. Changes
> * Refactor policy parser and validator for richer plan details and better 
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> h2. API
> * Parse API
> {code}
> POST /metadata/policies/parse 
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select 
> cmd, user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate 
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
>   "type": "siddhi",
>   "value": "from 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
> user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
>   {
>  "streamId": "hdfs_audit_log_enriched_stream",
>  "type": "GROUPBY",
>  "columns" : [
> "cmd"
>  ]
>   }
>],
>"parallelismHint": 2
> }
> {code}



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

[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-635:
---
Description: 
h2. Changes

* Refactor policy parser and validator for richer plan details and better 
performance
* Decouple PolicyExecutionPlan and PolicyValidation

h2. API
* Parse API

{code}
POST /metadata/policies/parse 
Accept-Type: text

from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}

* Validation API
{code}
POST /metadata/policies/validate 
Accept-Type: application/json

{
   "name": "hdfsPolicy",
   "description": "hdfsPolicy",
   "inputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
   ],
   "outputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
   ],
   "definition": {
  "type": "siddhi",
  "value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 
min) select cmd, user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
   },
   "partitionSpec": [
  {
 "streamId": "hdfs_audit_log_enriched_stream",
 "type": "GROUPBY",
 "columns" : [
"cmd"
 ]
  }
   ],
   "parallelismHint": 2
}

{code}

h2. Use Cases
* **parse**: So you could continuously call `parse` API aside during user keeps 
typing to verify the syntax and automatically generate input/output/partition , 
as it won't call back-end db, so will be very fast.
* **validate**: when user finishes defining policy, the api will validate the 
metadata end2end

  was:
h2. Changes

* Refactor policy parser and validator for richer plan details and better 
performance
* Decouple PolicyExecutionPlan and PolicyValidation

h2. API
* Parse API

{code}
POST /metadata/policies/parse 
Accept-Type: text

from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}

* Validation API
{code}
POST /metadata/policies/validate 
Accept-Type: application/json

{
   "name": "hdfsPolicy",
   "description": "hdfsPolicy",
   "inputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
   ],
   "outputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
   ],
   "definition": {
  "type": "siddhi",
  "value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 
min) select cmd, user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
   },
   "partitionSpec": [
  {
 "streamId": "hdfs_audit_log_enriched_stream",
 "type": "GROUPBY",
 "columns" : [
"cmd"
 ]
  }
   ],
   "parallelismHint": 2
}

{code}


> Refactor policy parser and validator for richer plan details and better 
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> h2. Changes
> * Refactor policy parser and validator for richer plan details and better 
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> h2. API
> * Parse API
> {code}
> POST /metadata/policies/parse 
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select 
> cmd, user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate 
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
>   "type": "siddhi",
>   "value": "from 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
> user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
>   {
>  "streamId": "hdfs_audit_log_enriched_stream",
>  "type": "GROUPBY",
>  "columns" : [
> "cmd"
>  ]
>   }
>],
>"parallelismHint": 2
> }
> {code}
> h2. Use Cases
> * **parse**: So you could continuously call `parse` API aside during user 
> keeps typing to verify the syntax and automatically generate 
> input/output/partition , as it won't call back-end db, so will be very fast.
> * **validate**: when user finishes defining policy, the api will validate the 
> metadata end2end

[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-635:
---
Description: 
h2. Changes

* Refactor policy parser and validator for richer plan details and better 
performance
* Decouple PolicyExecutionPlan and PolicyValidation

h2. API
* Parse API

{code}
POST /metadata/policies/parse 
Accept-Type: text

from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}

* Validation API
{code}
POST /metadata/policies/validate 
Accept-Type: application/json

{
   "name": "hdfsPolicy",
   "description": "hdfsPolicy",
   "inputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
   ],
   "outputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
   ],
   "definition": {
  "type": "siddhi",
  "value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 
min) select cmd, user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
   },
   "partitionSpec": [
  {
 "streamId": "hdfs_audit_log_enriched_stream",
 "type": "GROUPBY",
 "columns" : [
"cmd"
 ]
  }
   ],
   "parallelismHint": 2
}

{code}

h2. Use Cases
* *parse*: could continuously call `parse` API aside during user keeps typing 
to verify the syntax and automatically generate input/output/partition , as it 
won't call back-end db, so will be very fast.
* *validate*: when user finishes defining policy, the api will validate the 
metadata end2end

  was:
h2. Changes

* Refactor policy parser and validator for richer plan details and better 
performance
* Decouple PolicyExecutionPlan and PolicyValidation

h2. API
* Parse API

{code}
POST /metadata/policies/parse 
Accept-Type: text

from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}

* Validation API
{code}
POST /metadata/policies/validate 
Accept-Type: application/json

{
   "name": "hdfsPolicy",
   "description": "hdfsPolicy",
   "inputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
   ],
   "outputStreams": [
  "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
   ],
   "definition": {
  "type": "siddhi",
  "value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 
min) select cmd, user, count() as total_count group by cmd,user insert into 
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
   },
   "partitionSpec": [
  {
 "streamId": "hdfs_audit_log_enriched_stream",
 "type": "GROUPBY",
 "columns" : [
"cmd"
 ]
  }
   ],
   "parallelismHint": 2
}

{code}

h2. Use Cases
* **parse**: So you could continuously call `parse` API aside during user keeps 
typing to verify the syntax and automatically generate input/output/partition , 
as it won't call back-end db, so will be very fast.
* **validate**: when user finishes defining policy, the api will validate the 
metadata end2end


> Refactor policy parser and validator for richer plan details and better 
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> h2. Changes
> * Refactor policy parser and validator for richer plan details and better 
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> h2. API
> * Parse API
> {code}
> POST /metadata/policies/parse 
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select 
> cmd, user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate 
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
>   "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
>   "type": "siddhi",
>   "value": "from 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd, 
> user, count() as total_count group by cmd,user insert into 
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
>   {
>  "streamId": "hdfs_audit_log_enriched_stream",
>  "type": "GROUPBY",
>  "columns" : [
> "cmd"
>  ]
>   }
>],
>"parallelismHint": 2
> }
> {code}
> h2. Use Cases
> * *pars

[jira] [Closed] (EAGLE-592) Add a hdfs audit log parser which consumes message in Json format

[Zhao, Qingwen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhao, Qingwen closed EAGLE-592.
---
Resolution: Done

> Add a hdfs audit log parser which consumes message in Json format
> -
>
> Key: EAGLE-592
> URL: https://issues.apache.org/jira/browse/EAGLE-592
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> In Hdfs audit log application,  the default deserializer class configured in 
> Eagle is "storm.kafka.StringScheme", which only processes the raw log
> {code}
>  "dataSourceConfig": {
> ...
> "schemeCls" : "storm.kafka.StringScheme"
>   },
> {code}
> For some log collector agents, like filebeat (5.0), the output is in json 
> format. 
> {"xx": "abc", "yy": "aabbcc", "message": "audit log"}
> This ticket will create a class MessageJsonScheme which will extract 
> 'message' field from the message from Kafka



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

[jira] [Updated] (EAGLE-592) Add a hdfs audit log parser which consumes message in Json format

[Zhao, Qingwen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhao, Qingwen updated EAGLE-592:

Description: 
In Hdfs audit log application,  the default deserializer class configured in 
Eagle is "storm.kafka.StringScheme", which only processes the raw log

{code}
 "dataSourceConfig": {
...
"schemeCls" : "storm.kafka.StringScheme"
  },
{code}

For some log collector agents, like filebeat (5.0), the output is in json 
format. 

{"xx": "abc", "yy": "aabbcc", "message": "audit log"}

This ticket will create a class MessageJsonScheme which will extract 'message' 
field from the message from Kafka





  was:
For some log collector agents, like filebeat (5.0), the output is in json 
format. 

{"xx": "abc", "yy": "aabbcc", "message": "audit log"}

This ticket will create a class MessageJsonScheme which will extract 'message' 
field from the message from Kafka




> Add a hdfs audit log parser which consumes message in Json format
> -
>
> Key: EAGLE-592
> URL: https://issues.apache.org/jira/browse/EAGLE-592
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> In Hdfs audit log application,  the default deserializer class configured in 
> Eagle is "storm.kafka.StringScheme", which only processes the raw log
> {code}
>  "dataSourceConfig": {
> ...
> "schemeCls" : "storm.kafka.StringScheme"
>   },
> {code}
> For some log collector agents, like filebeat (5.0), the output is in json 
> format. 
> {"xx": "abc", "yy": "aabbcc", "message": "audit log"}
> This ticket will create a class MessageJsonScheme which will extract 
> 'message' field from the message from Kafka



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

[GitHub] incubator-eagle pull request #530: [EAGLE-634] clean up configuration for MR...

[wujinhu]

GitHub user wujinhu opened a pull request:

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

[EAGLE-634] clean up configuration for MR running feeder



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-634

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

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


commit 317b869935e84a37f0ee7e9f7bed9e6df64724de
Author: wujinhu 
Date:   2016-10-19T02:45:59Z

clean up configuration for MR running feeder




---
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-634) clean up configuration for MR running feeder

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-634:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-634] clean up configuration for MR running feeder



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-634

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

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


commit 317b869935e84a37f0ee7e9f7bed9e6df64724de
Author: wujinhu 
Date:   2016-10-19T02:45:59Z

clean up configuration for MR running feeder




> clean up configuration for MR running feeder
> 
>
> Key: EAGLE-634
> URL: https://issues.apache.org/jira/browse/EAGLE-634
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



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

[jira] [Resolved] (EAGLE-624) Installation Doc is not correctly shown in Installation Dialog

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen resolved EAGLE-624.

Resolution: Fixed

> Installation Doc is not correctly shown in Installation Dialog
> --
>
> Key: EAGLE-624
> URL: https://issues.apache.org/jira/browse/EAGLE-624
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: eagle-ui
> Fix For: v0.5.0
>
>
> h2. Improvements
> * Show dependencies apps number
> * Support XML child node tree as String in app docs
> * Cleanup eagle-server dependencies and output
> * Move business logic specific logics into dev profile
> * Rename header and remove pre fo installation content
> h2. Bugs
> * Fix siteName bug in ui
> * Installation Doc is not correctly shown in Installation Dialog



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

Re: [DISCUSS] restart Eagle graduate discussion

[Edward Zhang]

Thanks all for valuable feedback. We will work with our mentors to execute
the steps towards graduation. Cheers!

Thanks
Edward

On Tue, Oct 18, 2016 at 7:27 PM, Zhao Qingwen  wrote:

> +1
>
> Since last Oct, Eagle has grown a lot in all aspects described in Apache
> Project Maturity Model. It also accepts 4+ new committers and multiple
> other organizations also actively participate in the new feature
> development.
>
>
> Best Regards,
> Qingwen Zhao | 赵晴雯
>
>
>
>
> 2016-10-18 11:53 GMT+08:00 Jilin :
>
> > +1
> >
> > Eagle have a great process during this year. And it's also important to
> the
> > Hadoop ecosphere.
> > - Committer well follow the jira & PR process.
> > - Release the stable version.
> > - Keep updating the project.
> >
> > I think it's time for graduation.
> >
> > 2016-10-18 11:34 GMT+08:00 Hao Chen :
> >
> > > +1
> > >
> > > Very glad to hear that Eagle is infinitely closing to graduate at a
> > > top-level project since entering incubator at Oct 26th, 2016.
> > >
> > > In the past one year, the eagle community has always keep learning,
> > growing
> > > and practicing apache way every where and every day:
> > >
> > >- Meritocracy
> > >- Peer to Peer
> > >- Consensus decision making
> > >- Open, online communication
> > >- Responsible oversight
> > >
> > > Until now (10/26/2015 ~ 10/18/2016), eagle community has grown very
> fast
> > in
> > > features, code quality, community, consensus building etc.
> > >
> > >- Reached a very high maturity level: https://cwiki.apache.org/
> > >confluence/display/EAG/Eagle+Podling+Maturity+Assessment
> > > > > Podling+Maturity+Assessment>
> > >- Added *4+* new committers and *20+* contributors from different
> > >organizations around the world side
> > >- Successfully released *2* major versions and some minor versions,
> > >resolved *632+* jira tickets and *577+* pull requests.
> > >- *5+* public originations (e.g. eBay, Paypal, Yihaodian, Dataguise,
> > >etc.) are using or adopting eagle to monitor their hadoop clusters.
> > >- Shared eagle and apache way in *10+* tech conferences in* 8+
> > > *different
> > >cities around the world (e.g. Hadoop Summit, Hadoop Stratus, QCon,
> > etc.)
> > >
> > > - Hao
> > >
> > > On Tue, Oct 18, 2016 at 10:24 AM, Michael Wu  wrote:
> > >
> > > > +1
> > > >
> > > >  - 2 releases have been made and committers have summed lots of
> > > experience
> > > > of the releasing process.
> > > >  - More and more contributions are received from the community.
> > > >  - JIRA tickets are all with detailed descriptions.
> > > >  - PRs follow a good way of collaboration.
> > > >  - The project is being established in the industry.
> > > >  - Responses are made timely to requesters.
> > > >
> > > >
> > > > On Tue, Oct 18, 2016 at 8:04 AM, Liangfei.Su 
> > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Eagle Maturity Assessment clear listed and completed.
> > > > > JIRA with clear comments.
> > > > > PRs follow the convention that point to given JIRA by apache
> naming.
> > > This
> > > > > keeps clear commit history and friendly comments.
> > > > > Very happy to see more contributors other than originators to join
> > in.
> > > > > Documentation, these are continuing improved to help community
> easier
> > > to
> > > > > involve in.
> > > > >
> > > > > Thanks,
> > > > > Ralph
> > > > >
> > > > >
> > > > > On Mon, Oct 17, 2016 at 8:16 PM, Jinhu Wu 
> > > > wrote:
> > > > >
> > > > > > Vote +1.
> > > > > >
> > > > > > There are more and more contributors and they are making great
> > > > > > contributions to Apache Eagle.
> > > > > > Eagle codes are more stable and documents are more helpful to use
> > > eagle
> > > > > > system.
> > > > > >
> > > > > > Besides, Eagle team are working with other developers in other
> > > > > corporations
> > > > > > to discuss some features and optimizations to make eagle more
> > > powerful.
> > > > > >
> > > > > > I am also happy to become an Eagle committer and hope Eagle will
> be
> > > > > better.
> > > > > >
> > > > > > Thanks
> > > > > > Jinhu
> > > > > >
> > > > > > On Fri, Oct 14, 2016 at 5:29 AM, Da Zhou <
> daveloperz...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > Vote +1.
> > > > > > >  "Eagle Maturity Assessment" looks good to me. Great process
> has
> > > been
> > > > > > made
> > > > > > > since last discussion:
> > > > > > >
> > > > > > > - Lots of new features have been introduced, now Apache Eagle
> has
> > > > > become
> > > > > > > more powerful and user-friendly.(eg,  Application Management
> > > through
> > > > > > Eagle
> > > > > > > UI.)
> > > > > > > - Also many fixes have been checked in, which makes Eagle more
> > > stable
> > > > > and
> > > > > > > robust.
> > > > > > > - Community is getting more active, we can tell this based on
> > daily
> > > > > > > discussion happened in the emails.
> > > > > > > - Apache Eagle is getting more attention

[jira] [Created] (EAGLE-636) Absence Alert Engine doesn't alert in some case

[JiJun Tang (JIRA)]

JiJun Tang created EAGLE-636:


 Summary: Absence Alert Engine doesn't alert in some case
 Key: EAGLE-636
 URL: https://issues.apache.org/jira/browse/EAGLE-636
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: JiJun Tang
Assignee: JiJun Tang
 Fix For: v0.5.0


Something must happen within a specific time range within a day. For example 
one type of job {color:red}must be{color} running from 1PM - 2PM every day.
I think Absence Alert Engine should alert when a job running from 10AM-4PM or 
10AM-1PM.For now ,it doesn't alert.



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

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

[Apache Jenkins Server]

The Apache Jenkins build system has built incubator-eagle-main (build #215) 
Status: Failure Check console output at 
https://builds.apache.org/job/incubator-eagle-main/215/ to view the 
results. Test Report is at: Test Result

[GitHub] incubator-eagle issue #530: [EAGLE-634] clean up configuration for MR runnin...

[qingwen220]

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/530
  
LGTM


---
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-634) clean up configuration for MR running feeder

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-634:
--

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/530
  
LGTM


> clean up configuration for MR running feeder
> 
>
> Key: EAGLE-634
> URL: https://issues.apache.org/jira/browse/EAGLE-634
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



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

[GitHub] incubator-eagle pull request #531: EAGLE-637 set task number of UnitTopology...

[qingwen220]

GitHub user qingwen220 opened a pull request:

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

EAGLE-637 set task number of UnitTopologyRunner

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

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

$ git pull https://github.com/qingwen220/incubator-eagle quickFix

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

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


commit 22519845d21f44a87a20f6e5aad707b91a4c2e2d
Author: Zhao, Qingwen 
Date:   2016-10-18T11:30:20Z

set task number of UnitTopologyRunner

commit bfbb5a3499efbd203a41cbf4d915c5102a3032dc
Author: Zhao, Qingwen 
Date:   2016-10-18T12:50:22Z

set router & alert task number as 1




---
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-637) Set router/alert task number of UnitTopologyRunner

[Zhao, Qingwen (JIRA)]

Zhao, Qingwen created EAGLE-637:
---

 Summary: Set router/alert task number of UnitTopologyRunner
 Key: EAGLE-637
 URL: https://issues.apache.org/jira/browse/EAGLE-637
 Project: Eagle
  Issue Type: Improvement
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen


In UnitTopologyRunner, the router/alert bolt task number is not set. The 
default value is 1. While in some cases, if the task number is not 1, then the 
logical is wrong. 



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

[GitHub] incubator-eagle pull request #530: [EAGLE-634] clean up configuration for MR...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-637) Set router/alert task number of UnitTopologyRunner

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-637:
--

GitHub user qingwen220 opened a pull request:

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

EAGLE-637 set task number of UnitTopologyRunner

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

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

$ git pull https://github.com/qingwen220/incubator-eagle quickFix

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

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


commit 22519845d21f44a87a20f6e5aad707b91a4c2e2d
Author: Zhao, Qingwen 
Date:   2016-10-18T11:30:20Z

set task number of UnitTopologyRunner

commit bfbb5a3499efbd203a41cbf4d915c5102a3032dc
Author: Zhao, Qingwen 
Date:   2016-10-18T12:50:22Z

set router & alert task number as 1




> Set router/alert task number of UnitTopologyRunner
> --
>
> Key: EAGLE-637
> URL: https://issues.apache.org/jira/browse/EAGLE-637
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> In UnitTopologyRunner, the router/alert bolt task number is not set. The 
> default value is 1. While in some cases, if the task number is not 1, then 
> the logical is wrong. 



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

[jira] [Commented] (EAGLE-634) clean up configuration for MR running feeder

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-634:
--

Github user asfgit closed the pull request at:

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


> clean up configuration for MR running feeder
> 
>
> Key: EAGLE-634
> URL: https://issues.apache.org/jira/browse/EAGLE-634
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



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

[jira] [Closed] (EAGLE-634) clean up configuration for MR running feeder

[wujinhu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wujinhu closed EAGLE-634.
-
Resolution: Resolved

> clean up configuration for MR running feeder
> 
>
> Key: EAGLE-634
> URL: https://issues.apache.org/jira/browse/EAGLE-634
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



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

[jira] [Closed] (EAGLE-558) Use dynamical loaded jarPath as default value in ApplicationEntity

[wujinhu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wujinhu closed EAGLE-558.
-
Resolution: Resolved

> Use dynamical loaded jarPath as default value in ApplicationEntity
> --
>
> Key: EAGLE-558
> URL: https://issues.apache.org/jira/browse/EAGLE-558
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> Use dynamical loaded jarPath as default value in ApplicationEntity, which 
> could also be forcefully replaced with InstallOperation
> It's an improvement from patch: 
> https://github.com/apache/incubator-eagle/commit/6fc103338fa3e3275a1357144dfab2feb1a103ec#diff-c9c5f683c463429e5e1c01b8b6fa71b7



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

[jira] [Created] (EAGLE-638) clean up configuration for Eagle JPM aggregation feeder

[wujinhu (JIRA)]

wujinhu created EAGLE-638:
-

 Summary: clean up configuration for Eagle JPM aggregation feeder
 Key: EAGLE-638
 URL: https://issues.apache.org/jira/browse/EAGLE-638
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


1. remove useless configure
2. add required field to application provider.xml
3. add description to application provider.xml



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

[jira] [Created] (EAGLE-639) Generate sortSpec only on externalWindow

[Hao Chen (JIRA)]

Hao Chen created EAGLE-639:
--

 Summary: Generate sortSpec only on externalWindow
 Key: EAGLE-639
 URL: https://issues.apache.org/jira/browse/EAGLE-639
 Project: Eagle
  Issue Type: Sub-task
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


Generate sortSpec only on externalWindow



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

[GitHub] incubator-eagle pull request #532: [EAGLE-639] Generate sortSpec on external...

[haoch]

GitHub user haoch opened a pull request:

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

[EAGLE-639] Generate sortSpec on externalWindow

Generate sortSpec on externalWindow

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

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

$ git pull https://github.com/haoch/incubator-eagle EnhancePolicyIntepreter

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

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


commit fddcfdb4931ed399fef819d975e1749dcb986b6f
Author: Hao Chen 
Date:   2016-10-19T04:39:32Z

Generate sortSpec on externalWindow




---
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-639) Generate sortSpec only on externalWindow

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-639:
--

GitHub user haoch opened a pull request:

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

[EAGLE-639] Generate sortSpec on externalWindow

Generate sortSpec on externalWindow

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

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

$ git pull https://github.com/haoch/incubator-eagle EnhancePolicyIntepreter

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

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


commit fddcfdb4931ed399fef819d975e1749dcb986b6f
Author: Hao Chen 
Date:   2016-10-19T04:39:32Z

Generate sortSpec on externalWindow




> Generate sortSpec only on externalWindow
> 
>
> Key: EAGLE-639
> URL: https://issues.apache.org/jira/browse/EAGLE-639
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Generate sortSpec only on externalWindow



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

[GitHub] incubator-eagle pull request #531: EAGLE-637 set task number of UnitTopology...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-637) Set router/alert task number of UnitTopologyRunner

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-637:
--

Github user asfgit closed the pull request at:

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


> Set router/alert task number of UnitTopologyRunner
> --
>
> Key: EAGLE-637
> URL: https://issues.apache.org/jira/browse/EAGLE-637
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> In UnitTopologyRunner, the router/alert bolt task number is not set. The 
> default value is 1. While in some cases, if the task number is not 1, then 
> the logical is wrong. 



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

[EAGLE TEST FAILED] incubator-eagle-main failed in testing phase on build #219

[Apache Jenkins Server]

The Apache Jenkins build system has built incubator-eagle-main (build #219) 
Status: Unstable Check console output at 
https://builds.apache.org/job/incubator-eagle-main/219/ to view the 
results. Test Report is at: Test Result