[jira] [Created] (EAGLE-648) Stream router does not work properly sometimes

2016-10-19 Thread Garrett Li (JIRA) 
Garrett Li created EAGLE-648:


 Summary: Stream router does not work properly sometimes
 Key: EAGLE-648
 URL: https://issues.apache.org/jira/browse/EAGLE-648
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Garrett Li
Assignee: Garrett Li
 Fix For: v0.5.0


Stream router does not work properly when multiple policies use the same input 
stream with the same partition definition. It is because stream router bolt 
output maintains a map of the route specs, but the key of the map is streamId + 
partition information. The monitor stream may override each other if the 
streamId and partition are the same.



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

[jira] [Created] (EAGLE-649) Request Eagle Server will throw NoSuchMethodError

2016-10-19 Thread JiJun Tang (JIRA) 
JiJun Tang created EAGLE-649:


 Summary: Request Eagle Server will throw NoSuchMethodError
 Key: EAGLE-649
 URL: https://issues.apache.org/jira/browse/EAGLE-649
 Project: Eagle
  Issue Type: Bug
Reporter: JiJun Tang
Priority: Minor


I git clone the code ,then mvn clean package -DskipTests=true.
Then execute eagle-service.sh to start the server.But when I visit the server 
by Chrome. The exception throw as below:
{noformat}
WARN [2016-10-20 04:35:32,541] org.eclipse.jetty.servlet.ServletHandler: Error 
for /rest/apps/providers
! java.lang.NoSuchMethodError: 
javax.servlet.http.HttpServletRequest.getServletContext()Ljavax/servlet/ServletContext;
! at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:312) 
~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at io.dropwizard.jetty.BiDiGzipFilter.doFilter(BiDiGzipFilter.java:127) 
~[dropwizard-jetty-0.7.1.jar:0.7.1]
! at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486)
 ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at io.dropwizard.servlets.ThreadNameFilter.doFilter(ThreadNameFilter.java:29) 
~[dropwizard-servlets-0.7.1.jar:0.7.1]
! at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486)
 ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
io.dropwizard.jersey.filter.AllowedMethodsFilter.handle(AllowedMethodsFilter.java:44)
 ~[dropwizard-jersey-0.7.1.jar:0.7.1]
! at 
io.dropwizard.jersey.filter.AllowedMethodsFilter.doFilter(AllowedMethodsFilter.java:39)
 ~[dropwizard-jersey-0.7.1.jar:0.7.1]
! at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486)
 ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.apache.eagle.alert.resource.SimpleCORSFiler.doFilter(SimpleCORSFiler.java:51)
 ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486)
 ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:66)
 ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
 ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113) 
~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486)
 ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519) 
[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097)
 [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448) 
[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031)
 [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) 
[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) 
[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
com.codahale.metrics.jetty9.InstrumentedHandler.handle(InstrumentedHandler.java:175)
 [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at io.dropwizard.jetty.RoutingHandler.handle(RoutingHandler.java:51) 
[dropwizard-jetty-0.7.1.jar:0.7.1]
! at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) 
[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.server.handler.RequestLogHandler.handle(RequestLogHandler.java:92)
 [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) 
[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:162)
 [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) 
[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at org.eclipse.jetty.server.Server.handle(Server.java:446) 
[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271) 
[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
! at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246)

[jira] [Commented] (EAGLE-644) optimize some default configurations for JPM

2016-10-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-644:
--

Github user asfgit closed the pull request at:

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


> optimize some default configurations for JPM
> 
>
> Key: EAGLE-644
> URL: https://issues.apache.org/jira/browse/EAGLE-644
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> optimize some default configurations for JPM



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

[jira] [Updated] (EAGLE-647) Support Policy Execution Interpreter and Planner to compile siddhi query to distributed execution plan

2016-10-19 Thread Hao Chen (JIRA) 

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

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

> Support Policy Execution Interpreter and Planner to compile siddhi query to 
> distributed execution plan
> --
>
> Key: EAGLE-647
> URL: https://issues.apache.org/jira/browse/EAGLE-647
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Support Policy Execution Interpreter and Planner to compile siddhi query to 
> distributed execution plan
> * Support parse siddhi pattern and join query as distributed execution
> * Support alias in inner join condition
> * Refactor PolicyIntepreter to eagle-alert-engine and decoupel 
> PolicyExecutionPlanner
> * Fix factory method for PolicyExecutionPlanner



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

[GitHub] incubator-eagle pull request #536: [EAGLE-647] Support Policy Execution Inte...

2016-10-19 Thread haoch 
GitHub user haoch opened a pull request:

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

[EAGLE-647] Support Policy Execution Interpreter and Planner to compile 
siddhi query to distributed execution plan

Support Policy Execution Interpreter and Planner to compile siddhi query to 
distributed execution plan

* Support parse siddhi pattern and join query as distributed execution
* Support alias in inner join condition
* Refactor PolicyIntepreter to eagle-alert-engine and decoupel 
PolicyExecutionPlanner
* Fix factory method for PolicyExecutionPlanner

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

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

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

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


commit 4a804e9a8f3240d4e7c8ad469a160ac06cb32259
Author: Hao Chen 
Date:   2016-10-19T13:25:20Z

Support parse siddhi pattern and join query as distributed execution plan

commit 58c63fb10c271cd0de9377fa3935e35f972718ce
Author: Hao Chen 
Date:   2016-10-20T03:10:20Z

Support alias in inner join condition

commit c30f3b303e8fdc9e25cebc75aa6386ff55a28921
Author: Hao Chen 
Date:   2016-10-20T03:38:10Z

Refactor PolicyIntepreter to eagle-alert-engine and decoupel 
PolicyExecutionPlanner

commit 08d911cb1989f4a05aab19419f3791786023debb
Author: Hao Chen 
Date:   2016-10-20T03:42:23Z

Fix factory method for PolicyExecutionPlanner




---
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-647) Support Policy Execution Interpreter and Planner to compile siddhi query to distributed execution plan

2016-10-19 Thread Hao Chen (JIRA) 
Hao Chen created EAGLE-647:
--

 Summary: Support Policy Execution Interpreter and Planner to 
compile siddhi query to distributed execution plan
 Key: EAGLE-647
 URL: https://issues.apache.org/jira/browse/EAGLE-647
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


Support Policy Execution Interpreter and Planner to compile siddhi query to 
distributed execution plan

* Support parse siddhi pattern and join query as distributed execution
* Support alias in inner join condition
* Refactor PolicyIntepreter to eagle-alert-engine and decoupel 
PolicyExecutionPlanner
* Fix factory method for PolicyExecutionPlanner



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

[jira] [Commented] (EAGLE-647) Support Policy Execution Interpreter and Planner to compile siddhi query to distributed execution plan

2016-10-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-647:
--

GitHub user haoch opened a pull request:

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

[EAGLE-647] Support Policy Execution Interpreter and Planner to compile 
siddhi query to distributed execution plan

Support Policy Execution Interpreter and Planner to compile siddhi query to 
distributed execution plan

* Support parse siddhi pattern and join query as distributed execution
* Support alias in inner join condition
* Refactor PolicyIntepreter to eagle-alert-engine and decoupel 
PolicyExecutionPlanner
* Fix factory method for PolicyExecutionPlanner

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

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

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

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


commit 4a804e9a8f3240d4e7c8ad469a160ac06cb32259
Author: Hao Chen 
Date:   2016-10-19T13:25:20Z

Support parse siddhi pattern and join query as distributed execution plan

commit 58c63fb10c271cd0de9377fa3935e35f972718ce
Author: Hao Chen 
Date:   2016-10-20T03:10:20Z

Support alias in inner join condition

commit c30f3b303e8fdc9e25cebc75aa6386ff55a28921
Author: Hao Chen 
Date:   2016-10-20T03:38:10Z

Refactor PolicyIntepreter to eagle-alert-engine and decoupel 
PolicyExecutionPlanner

commit 08d911cb1989f4a05aab19419f3791786023debb
Author: Hao Chen 
Date:   2016-10-20T03:42:23Z

Fix factory method for PolicyExecutionPlanner




> Support Policy Execution Interpreter and Planner to compile siddhi query to 
> distributed execution plan
> --
>
> Key: EAGLE-647
> URL: https://issues.apache.org/jira/browse/EAGLE-647
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Support Policy Execution Interpreter and Planner to compile siddhi query to 
> distributed execution plan
> * Support parse siddhi pattern and join query as distributed execution
> * Support alias in inner join condition
> * Refactor PolicyIntepreter to eagle-alert-engine and decoupel 
> PolicyExecutionPlanner
> * Fix factory method for PolicyExecutionPlanner



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

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

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

[jira] [Created] (EAGLE-645) No log retention for eagle server log

2016-10-19 Thread Zhao, Qingwen (JIRA) 
Zhao, Qingwen created EAGLE-645:
---

 Summary: No log retention for eagle server log
 Key: EAGLE-645
 URL: https://issues.apache.org/jira/browse/EAGLE-645
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Zhao, Qingwen
 Fix For: v0.5.0


There is not any retention configurations in Eagle server. The logs keeps 
increasing 



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

[jira] [Closed] (EAGLE-644) optimize some default configurations for JPM

2016-10-19 Thread wujinhu (JIRA) 

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

wujinhu closed EAGLE-644.
-
Resolution: Resolved

> optimize some default configurations for JPM
> 
>
> Key: EAGLE-644
> URL: https://issues.apache.org/jira/browse/EAGLE-644
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> optimize some default configurations for JPM



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

[GitHub] incubator-eagle pull request #535: [EAGLE-644] optimize some default configu...

2016-10-19 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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-644) optimize some default configurations for JPM

2016-10-19 Thread wujinhu (JIRA) 
wujinhu created EAGLE-644:
-

 Summary: optimize some default configurations for JPM
 Key: EAGLE-644
 URL: https://issues.apache.org/jira/browse/EAGLE-644
 Project: Eagle
  Issue Type: Improvement
Reporter: wujinhu
Assignee: wujinhu


optimize some default configurations for JPM



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

[jira] [Commented] (EAGLE-644) optimize some default configurations for JPM

2016-10-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-644:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-644] optimize some default configurations for JPM



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

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

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

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


commit 75c753a6449340a32ed8bc32fa02156a7585f573
Author: wujinhu 
Date:   2016-10-20T02:24:44Z

optimize some default configurations for JPM




> optimize some default configurations for JPM
> 
>
> Key: EAGLE-644
> URL: https://issues.apache.org/jira/browse/EAGLE-644
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> optimize some default configurations for JPM



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

[GitHub] incubator-eagle pull request #535: [EAGLE-644] optimize some default configu...

2016-10-19 Thread wujinhu 
GitHub user wujinhu opened a pull request:

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

[EAGLE-644] optimize some default configurations for JPM



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

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

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

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


commit 75c753a6449340a32ed8bc32fa02156a7585f573
Author: wujinhu 
Date:   2016-10-20T02:24:44Z

optimize some default configurations for JPM




---
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-643) Implement oozieAuditLogAppProvider

2016-10-19 Thread JiJun Tang (JIRA) 
JiJun Tang created EAGLE-643:


 Summary: Implement oozieAuditLogAppProvider
 Key: EAGLE-643
 URL: https://issues.apache.org/jira/browse/EAGLE-643
 Project: Eagle
  Issue Type: New Feature
Reporter: JiJun Tang
Assignee: JiJun Tang
Priority: Minor
 Fix For: v0.5.0






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

[jira] [Created] (EAGLE-642) move application runtime configure to ApplicationEntity context

2016-10-19 Thread wujinhu (JIRA) 
wujinhu created EAGLE-642:
-

 Summary: move application runtime configure to ApplicationEntity 
context
 Key: EAGLE-642
 URL: https://issues.apache.org/jira/browse/EAGLE-642
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


When install an application, there are some configures like appId/siteId that 
should not changed by user, so we move them to context.



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

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

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

[jira] [Commented] (EAGLE-641) Publishment reload may introduce NPE

2016-10-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-641:
--

Github user asfgit closed the pull request at:

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


> Publishment reload may introduce NPE
> 
>
> Key: EAGLE-641
> URL: https://issues.apache.org/jira/browse/EAGLE-641
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>
> 2016-10-18 23:59:12.128 o.a.c.f.r.c.NodeCache [ERROR] Calling listener
> java.lang.NullPointerException
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertKafkaPublisher.update(AlertKafkaPublisher.java:78)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:164)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:109)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNotifyService.java:102)
>  ~[stormjar.jar:?]
>   at java.util.ArrayList.forEach(ArrayList.java:1249) 
> ~[?:1.8.0_92-internal]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyService.java:102)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:132)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44)
>  ~[stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
>  [stormjar.jar:?]
>   at 
> com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254)
>  [stormjar.jar:?]
>   at 
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) 
> [stormjar.jar:?]
>   at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) 
> [stormjar.jar:?]



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

[GitHub] incubator-eagle pull request #534: EAGLE-641: Publishment reload may introdu...

2016-10-19 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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 TEST FAILED] incubator-eagle-main failed in testing phase on build #222

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

[jira] [Resolved] (EAGLE-641) Publishment reload may introduce NPE

2016-10-19 Thread Garrett Li (JIRA) 

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

Garrett Li resolved EAGLE-641.
--
Resolution: Fixed

> Publishment reload may introduce NPE
> 
>
> Key: EAGLE-641
> URL: https://issues.apache.org/jira/browse/EAGLE-641
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>
> 2016-10-18 23:59:12.128 o.a.c.f.r.c.NodeCache [ERROR] Calling listener
> java.lang.NullPointerException
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertKafkaPublisher.update(AlertKafkaPublisher.java:78)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:164)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:109)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNotifyService.java:102)
>  ~[stormjar.jar:?]
>   at java.util.ArrayList.forEach(ArrayList.java:1249) 
> ~[?:1.8.0_92-internal]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyService.java:102)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:132)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44)
>  ~[stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
>  [stormjar.jar:?]
>   at 
> com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254)
>  [stormjar.jar:?]
>   at 
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) 
> [stormjar.jar:?]
>   at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) 
> [stormjar.jar:?]



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

[GitHub] incubator-eagle pull request #534: EAGLE-641: Publishment reload may introdu...

2016-10-19 Thread garrettlish 
GitHub user garrettlish opened a pull request:

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

EAGLE-641: Publishment reload may introduce NPE

The publishment initialization may have problem which will cause reload NPE.

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

$ git pull https://github.com/garrettlish/incubator-eagle master

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

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


commit 2aa04ec59587c643056380cfa8ee3b0a3db0f847
Author: Xiancheng Li 
Date:   2016-10-19T09:53:35Z

EAGLE-641: Publishment reload may introduce NPE

The publishment initialization may have problem which will cause reload NPE.




---
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-641) Publishment reload may introduce NPE

2016-10-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-641:
--

GitHub user garrettlish opened a pull request:

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

EAGLE-641: Publishment reload may introduce NPE

The publishment initialization may have problem which will cause reload NPE.

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

$ git pull https://github.com/garrettlish/incubator-eagle master

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

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


commit 2aa04ec59587c643056380cfa8ee3b0a3db0f847
Author: Xiancheng Li 
Date:   2016-10-19T09:53:35Z

EAGLE-641: Publishment reload may introduce NPE

The publishment initialization may have problem which will cause reload NPE.




> Publishment reload may introduce NPE
> 
>
> Key: EAGLE-641
> URL: https://issues.apache.org/jira/browse/EAGLE-641
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>
> 2016-10-18 23:59:12.128 o.a.c.f.r.c.NodeCache [ERROR] Calling listener
> java.lang.NullPointerException
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertKafkaPublisher.update(AlertKafkaPublisher.java:78)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:164)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:109)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNotifyService.java:102)
>  ~[stormjar.jar:?]
>   at java.util.ArrayList.forEach(ArrayList.java:1249) 
> ~[?:1.8.0_92-internal]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyService.java:102)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:132)
>  ~[stormjar.jar:?]
>   at 
> org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44)
>  ~[stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
>  [stormjar.jar:?]
>   at 
> com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516)
>  [stormjar.jar:?]
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254)
>  [stormjar.jar:?]
>   at 
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) 
> [stormjar.jar:?]
>   at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) 
> [stormjar.jar:?]



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

[jira] [Created] (EAGLE-641) Publishment reload may introduce NPE

2016-10-19 Thread Garrett Li (JIRA) 
Garrett Li created EAGLE-641:


 Summary: Publishment reload may introduce NPE
 Key: EAGLE-641
 URL: https://issues.apache.org/jira/browse/EAGLE-641
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Garrett Li
Assignee: Garrett Li


2016-10-18 23:59:12.128 o.a.c.f.r.c.NodeCache [ERROR] Calling listener
java.lang.NullPointerException
at 
org.apache.eagle.alert.engine.publisher.impl.AlertKafkaPublisher.update(AlertKafkaPublisher.java:78)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:164)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:109)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNotifyService.java:102)
 ~[stormjar.jar:?]
at java.util.ArrayList.forEach(ArrayList.java:1249) 
~[?:1.8.0_92-internal]
at 
org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyService.java:102)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:132)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44)
 ~[stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287)
 [stormjar.jar:?]
at 
org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
 [stormjar.jar:?]
at 
com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
 [stormjar.jar:?]
at 
org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111)
 [stormjar.jar:?]
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730)
 [stormjar.jar:?]
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516)
 [stormjar.jar:?]
at 
org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254)
 [stormjar.jar:?]
at 
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) 
[stormjar.jar:?]
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) 
[stormjar.jar:?]




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

[jira] [Resolved] (EAGLE-594) Remove raw alert from kafka publisher

2016-10-19 Thread Garrett Li (JIRA) 

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

Garrett Li resolved EAGLE-594.
--
Resolution: Fixed

> Remove raw alert from kafka publisher
> -
>
> Key: EAGLE-594
> URL: https://issues.apache.org/jira/browse/EAGLE-594
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>Assignee: Garrett Li
>Priority: Minor
>
> We are leveraging configured deduplicator to dedup the duplicated alerts 
> before publish to kafka, email, slack, etc. However, sometimes we may still 
> want to keep the raw alerts in kafka. Here we have defined 
> rawAlertNamespaceLabel and rawAlertNamespaceValue custom fields to emit the 
> raw alerts into kafka. 
> However, these configured namespace concept is ebay/sherlock specific, we 
> should remove it from eagle and use it ebay/sherlock extended kafka publisher.



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

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

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

[jira] [Closed] (EAGLE-43) Eagle Job Running Spout should support HTTPS

2016-10-19 Thread wujinhu (JIRA) 

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

wujinhu closed EAGLE-43.

   Resolution: Fixed
Fix Version/s: v0.5.0

> Eagle Job Running Spout should support HTTPS
> 
>
> Key: EAGLE-43
> URL: https://issues.apache.org/jira/browse/EAGLE-43
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Libin, Sun
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> Job Running Spout is a data source for hive security monitoring, it get data 
> from RM yarn API and RM web page, currently we only support HTTP, should add 
> HTTPS supprot



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

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

2016-10-19 Thread wujinhu (JIRA) 

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

wujinhu closed EAGLE-638.
-
Resolution: Resolved

> 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] [Commented] (EAGLE-638) clean up configuration for Eagle JPM aggregation feeder

2016-10-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-638:
--

Github user asfgit closed the pull request at:

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


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

[GitHub] incubator-eagle pull request #533: [EAGLE-638] clean up configuration for Ea...

2016-10-19 Thread asfgit 
Github user asfgit closed the pull request at:

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


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

2016-10-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-639:
--

Github user asfgit closed the pull request at:

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


> 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 only on ext...

2016-10-19 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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 TEST FAILED] incubator-eagle-main failed in testing phase on build #220

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

[jira] [Commented] (EAGLE-563) Refactor Hadoop queue feeder using application framework

2016-10-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-563:
--

Github user asfgit closed the pull request at:

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


> 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 pull request #528: [EAGLE-563] migrate eagle-hadoop-queue to...

2016-10-19 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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-638) clean up configuration for Eagle JPM aggregation feeder

2016-10-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-638:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-638] clean up configuration for Eagle JPM aggregation feeder



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

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

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

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


commit 8c08cd15e029f9e629615b5f991a83d31d7dec06
Author: wujinhu 
Date:   2016-10-19T07:30:57Z

clean up configuration for Eagle JPM aggregation feeder




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

[GitHub] incubator-eagle pull request #533: [EAGLE-638] clean up configuration for Ea...

2016-10-19 Thread wujinhu 
GitHub user wujinhu opened a pull request:

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

[EAGLE-638] clean up configuration for Eagle JPM aggregation feeder



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

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

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

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


commit 8c08cd15e029f9e629615b5f991a83d31d7dec06
Author: wujinhu 
Date:   2016-10-19T07:30:57Z

clean up configuration for Eagle JPM aggregation 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] [Created] (EAGLE-640) Publishment reload may introduce NPE

2016-10-19 Thread Garrett Li (JIRA) 
Garrett Li created EAGLE-640:


 Summary: Publishment reload may introduce NPE
 Key: EAGLE-640
 URL: https://issues.apache.org/jira/browse/EAGLE-640
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Garrett Li
Assignee: Garrett Li


2016-10-18 23:59:12.128 o.a.c.f.r.c.NodeCache [ERROR] Calling listener
java.lang.NullPointerException
at 
org.apache.eagle.alert.engine.publisher.impl.AlertKafkaPublisher.update(AlertKafkaPublisher.java:78)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.onPublishChange(AlertPublisherImpl.java:164)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.engine.runner.AlertPublisherBolt.onAlertPublishSpecChange(AlertPublisherBolt.java:109)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifyAlertPublishBolt$3(AbstractMetadataChangeNotifyService.java:102)
 ~[stormjar.jar:?]
at java.util.ArrayList.forEach(ArrayList.java:1249) 
~[?:1.8.0_92-internal]
at 
org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifyAlertPublishBolt(AbstractMetadataChangeNotifyService.java:102)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:132)
 ~[stormjar.jar:?]
at 
org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44)
 ~[stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287)
 [stormjar.jar:?]
at 
org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
 [stormjar.jar:?]
at 
com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
 [stormjar.jar:?]
at 
org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53)
 [stormjar.jar:?]
at 
org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111)
 [stormjar.jar:?]
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730)
 [stormjar.jar:?]
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516)
 [stormjar.jar:?]
at 
org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254)
 [stormjar.jar:?]
at 
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) 
[stormjar.jar:?]
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) 
[stormjar.jar:?]




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

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

2016-10-19 Thread 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