[jira] [Commented] (EAGLE-593) Eagle Topology assembly multi-version Hadoop support & bug fix

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-593:
--

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/481#discussion_r82543889
  
--- Diff: eagle-core/eagle-app/eagle-app-base/pom.xml ---
@@ -62,6 +62,11 @@
 1.1.1
 
 
+org.apache.thrift
+libthrift
+0.9.2
--- End diff --

avoid declaring version directly in nested modules.


> Eagle Topology assembly multi-version Hadoop support & bug fix
> --
>
> Key: EAGLE-593
> URL: https://issues.apache.org/jira/browse/EAGLE-593
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. User may want to support different version of hadoop in eagle jpm when 
> uses topology asembly to be a final package. For this requirement, we add 
> profiles to eagle-topology-assembly pom.xml. In this pom, we could add 
> different versions of Hadoop.
> 2. Fix StormSubmitter does not support submit another jar
> In storm StormSubmitter
> --
> private static String submittedJar = null;
> private static void submitJar(Map conf, ProgressListener listener) {
> if(submittedJar==null) {
> LOG.info("Jar not uploaded to master yet. Submitting jar...");
> String localJar = System.getProperty("storm.jar");
> submittedJar = submitJar(conf, localJar, listener);
> } else {
> LOG.info("Jar already uploaded to master. Not submitting jar.");
> }
> }
> --
> It can not submit another jar once submittedJar is set.
> So I rewrote this class.
> 3. Fix MR Running Job that does not set finished jobs' state



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

[GitHub] incubator-eagle pull request #481: [EAGLE-593] Eagle Topology assembly multi...

[haoch]

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/481#discussion_r82543889
  
--- Diff: eagle-core/eagle-app/eagle-app-base/pom.xml ---
@@ -62,6 +62,11 @@
 1.1.1
 
 
+org.apache.thrift
+libthrift
+0.9.2
--- End diff --

avoid declaring version directly in nested modules.


---
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-593) Eagle Topology assembly multi-version Hadoop support & bug fix

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-593:
--

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/481#discussion_r82543907
  
--- Diff: 
eagle-core/eagle-app/eagle-app-base/src/main/java/org/apache/eagle/app/environment/impl/StormSubmitter.java
 ---
@@ -0,0 +1,317 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.eagle.app.environment.impl;
+import java.io.File;
+import java.nio.ByteBuffer;
+import java.util.HashMap;
+import java.util.Map;
+
+import org.apache.commons.lang.StringUtils;
+import org.json.simple.JSONValue;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import backtype.storm.generated.AlreadyAliveException;
+import backtype.storm.generated.ClusterSummary;
+import backtype.storm.generated.InvalidTopologyException;
+import backtype.storm.generated.Nimbus;
+import backtype.storm.generated.StormTopology;
+import backtype.storm.generated.SubmitOptions;
+import backtype.storm.generated.TopologySummary;
+import backtype.storm.utils.BufferFileInputStream;
+import backtype.storm.utils.NimbusClient;
+import backtype.storm.utils.Utils;
+import backtype.storm.Config;
+
+/**
+ * copy from storm StormSubmitter
+ * just rewrite StormSubmitter that does not support summit other jars 
once submittedJar is set.
+ * Our implementation will not add this restrict.
+ */
+
--- End diff --

Keep original comments


> Eagle Topology assembly multi-version Hadoop support & bug fix
> --
>
> Key: EAGLE-593
> URL: https://issues.apache.org/jira/browse/EAGLE-593
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. User may want to support different version of hadoop in eagle jpm when 
> uses topology asembly to be a final package. For this requirement, we add 
> profiles to eagle-topology-assembly pom.xml. In this pom, we could add 
> different versions of Hadoop.
> 2. Fix StormSubmitter does not support submit another jar
> In storm StormSubmitter
> --
> private static String submittedJar = null;
> private static void submitJar(Map conf, ProgressListener listener) {
> if(submittedJar==null) {
> LOG.info("Jar not uploaded to master yet. Submitting jar...");
> String localJar = System.getProperty("storm.jar");
> submittedJar = submitJar(conf, localJar, listener);
> } else {
> LOG.info("Jar already uploaded to master. Not submitting jar.");
> }
> }
> --
> It can not submit another jar once submittedJar is set.
> So I rewrote this class.
> 3. Fix MR Running Job that does not set finished jobs' state



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

[GitHub] incubator-eagle pull request #481: [EAGLE-593] Eagle Topology assembly multi...

[haoch]

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/481#discussion_r82543907
  
--- Diff: 
eagle-core/eagle-app/eagle-app-base/src/main/java/org/apache/eagle/app/environment/impl/StormSubmitter.java
 ---
@@ -0,0 +1,317 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.eagle.app.environment.impl;
+import java.io.File;
+import java.nio.ByteBuffer;
+import java.util.HashMap;
+import java.util.Map;
+
+import org.apache.commons.lang.StringUtils;
+import org.json.simple.JSONValue;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import backtype.storm.generated.AlreadyAliveException;
+import backtype.storm.generated.ClusterSummary;
+import backtype.storm.generated.InvalidTopologyException;
+import backtype.storm.generated.Nimbus;
+import backtype.storm.generated.StormTopology;
+import backtype.storm.generated.SubmitOptions;
+import backtype.storm.generated.TopologySummary;
+import backtype.storm.utils.BufferFileInputStream;
+import backtype.storm.utils.NimbusClient;
+import backtype.storm.utils.Utils;
+import backtype.storm.Config;
+
+/**
+ * copy from storm StormSubmitter
+ * just rewrite StormSubmitter that does not support summit other jars 
once submittedJar is set.
+ * Our implementation will not add this restrict.
+ */
+
--- End diff --

Keep original comments


---
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-582) register simple Basic Authentication to server application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-582:
--

Github user anyway1021 commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/468#discussion_r82542185
  
--- Diff: eagle-server/src/main/resources/application.conf ---
@@ -115,4 +115,49 @@ coordinator {
 initDelayMillis = 1000
 delayMillis = 3
   }
+}
+
+# -
+# Eagle Authentication Configuration
+# -
+
+auth {
+  # indicating authentication mode, "simple" or "ldap"
+  mode = simple
+
+  # indicating whether to use cache: cache is usually used for 
authentications that may
+  # not handle high throughput (an RDBMS or LDAP server, for example)
+  cache = false
+
+  # indicating the cache policy, containing maximumSize and 
expireAfterWrite, e.g. maximumSize=1, expireAfterWrite=10m
+  cachePolicy = "maximumSize=1, expireAfterWrite=1m"
+
+  # indicating whether authorization is needed
+  authorize = false
+
+  # indicating whether @Auth annotation on parameters is needed
+  parameter.annotation = true
+
+  # for basic authentication, effective only when auth.mode=simple
+  simple {
+# username for basic authentication, effective only when 
auth.mode=simple
+username = "admin"
+
+# password for basic authentication, effective only when 
auth.mode=simple
+password = "secret"
+  }
+
+  # for ldap authentication, effective only when auth.mode=ldap
+  ldap {
+uri = "ldaps://ldap.ebay.corp.com:636"
--- End diff --

forget to erase these text before checkin, will modify it, thanks.



> register simple Basic Authentication to server application
> --
>
> Key: EAGLE-582
> URL: https://issues.apache.org/jira/browse/EAGLE-582
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> simple basic authentication with just some expected username-password pairs 
> configured for the application.
> This is one of the sub-tasks of ticket EAGLE-433, to successfully register a 
> simple Basic Authentication authenticator to the server application.
> With this check-in, when the server is up, any access to rest api method that 
> has a @Auth annotation on it's User field will require correct credentials.



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

[GitHub] incubator-eagle pull request #468: [EAGLE-582] add simple Basic Authenticati...

[anyway1021]

Github user anyway1021 commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/468#discussion_r82542185
  
--- Diff: eagle-server/src/main/resources/application.conf ---
@@ -115,4 +115,49 @@ coordinator {
 initDelayMillis = 1000
 delayMillis = 3
   }
+}
+
+# -
+# Eagle Authentication Configuration
+# -
+
+auth {
+  # indicating authentication mode, "simple" or "ldap"
+  mode = simple
+
+  # indicating whether to use cache: cache is usually used for 
authentications that may
+  # not handle high throughput (an RDBMS or LDAP server, for example)
+  cache = false
+
+  # indicating the cache policy, containing maximumSize and 
expireAfterWrite, e.g. maximumSize=1, expireAfterWrite=10m
+  cachePolicy = "maximumSize=1, expireAfterWrite=1m"
+
+  # indicating whether authorization is needed
+  authorize = false
+
+  # indicating whether @Auth annotation on parameters is needed
+  parameter.annotation = true
+
+  # for basic authentication, effective only when auth.mode=simple
+  simple {
+# username for basic authentication, effective only when 
auth.mode=simple
+username = "admin"
+
+# password for basic authentication, effective only when 
auth.mode=simple
+password = "secret"
+  }
+
+  # for ldap authentication, effective only when auth.mode=ldap
+  ldap {
+uri = "ldaps://ldap.ebay.corp.com:636"
--- End diff --

forget to erase these text before checkin, will modify it, thanks.



---
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 #468: [EAGLE-582] add simple Basic Authenticati...

[anyway1021]

Github user anyway1021 commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/468#discussion_r82541902
  
--- Diff: eagle-server/src/main/resources/application.conf ---
@@ -115,4 +115,49 @@ coordinator {
 initDelayMillis = 1000
 delayMillis = 3
   }
+}
+
+# -
+# Eagle Authentication Configuration
+# -
+
+auth {
+  # indicating authentication mode, "simple" or "ldap"
+  mode = simple
+
+  # indicating whether to use cache: cache is usually used for 
authentications that may
+  # not handle high throughput (an RDBMS or LDAP server, for example)
+  cache = false
+
+  # indicating the cache policy, containing maximumSize and 
expireAfterWrite, e.g. maximumSize=1, expireAfterWrite=10m
+  cachePolicy = "maximumSize=1, expireAfterWrite=1m"
+
+  # indicating whether authorization is needed
+  authorize = false
+
+  # indicating whether @Auth annotation on parameters is needed
+  parameter.annotation = true
+
+  # for basic authentication, effective only when auth.mode=simple
+  simple {
+# username for basic authentication, effective only when 
auth.mode=simple
+username = "admin"
+
+# password for basic authentication, effective only when 
auth.mode=simple
+password = "secret"
+  }
+
+  # for ldap authentication, effective only when auth.mode=ldap
+  ldap {
+uri = "ldaps://ldap.ebay.corp.com:636"
+userFilter = "ou=ziwu,dc=ebay,dc=com"
--- End diff --

forget to erase these text before checkin, will modify it, thanks.


---
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] [Reopened] (EAGLE-440) Alert mongodb storage refine

[Su Ralph (JIRA)]

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

Su Ralph reopened EAGLE-440:


> Alert mongodb storage refine
> 
>
> Key: EAGLE-440
> URL: https://issues.apache.org/jira/browse/EAGLE-440
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Currently, some Alert Mongo Collection is too large. Consider future 
> increase, need to split large collection to some small collections.
> To back compatible, need to keep the interface as the same as before. 



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

[GitHub] incubator-eagle pull request #449: EAGLE-545: hdfs/bhase/yarn topology healt...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-545) hdfs/bhase/yarn health check

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-545:
--

Github user asfgit closed the pull request at:

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


> hdfs/bhase/yarn health check 
> -
>
> Key: EAGLE-545
> URL: https://issues.apache.org/jira/browse/EAGLE-545
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> * HDFS: namenode, datanode, journalnode
> * HBASE: hmaster, regionservers
> * YARN: resourcemanager, nodemanagers, historyserver
> More detailed requirements:
> 1. provides node level health diagnosis including the master nodes and slave 
> nodes
> 2. provide several cluster-level metrics



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

[jira] [Updated] (EAGLE-519) No data / gap alert enhancement

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-519:
---
Description: 
1. no data for an entire stream won't trigger gap alert (use local time & batch 
window) 
2. no data policies definition is too complex, make the nodata offer optional 
settings in stream definition 
3. bolt parallellism will cause multiple alerts in the same time window (use 
loopback) 

The extension of no data alert design is posted at 
https://cwiki.apache.org/confluence/display/EAG/Alert+Engine+Extension.

  was:
1. no data for an entire stream won't trigger gap alert (use local time & batch 
window) 
2. no data policies definition is too complex, make the nodata offer optional 
settings in stream definition 
3. bolt parallellism will cause multiple alerts in the same time window (use 
loopback) 



> No data / gap alert enhancement
> ---
>
> Key: EAGLE-519
> URL: https://issues.apache.org/jira/browse/EAGLE-519
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> 1. no data for an entire stream won't trigger gap alert (use local time & 
> batch window) 
> 2. no data policies definition is too complex, make the nodata offer optional 
> settings in stream definition 
> 3. bolt parallellism will cause multiple alerts in the same time window (use 
> loopback) 
> The extension of no data alert design is posted at 
> https://cwiki.apache.org/confluence/display/EAG/Alert+Engine+Extension.



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

[jira] [Updated] (EAGLE-531) Dedup alerts according to state change

[Garrett Li (JIRA)]

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

Garrett Li updated EAGLE-531:
-
Description: 
Currently the dedup is only for specified fields dedup, it cannot support dedup 
the alert according to dedup fields along with one specific field value changes 
(such as state change). This change is support both cases.

If only specified fields for dedup, we will according to specified fields and 
duration time to filter duplicated alerts.
If specified state field along with dedup fields, we will check state filed 
value change to filter duplicated alerts.

  was:This is for stateful and stateless logs


> Dedup alerts according to state change
> --
>
> Key: EAGLE-531
> URL: https://issues.apache.org/jira/browse/EAGLE-531
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Currently the dedup is only for specified fields dedup, it cannot support 
> dedup the alert according to dedup fields along with one specific field value 
> changes (such as state change). This change is support both cases.
> If only specified fields for dedup, we will according to specified fields and 
> duration time to filter duplicated alerts.
> If specified state field along with dedup fields, we will check state filed 
> value change to filter duplicated alerts.



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

[jira] [Closed] (EAGLE-564) pack mr history/running feeder in one topology and bugs fix

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-564.
-
Resolution: Fixed

> pack mr history/running feeder in one topology and bugs fix
> ---
>
> Key: EAGLE-564
> URL: https://issues.apache.org/jira/browse/EAGLE-564
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> Pack MR history/Running feeder in the final topology by using 
> topology-assembly. 
> Changes:
> 1. remove useless configure
> 2. add application provider to topology assembly spi
> Bug fix:
> 1. Storm configure(workers/timeout...) does not overrided by customer defined 
> configure.
> 2. When install an application, user may not set jarPath, in this case, we 
> need to dynamic load, otherwise, use the jarPath that user provides.



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

[jira] [Updated] (EAGLE-544) Enhance dedup to support extended deduplicator

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-544:
---
Description: 
The deduplicator configuration in publishment metadata is not configurable.

To provide extensibility, need to make deduplicator configurable also provide 
base interface/class for service provide to plugin.
Add "overrideDeduplicator" in publishment.


  was:
The deduplicator configuration in publishment metadata is not configurable.

To provide extensibility, need to make deduplicator configurable also provide 
base interface/class for service provide to plugin.



> Enhance dedup to support extended deduplicator
> --
>
> Key: EAGLE-544
> URL: https://issues.apache.org/jira/browse/EAGLE-544
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> The deduplicator configuration in publishment metadata is not configurable.
> To provide extensibility, need to make deduplicator configurable also provide 
> base interface/class for service provide to plugin.
> Add "overrideDeduplicator" in publishment.



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

[jira] [Resolved] (EAGLE-544) Enhance dedup to support extended deduplicator

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-544.

Resolution: Fixed

> Enhance dedup to support extended deduplicator
> --
>
> Key: EAGLE-544
> URL: https://issues.apache.org/jira/browse/EAGLE-544
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> The deduplicator configuration in publishment metadata is not configurable.
> To provide extensibility, need to make deduplicator configurable also provide 
> base interface/class for service provide to plugin.



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

[jira] [Updated] (EAGLE-544) Enhance dedup to support extended deduplicator

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-544:
---
Description: 
The deduplicator configuration in publishment metadata is not configurable.

To provide extensibility, need to make deduplicator configurable also provide 
base interface/class for service provide to plugin.


> Enhance dedup to support extended deduplicator
> --
>
> Key: EAGLE-544
> URL: https://issues.apache.org/jira/browse/EAGLE-544
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> The deduplicator configuration in publishment metadata is not configurable.
> To provide extensibility, need to make deduplicator configurable also provide 
> base interface/class for service provide to plugin.



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

[jira] [Closed] (EAGLE-345) add "apache-" as a prefix of finalName in eagle-assembly's pom and remove -snapshot in versions

[Michael Wu (JIRA)]

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

Michael Wu closed EAGLE-345.

Resolution: Fixed

> add "apache-" as a prefix of finalName in eagle-assembly's pom and remove 
> -snapshot in versions
> ---
>
> Key: EAGLE-345
> URL: https://issues.apache.org/jira/browse/EAGLE-345
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>Priority: Minor
>
> a prefix "apache-" is omitted in the final name, add it to pom.xml of the 
> project



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

[jira] [Commented] (EAGLE-593) Eagle Topology assembly multi-version Hadoop support & bug fix

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-593:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-593] Eagle Topology assembly multi-version Hadoop support & bug fix

1. User may want to support different version of hadoop in eagle jpm when 
uses topology asembly to be a final package. For this requirement, we add 
profiles to eagle-topology-assembly pom.xml. In this pom, we could add 
different versions of Hadoop.
2. Fix StormSubmitter does not support submit another jar
In storm StormSubmitter

--
private static String submittedJar = null;
private static void submitJar(Map conf, ProgressListener listener) {
if(submittedJar==null)
{ LOG.info("Jar not uploaded to master yet. Submitting jar..."); String 
localJar = System.getProperty("storm.jar"); submittedJar = submitJar(conf, 
localJar, listener); }
else
{ LOG.info("Jar already uploaded to master. Not submitting jar."); }
}

--
It can not submit another jar once submittedJar is set.
So I rewrote this class.
3. Fix MR Running Job that does not set finished jobs' state

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

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

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

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


commit ddaf662a5d7df4ae40c88871f17d2efb0a8157ab
Author: wujinhu 
Date:   2016-10-10T02:27:59Z

Eagle Topology assembly multi-version Hadoop support & bug fix

commit 52e73185155c42af3ecebc8ee0ba09ca3cb39840
Author: wujinhu 
Date:   2016-10-10T02:31:31Z

Eagle Topology assembly multi-version Hadoop support & bug fix




> Eagle Topology assembly multi-version Hadoop support & bug fix
> --
>
> Key: EAGLE-593
> URL: https://issues.apache.org/jira/browse/EAGLE-593
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. User may want to support different version of hadoop in eagle jpm when 
> uses topology asembly to be a final package. For this requirement, we add 
> profiles to eagle-topology-assembly pom.xml. In this pom, we could add 
> different versions of Hadoop.
> 2. Fix StormSubmitter does not support submit another jar
> In storm StormSubmitter
> --
> private static String submittedJar = null;
> private static void submitJar(Map conf, ProgressListener listener) {
> if(submittedJar==null) {
> LOG.info("Jar not uploaded to master yet. Submitting jar...");
> String localJar = System.getProperty("storm.jar");
> submittedJar = submitJar(conf, localJar, listener);
> } else {
> LOG.info("Jar already uploaded to master. Not submitting jar.");
> }
> }
> --
> It can not submit another jar once submittedJar is set.
> So I rewrote this class.
> 3. Fix MR Running Job that does not set finished jobs' state



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

[GitHub] incubator-eagle pull request #481: [EAGLE-593] Eagle Topology assembly multi...

[wujinhu]

GitHub user wujinhu opened a pull request:

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

[EAGLE-593] Eagle Topology assembly multi-version Hadoop support & bug fix

1. User may want to support different version of hadoop in eagle jpm when 
uses topology asembly to be a final package. For this requirement, we add 
profiles to eagle-topology-assembly pom.xml. In this pom, we could add 
different versions of Hadoop.
2. Fix StormSubmitter does not support submit another jar
In storm StormSubmitter

--
private static String submittedJar = null;
private static void submitJar(Map conf, ProgressListener listener) {
if(submittedJar==null)
{ LOG.info("Jar not uploaded to master yet. Submitting jar..."); String 
localJar = System.getProperty("storm.jar"); submittedJar = submitJar(conf, 
localJar, listener); }
else
{ LOG.info("Jar already uploaded to master. Not submitting jar."); }
}

--
It can not submit another jar once submittedJar is set.
So I rewrote this class.
3. Fix MR Running Job that does not set finished jobs' state

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

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

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

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


commit ddaf662a5d7df4ae40c88871f17d2efb0a8157ab
Author: wujinhu 
Date:   2016-10-10T02:27:59Z

Eagle Topology assembly multi-version Hadoop support & bug fix

commit 52e73185155c42af3ecebc8ee0ba09ca3cb39840
Author: wujinhu 
Date:   2016-10-10T02:31:31Z

Eagle Topology assembly multi-version Hadoop support & bug fix




---
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-345) add "apache-" as a prefix of finalName in eagle-assembly's pom and remove -snapshot in versions

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-345:
-
Description: a prefix "apache-" is omitted in the final name, add it to 
pom.xml of the project

> add "apache-" as a prefix of finalName in eagle-assembly's pom and remove 
> -snapshot in versions
> ---
>
> Key: EAGLE-345
> URL: https://issues.apache.org/jira/browse/EAGLE-345
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>Priority: Minor
>
> a prefix "apache-" is omitted in the final name, add it to pom.xml of the 
> project



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

[jira] [Reopened] (EAGLE-345) add "apache-" as a prefix of finalName in eagle-assembly's pom and remove -snapshot in versions

[Michael Wu (JIRA)]

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

Michael Wu reopened EAGLE-345:
--

add description

> add "apache-" as a prefix of finalName in eagle-assembly's pom and remove 
> -snapshot in versions
> ---
>
> Key: EAGLE-345
> URL: https://issues.apache.org/jira/browse/EAGLE-345
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>Priority: Minor
>




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

[jira] [Updated] (EAGLE-593) Eagle Topology assembly multi-version Hadoop support & bug fix

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-593:
--
Description: 
1. User may want to support different version of hadoop in eagle jpm when uses 
topology asembly to be a final package. For this requirement, we add profiles 
to eagle-topology-assembly pom.xml. In this pom, we could add different 
versions of Hadoop.
2. Fix StormSubmitter does not support submit another jar
In storm StormSubmitter
--
private static String submittedJar = null;
private static void submitJar(Map conf, ProgressListener listener) {
if(submittedJar==null) {
LOG.info("Jar not uploaded to master yet. Submitting jar...");
String localJar = System.getProperty("storm.jar");
submittedJar = submitJar(conf, localJar, listener);
} else {
LOG.info("Jar already uploaded to master. Not submitting jar.");
}
}
--
It can not submit another jar once submittedJar is set.
So I rewrote this class.
3. Fix MR Running Job that does not set finished jobs' state


  was:User may want to support different version of hadoop in eagle jpm. For 
this requirement, we add profiles to eagle-jpm pom.xml. In this pom, we could 
add different versions of Hadoop.


> Eagle Topology assembly multi-version Hadoop support & bug fix
> --
>
> Key: EAGLE-593
> URL: https://issues.apache.org/jira/browse/EAGLE-593
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. User may want to support different version of hadoop in eagle jpm when 
> uses topology asembly to be a final package. For this requirement, we add 
> profiles to eagle-topology-assembly pom.xml. In this pom, we could add 
> different versions of Hadoop.
> 2. Fix StormSubmitter does not support submit another jar
> In storm StormSubmitter
> --
> private static String submittedJar = null;
> private static void submitJar(Map conf, ProgressListener listener) {
> if(submittedJar==null) {
> LOG.info("Jar not uploaded to master yet. Submitting jar...");
> String localJar = System.getProperty("storm.jar");
> submittedJar = submitJar(conf, localJar, listener);
> } else {
> LOG.info("Jar already uploaded to master. Not submitting jar.");
> }
> }
> --
> It can not submit another jar once submittedJar is set.
> So I rewrote this class.
> 3. Fix MR Running Job that does not set finished jobs' state



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

[jira] [Closed] (EAGLE-406) Add develop branch CI build status to README.md

[Michael Wu (JIRA)]

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

Michael Wu closed EAGLE-406.

Resolution: Fixed

> Add develop branch CI build status to README.md
> ---
>
> Key: EAGLE-406
> URL: https://issues.apache.org/jira/browse/EAGLE-406
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> we'd like to show CI build status in the project's README.md file, determined 
> to use jenkins plugin to make it.



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

[jira] [Updated] (EAGLE-406) Add develop branch CI build status to README.md

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-406:
-
Description: we'd like to show CI build status in the project's README.md 
file, determined to use jenkins plugin to make it.

> Add develop branch CI build status to README.md
> ---
>
> Key: EAGLE-406
> URL: https://issues.apache.org/jira/browse/EAGLE-406
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> we'd like to show CI build status in the project's README.md file, determined 
> to use jenkins plugin to make it.



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

[jira] [Reopened] (EAGLE-406) Add develop branch CI build status to README.md

[Michael Wu (JIRA)]

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

Michael Wu reopened EAGLE-406:
--

adding description to it

> Add develop branch CI build status to README.md
> ---
>
> Key: EAGLE-406
> URL: https://issues.apache.org/jira/browse/EAGLE-406
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>




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

[jira] [Deleted] (EAGLE-523) fix eagle's javadoc error complained by jdk1.8

[Michael Wu (JIRA)]

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

Michael Wu deleted EAGLE-523:
-


> fix eagle's javadoc error complained by jdk1.8
> --
>
> Key: EAGLE-523
> URL: https://issues.apache.org/jira/browse/EAGLE-523
> Project: Eagle
>  Issue Type: Bug
>Reporter: Michael Wu
>Assignee: Michael Wu
>




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

[jira] [Updated] (EAGLE-439) Introduce policy enable/disable support

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-439:
---
Description: 
Introduce policy enable/disable support.

Suggestion:
Add policyStatus field in policy definition. With value of "ENABLED" and 
"DISABLED".
For DISABLED policy, the coordinator will exclude the policy with DISABLED 
status.

  was:Introduce policy enable/disable support


> Introduce policy enable/disable support
> ---
>
> Key: EAGLE-439
> URL: https://issues.apache.org/jira/browse/EAGLE-439
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.4.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>  Labels: alert-engine
> Fix For: v0.5.0
>
>
> Introduce policy enable/disable support.
> Suggestion:
> Add policyStatus field in policy definition. With value of "ENABLED" and 
> "DISABLED".
> For DISABLED policy, the coordinator will exclude the policy with DISABLED 
> status.



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

[jira] [Updated] (EAGLE-322) setup Buildbot configuration for eagle documentation

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-322:
-
Description: add configuration for Buildbot to auto-build for the project

> setup Buildbot configuration for eagle documentation
> 
>
> Key: EAGLE-322
> URL: https://issues.apache.org/jira/browse/EAGLE-322
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>Priority: Minor
>
> add configuration for Buildbot to auto-build for the project



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

[jira] [Updated] (EAGLE-300) Disable spring debug log by default in webservice

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-300:
-
Description: there are tons of "debug" logs output by spring framework, log 
rules should be modified to hide such debug logs so that more valuable logs can 
be found more easily.

> Disable spring debug log by default in webservice
> -
>
> Key: EAGLE-300
> URL: https://issues.apache.org/jira/browse/EAGLE-300
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0, v0.3.1
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.4.0
>
>
> there are tons of "debug" logs output by spring framework, log rules should 
> be modified to hide such debug logs so that more valuable logs can be found 
> more easily.



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

[jira] [Closed] (EAGLE-300) Disable spring debug log by default in webservice

[Michael Wu (JIRA)]

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

Michael Wu closed EAGLE-300.

Resolution: Fixed

> Disable spring debug log by default in webservice
> -
>
> Key: EAGLE-300
> URL: https://issues.apache.org/jira/browse/EAGLE-300
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0, v0.3.1
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.4.0
>
>
> there are tons of "debug" logs output by spring framework, log rules should 
> be modified to hide such debug logs so that more valuable logs can be found 
> more easily.



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

[jira] [Updated] (EAGLE-243) Set up Eagle IT (Integration Test) Suite

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-243:
-
Description: setup a integration test CI for eagle

> Set up Eagle IT (Integration Test) Suite 
> -
>
> Key: EAGLE-243
> URL: https://issues.apache.org/jira/browse/EAGLE-243
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> setup a integration test CI for eagle



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

[jira] [Updated] (EAGLE-234) Clean maven build warning in eagle

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-234:
-
Description: clean warnings thrown out while compiling the project

> Clean maven build warning in eagle
> --
>
> Key: EAGLE-234
> URL: https://issues.apache.org/jira/browse/EAGLE-234
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Hao Chen
>Assignee: Michael Wu
>  Labels: new
> Fix For: v0.5.0
>
>
> clean warnings thrown out while compiling the project



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

[jira] [Updated] (EAGLE-134) publish javadoc of eagle

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-134:
-
Description: try to find a way to publish javadoc

> publish javadoc of eagle
> 
>
> Key: EAGLE-134
> URL: https://issues.apache.org/jira/browse/EAGLE-134
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Michael Wu
>Assignee: Michael Wu
>Priority: Minor
> Fix For: v0.5.0
>
>
> try to find a way to publish javadoc



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

[jira] [Updated] (EAGLE-365) Fix found issues of 0.4.0-incubating-rc2 and create rc3

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-365:
-
Description: remove tomcat related jar dependencies in the project

> Fix found issues of 0.4.0-incubating-rc2 and create rc3
> ---
>
> Key: EAGLE-365
> URL: https://issues.apache.org/jira/browse/EAGLE-365
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> remove tomcat related jar dependencies in the project



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

[jira] [Closed] (EAGLE-365) Fix found issues of 0.4.0-incubating-rc2 and create rc3

[Michael Wu (JIRA)]

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

Michael Wu closed EAGLE-365.

Resolution: Fixed

> Fix found issues of 0.4.0-incubating-rc2 and create rc3
> ---
>
> Key: EAGLE-365
> URL: https://issues.apache.org/jira/browse/EAGLE-365
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> remove tomcat related jar dependencies in the project



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

[jira] [Updated] (EAGLE-593) Eagle Topology assembly multi-version Hadoop support & bug fix

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-593:
--
Summary: Eagle Topology assembly multi-version Hadoop support & bug fix  
(was: Eagle JPM multi-version Hadoop support)

> Eagle Topology assembly multi-version Hadoop support & bug fix
> --
>
> Key: EAGLE-593
> URL: https://issues.apache.org/jira/browse/EAGLE-593
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> User may want to support different version of hadoop in eagle jpm. For this 
> requirement, we add profiles to eagle-jpm pom.xml. In this pom, we could add 
> different versions of Hadoop.



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

[jira] [Resolved] (EAGLE-597) Add API to filter publishment by policy: /policies/{policyId}/publishments

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-597.

Resolution: Fixed

Merged to master in 
https://github.com/apache/incubator-eagle/commit/8ba1b844cdb9e165844896b526631eec5a1b64aa

> Add API to filter publishment by policy: /policies/{policyId}/publishments
> --
>
> Key: EAGLE-597
> URL: https://issues.apache.org/jira/browse/EAGLE-597
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: alert-engine, alert-service
> Fix For: v0.5.0
>
>
> Alert engine publishments API only support to provide all publishments and 
> let client-side to filter according requirements, which is NOT an scalable 
> implementation. 
> As a quick solution to fix it in some way, we should provide a API to filter 
> publishments by policy ID, so in this patch it mainly added two APIs:
> * GET /policies/\{policyId\}
> * GET /policies/\{policyId\}/publishments



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

[jira] [Commented] (EAGLE-597) Add API to filter publishment by policy: /policies/{policyId}/publishments

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-597:
--

Github user asfgit closed the pull request at:

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


> Add API to filter publishment by policy: /policies/{policyId}/publishments
> --
>
> Key: EAGLE-597
> URL: https://issues.apache.org/jira/browse/EAGLE-597
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: alert-engine, alert-service
> Fix For: v0.5.0
>
>
> Alert engine publishments API only support to provide all publishments and 
> let client-side to filter according requirements, which is NOT an scalable 
> implementation. 
> As a quick solution to fix it in some way, we should provide a API to filter 
> publishments by policy ID, so in this patch it mainly added two APIs:
> * GET /policies/\{policyId\}
> * GET /policies/\{policyId\}/publishments



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

[GitHub] incubator-eagle pull request #480: [EAGLE-597] Add API to filter publishment...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-597) Add API to filter publishment by policy: /policies/{policyId}/publishments

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-597:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/480
  
It's a simple patch adding a few features, and passed CI, so will merge.


> Add API to filter publishment by policy: /policies/{policyId}/publishments
> --
>
> Key: EAGLE-597
> URL: https://issues.apache.org/jira/browse/EAGLE-597
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: alert-engine, alert-service
> Fix For: v0.5.0
>
>
> Alert engine publishments API only support to provide all publishments and 
> let client-side to filter according requirements, which is NOT an scalable 
> implementation. 
> As a quick solution to fix it in some way, we should provide a API to filter 
> publishments by policy ID, so in this patch it mainly added two APIs:
> * GET /policies/\{policyId\}
> * GET /policies/\{policyId\}/publishments



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

[GitHub] incubator-eagle issue #480: [EAGLE-597] Add API to filter publishment and si...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/480
  
It's a simple patch adding a few features, and passed CI, so will merge.


---
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-435) Coordiantor schedule operation must be exclusive in distributed deployment

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-435:
---
Description: 
Coordiantor schedule operation must be exclusive in distributed deployment

This is critical for ha-mode deploy of coordinator. We don't want to have 
coordinator concurrently build the specs.

  was:Coordiantor schedule operation must be exclusive in distributed deployment


> Coordiantor schedule operation must be exclusive in distributed deployment
> --
>
> Key: EAGLE-435
> URL: https://issues.apache.org/jira/browse/EAGLE-435
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
>  Labels: alert_engine
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Coordiantor schedule operation must be exclusive in distributed deployment
> This is critical for ha-mode deploy of coordinator. We don't want to have 
> coordinator concurrently build the specs.



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

[GitHub] incubator-eagle pull request #480: Add API to filter publishment and single ...

[haoch]

GitHub user haoch opened a pull request:

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

Add API to filter publishment and single policy metadata by policyId

Alert engine publishments API only support to provide all publishments and 
let client-side to filter according requirements, which is NOT an scalable 
implementation.

As a quick solution to fix it in some way, we should provide a API to 
filter publishments by policy ID, so in this patch it mainly added two APIs:

* GET /policies/{policyId}
* GET /policies/{policyId}/publishments


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

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

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

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


commit 931a34eb30c125480f0aaf85a47c1002d813b707
Author: Hao Chen 
Date:   2016-10-09T10:52:20Z

Add API to filter publishment by policy: /policies/{policyId}/publishments




---
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-597) Add API to filter publishment by policy: /policies/{policyId}/publishments

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-597:
---
Affects Version/s: v0.5.0

> Add API to filter publishment by policy: /policies/{policyId}/publishments
> --
>
> Key: EAGLE-597
> URL: https://issues.apache.org/jira/browse/EAGLE-597
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: alert-engine, alert-service
> Fix For: v0.5.0
>
>
> Alert engine publishments API only support to provide all publishments and 
> let client-side to filter according requirements, which is NOT an scalable 
> implementation. 
> As a quick solution to fix it in some way, we should provide a API to filter 
> publishments by policy ID, so in this patch it mainly added two APIs:
> * GET /policies/\{policyId\}
> * GET /policies/\{policyId\}/publishments



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

[jira] [Updated] (EAGLE-597) Add API to filter publishment by policy: /policies/{policyId}/publishments

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-597:
---
Labels: alert-engine alert-service  (was: )

> Add API to filter publishment by policy: /policies/{policyId}/publishments
> --
>
> Key: EAGLE-597
> URL: https://issues.apache.org/jira/browse/EAGLE-597
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: alert-engine, alert-service
> Fix For: v0.5.0
>
>
> Alert engine publishments API only support to provide all publishments and 
> let client-side to filter according requirements, which is NOT an scalable 
> implementation. 
> As a quick solution to fix it in some way, we should provide a API to filter 
> publishments by policy ID, so in this patch it mainly added two APIs:
> * GET /policies/\{policyId\}
> * GET /policies/\{policyId\}/publishments



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

[jira] [Updated] (EAGLE-597) Add API to filter publishment by policy: /policies/{policyId}/publishments

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-597:
---
Fix Version/s: v0.5.0

> Add API to filter publishment by policy: /policies/{policyId}/publishments
> --
>
> Key: EAGLE-597
> URL: https://issues.apache.org/jira/browse/EAGLE-597
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: alert-engine, alert-service
> Fix For: v0.5.0
>
>
> Alert engine publishments API only support to provide all publishments and 
> let client-side to filter according requirements, which is NOT an scalable 
> implementation. 
> As a quick solution to fix it in some way, we should provide a API to filter 
> publishments by policy ID, so in this patch it mainly added two APIs:
> * GET /policies/\{policyId\}
> * GET /policies/\{policyId\}/publishments



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

[jira] [Updated] (EAGLE-597) Add API to filter publishment by policy: /policies/{policyId}/publishments

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-597:
---
Description: 
Alert engine publishments API only support to provide all publishments and let 
client-side to filter according requirements, which is NOT an scalable 
implementation. 

As a quick solution to fix it in some way, we should provide a API to filter 
publishments by policy ID, so in this patch it mainly added two APIs:
* GET /policies/\{policyId\}
* GET /policies/\{policyId\}/publishments

  was:
Alert engine publishments API only support to provide all publishments and let 
client-side to filter according requirements, which is NOT an scalable 
implementation. 

As a quick solution to fix it in some way, we should provide a API to filter 
publishments by policy ID, so in this patch it mainly added two APIs:
* GET /policies/{policyId}
* GET /policies/{policyId}/publishments


> Add API to filter publishment by policy: /policies/{policyId}/publishments
> --
>
> Key: EAGLE-597
> URL: https://issues.apache.org/jira/browse/EAGLE-597
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: alert-engine, alert-service
> Fix For: v0.5.0
>
>
> Alert engine publishments API only support to provide all publishments and 
> let client-side to filter according requirements, which is NOT an scalable 
> implementation. 
> As a quick solution to fix it in some way, we should provide a API to filter 
> publishments by policy ID, so in this patch it mainly added two APIs:
> * GET /policies/\{policyId\}
> * GET /policies/\{policyId\}/publishments



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

[jira] [Updated] (EAGLE-597) Add API to filter publishment by policy: /policies/{policyId}/publishments

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-597:
---
Description: 
Alert engine publishments API only support to provide all publishments and let 
client-side to filter according requirements, which is NOT an scalable 
implementation. 

As a quick solution to fix it in some way, we should provide a API to filter 
publishments by policy ID, so in this patch it mainly added two APIs:
* GET /policies/{policyId}
* GET /policies/{policyId}/publishments

  was:
Alert engine publishments API only support to provide all publishments and let 
client-side to filter according requirements, which is NOT an scalable 
implementation. 

As a quick solution to fix it in some way, we should provide a API to filter 
publishments by policy ID


> Add API to filter publishment by policy: /policies/{policyId}/publishments
> --
>
> Key: EAGLE-597
> URL: https://issues.apache.org/jira/browse/EAGLE-597
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> Alert engine publishments API only support to provide all publishments and 
> let client-side to filter according requirements, which is NOT an scalable 
> implementation. 
> As a quick solution to fix it in some way, we should provide a API to filter 
> publishments by policy ID, so in this patch it mainly added two APIs:
> * GET /policies/{policyId}
> * GET /policies/{policyId}/publishments



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

[jira] [Updated] (EAGLE-597) Add API to filter publishment by policy: /policies/{policyId}/publishments

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-597:
---
Summary: Add API to filter publishment by policy: 
/policies/{policyId}/publishments  (was: Add API to filter publishment by 
policy)

> Add API to filter publishment by policy: /policies/{policyId}/publishments
> --
>
> Key: EAGLE-597
> URL: https://issues.apache.org/jira/browse/EAGLE-597
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> Alert engine publishments API only support to provide all publishments and 
> let client-side to filter according requirements, which is NOT an scalable 
> implementation. 
> As a quick solution to fix it in some way, we should provide a API to filter 
> publishments by policy ID



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

[jira] [Created] (EAGLE-597) Add API to filter publishment by policy

[Hao Chen (JIRA)]

Hao Chen created EAGLE-597:
--

 Summary: Add API to filter publishment by policy
 Key: EAGLE-597
 URL: https://issues.apache.org/jira/browse/EAGLE-597
 Project: Eagle
  Issue Type: Bug
Reporter: Hao Chen
Assignee: Hao Chen


Alert engine publishments API only support to provide all publishments and let 
client-side to filter according requirements, which is NOT an scalable 
implementation. 

As a quick solution to fix it in some way, we should provide a API to filter 
publishments by policy ID



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

[jira] [Updated] (EAGLE-596) Caught NoSuchFieldError when creating policy with existing policyId

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-596:
---
Labels: alert-engine alert-service metadata  (was: alert-engine metadata 
webservice)

> Caught NoSuchFieldError when creating policy with existing policyId
> ---
>
> Key: EAGLE-596
> URL: https://issues.apache.org/jira/browse/EAGLE-596
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.5
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
>  Labels: alert-engine, alert-service, metadata
> Fix For: v0.5.0
>
>
> h2. Sample Data
> {code}
> {"name":"Mock","description":"asdadsasd","inputStreams":["hbase_audit_log_stream"],"outputStreams":["hbase_audit_log_stream"],"definition":{"type":"siddhi","value":"test","handlerClass":null,"properties":{},"inputStreams":[],"outputStreams":[]},"partitionSpec":[],"parallelismHint":2}
> {code}
> h2. NoSuchFieldError
> {code}
> WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: 
> Error for /rest/metadata/policies
> ! java.lang.NoSuchFieldError: _nullProvider
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
>  ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
> ~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
> ! at 
> io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> 

[jira] [Updated] (EAGLE-596) Caught NoSuchFieldError when creating policy with existing policyId

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-596:
---
Fix Version/s: v0.5.0

> Caught NoSuchFieldError when creating policy with existing policyId
> ---
>
> Key: EAGLE-596
> URL: https://issues.apache.org/jira/browse/EAGLE-596
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.5
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
>  Labels: alert-engine, metadata, webservice
> Fix For: v0.5.0
>
>
> h2. Sample Data
> {code}
> {"name":"Mock","description":"asdadsasd","inputStreams":["hbase_audit_log_stream"],"outputStreams":["hbase_audit_log_stream"],"definition":{"type":"siddhi","value":"test","handlerClass":null,"properties":{},"inputStreams":[],"outputStreams":[]},"partitionSpec":[],"parallelismHint":2}
> {code}
> h2. NoSuchFieldError
> {code}
> WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: 
> Error for /rest/metadata/policies
> ! java.lang.NoSuchFieldError: _nullProvider
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
>  ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
> ~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
> ! at 
> io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> 

[jira] [Updated] (EAGLE-596) Caught NoSuchFieldError when creating policy with existing policyId

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-596:
---
Labels: metadata webservice  (was: metadata)

> Caught NoSuchFieldError when creating policy with existing policyId
> ---
>
> Key: EAGLE-596
> URL: https://issues.apache.org/jira/browse/EAGLE-596
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.5
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
>  Labels: alert-engine, metadata, webservice
> Fix For: v0.5.0
>
>
> h2. Sample Data
> {code}
> {"name":"Mock","description":"asdadsasd","inputStreams":["hbase_audit_log_stream"],"outputStreams":["hbase_audit_log_stream"],"definition":{"type":"siddhi","value":"test","handlerClass":null,"properties":{},"inputStreams":[],"outputStreams":[]},"partitionSpec":[],"parallelismHint":2}
> {code}
> h2. NoSuchFieldError
> {code}
> WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: 
> Error for /rest/metadata/policies
> ! java.lang.NoSuchFieldError: _nullProvider
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
>  ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
> ~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
> ! at 
> io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> 

[jira] [Updated] (EAGLE-596) Caught NoSuchFieldError when creating policy with existing policyId

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-596:
---
Labels: alert-engine metadata webservice  (was: metadata webservice)

> Caught NoSuchFieldError when creating policy with existing policyId
> ---
>
> Key: EAGLE-596
> URL: https://issues.apache.org/jira/browse/EAGLE-596
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.5
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
>  Labels: alert-engine, metadata, webservice
> Fix For: v0.5.0
>
>
> h2. Sample Data
> {code}
> {"name":"Mock","description":"asdadsasd","inputStreams":["hbase_audit_log_stream"],"outputStreams":["hbase_audit_log_stream"],"definition":{"type":"siddhi","value":"test","handlerClass":null,"properties":{},"inputStreams":[],"outputStreams":[]},"partitionSpec":[],"parallelismHint":2}
> {code}
> h2. NoSuchFieldError
> {code}
> WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: 
> Error for /rest/metadata/policies
> ! java.lang.NoSuchFieldError: _nullProvider
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
>  ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
> ~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
> ! at 
> io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> 

[jira] [Updated] (EAGLE-596) Caught NoSuchFieldError when creating policy with existing policyId

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-596:
---
Summary: Caught NoSuchFieldError when creating policy with existing 
policyId  (was: Got NoSuchFieldError when creating policy with existing 
policyId)

> Caught NoSuchFieldError when creating policy with existing policyId
> ---
>
> Key: EAGLE-596
> URL: https://issues.apache.org/jira/browse/EAGLE-596
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.5
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
>
> h2. Sample Data
> {code}
> {"name":"Mock","description":"asdadsasd","inputStreams":["hbase_audit_log_stream"],"outputStreams":["hbase_audit_log_stream"],"definition":{"type":"siddhi","value":"test","handlerClass":null,"properties":{},"inputStreams":[],"outputStreams":[]},"partitionSpec":[],"parallelismHint":2}
> {code}
> h2. NoSuchFieldError
> {code}
> WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: 
> Error for /rest/metadata/policies
> ! java.lang.NoSuchFieldError: _nullProvider
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
>  ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
> ~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
> ! at 
> io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> 

[jira] [Resolved] (EAGLE-567) Enhance Slack publish format

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-567.

Resolution: Fixed

> Enhance Slack publish format
> 
>
> Key: EAGLE-567
> URL: https://issues.apache.org/jira/browse/EAGLE-567
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Currently message publish to Slack is raw String, and this is not very clear 
> for user.
> So need to add format for it for better viewing.



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

[jira] [Updated] (EAGLE-596) Got NoSuchFieldError when creating policy with existing policyId

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-596:
---
Summary: Got NoSuchFieldError when creating policy with existing policyId  
(was: Got NoSuchFieldError when create policy with existing policyId)

> Got NoSuchFieldError when creating policy with existing policyId
> 
>
> Key: EAGLE-596
> URL: https://issues.apache.org/jira/browse/EAGLE-596
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.5
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
>
> h2. Sample Data
> {code}
> {"name":"Mock","description":"asdadsasd","inputStreams":["hbase_audit_log_stream"],"outputStreams":["hbase_audit_log_stream"],"definition":{"type":"siddhi","value":"test","handlerClass":null,"properties":{},"inputStreams":[],"outputStreams":[]},"partitionSpec":[],"parallelismHint":2}
> {code}
> h2. NoSuchFieldError
> {code}
> WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: 
> Error for /rest/metadata/policies
> ! java.lang.NoSuchFieldError: _nullProvider
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
>  ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
> ~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
> ! at 
> io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> 

[jira] [Commented] (EAGLE-567) Enhance Slack publish format

[Su Ralph (JIRA)]

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

Su Ralph commented on EAGLE-567:


Link to https://issues.apache.org/jira/browse/EAGLE-570 which is the further 
enhancement on the publishment change.

> Enhance Slack publish format
> 
>
> Key: EAGLE-567
> URL: https://issues.apache.org/jira/browse/EAGLE-567
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Currently message publish to Slack is raw String, and this is not very clear 
> for user.
> So need to add format for it for better viewing.



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

[jira] [Updated] (EAGLE-596) Got NoSuchFieldError when create policy with existing policyId

[Jilin, Jiang (JIRA)]

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

Jilin, Jiang updated EAGLE-596:
---
Description: 
Post:
{"name":"Mock","description":"asdadsasd","inputStreams":["hbase_audit_log_stream"],"outputStreams":["hbase_audit_log_stream"],"definition":{"type":"siddhi","value":"test","handlerClass":null,"properties":{},"inputStreams":[],"outputStreams":[]},"partitionSpec":[],"parallelismHint":2}


h2. Exception

{code}
WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: Error 
for /rest/metadata/policies
! java.lang.NoSuchFieldError: _nullProvider
! at 
com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
 ~[jackson-databind-2.6.6.jar:2.6.6]
! at 
com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
~[jackson-databind-2.6.6.jar:2.6.6]
! at 
com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
~[jackson-databind-2.6.6.jar:2.6.6]
! at 
com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
! at 
io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
 ~[dropwizard-jersey-0.7.1.jar:0.7.1]
! at 
com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
 ~[dropwizard-jersey-0.7.1.jar:0.7.1]
! at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 

[jira] [Commented] (EAGLE-567) Enhance Slack publish format

[Su Ralph (JIRA)]

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

Su Ralph commented on EAGLE-567:


```from pr

The ticket is aim to enhance the format of slack publishment of Alert. The 
original message was just a raw string which is not clear for user. Add more 
format such as color for better viewing.


> Enhance Slack publish format
> 
>
> Key: EAGLE-567
> URL: https://issues.apache.org/jira/browse/EAGLE-567
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Currently message publish to Slack is raw String, and this is not very clear 
> for user.
> So need to add format for it for better viewing.



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

[jira] [Updated] (EAGLE-596) Got NoSuchFieldError when create policy with existing policyId

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-596:
---
Summary: Got NoSuchFieldError when create policy with existing policyId  
(was: Got Create policy error)

> Got NoSuchFieldError when create policy with existing policyId
> --
>
> Key: EAGLE-596
> URL: https://issues.apache.org/jira/browse/EAGLE-596
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.5
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
>
> h2. Exception
> {code}
> WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: 
> Error for /rest/metadata/policies
> ! java.lang.NoSuchFieldError: _nullProvider
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
>  ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
> ~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
> ! at 
> io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! 

[jira] [Updated] (EAGLE-596) Got Create policy error

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-596:
---
Summary: Got Create policy error  (was: Create policy error)

> Got Create policy error
> ---
>
> Key: EAGLE-596
> URL: https://issues.apache.org/jira/browse/EAGLE-596
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.5
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
>
> h2. Exception
> {code}
> WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: 
> Error for /rest/metadata/policies
> ! java.lang.NoSuchFieldError: _nullProvider
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
>  ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
>  ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at 
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
> ~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
> ! at 
> io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
>  ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>  ~[jersey-server-1.19.1.jar:1.19.1]
> ! at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>  

[jira] [Updated] (EAGLE-596) Create policy error

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-596:
---
Description: 
h2. Exception

{code}
WARN  [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler: Error 
for /rest/metadata/policies
! java.lang.NoSuchFieldError: _nullProvider
! at 
com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
 ~[jackson-databind-2.6.6.jar:2.6.6]
! at 
com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at 
com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
 ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
! at com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470) 
~[jackson-databind-2.6.6.jar:2.6.6]
! at 
com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912) 
~[jackson-databind-2.6.6.jar:2.6.6]
! at 
com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 
~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
! at 
io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
 ~[dropwizard-jersey-0.7.1.jar:0.7.1]
! at 
com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
 ~[dropwizard-jersey-0.7.1.jar:0.7.1]
! at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
 ~[jersey-server-1.19.1.jar:1.19.1]
! at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
 ~[jersey-servlet-1.18.1.jar:1.18.1]
! at 

[jira] [Resolved] (EAGLE-121) predefined/generic topology for adhoc data sources

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-121.

Resolution: Fixed

> predefined/generic topology for adhoc data sources
> --
>
> Key: EAGLE-121
> URL: https://issues.apache.org/jira/browse/EAGLE-121
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Aroop Maliakkal
>Assignee: Su Ralph
>
> Eagle should provide one or more predefined topology where user can send any 
> metrics to the predefined topology. This predefined/generic topology should 
> be exposed with well documented contract/grammer details so that any process 
> which talks to this generic topology can send metrics on that contract



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

[jira] [Updated] (EAGLE-471) AlertBolt introduce un-serializble member

[Zeng, Bryant (JIRA)]

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

Zeng, Bryant updated EAGLE-471:
---
Description: 
Exception is as below:
2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set 
topology.message.timeout.secs as 3600
Exception in thread "main" java.lang.RuntimeException: 
java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor
   at 
backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43)
at backtype.storm.utils.Utils.serialize(Utils.java:85)
at 
backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106)
at 
org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144)
at 
org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168)
at 
org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193)
at 
org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: java.io.NotSerializableException: 
java.util.concurrent.ThreadPoolExecutor
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
at 
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
at 
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at 
backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15]
  

It seems there's some member in AlertBolt which is not serialized.

  was:
AlerBolt.executors  

2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set 
topology.message.timeout.secs as 3600
Exception in thread "main" java.lang.RuntimeException: 
java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor
   at 
backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43)
at backtype.storm.utils.Utils.serialize(Utils.java:85)
at 
backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106)
at 
org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144)
at 
org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168)
at 
org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193)
at 
org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: java.io.NotSerializableException: 
java.util.concurrent.ThreadPoolExecutor
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
at 
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
at 
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at 
backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15]
  
idea里跑UnitTopologyMain


> AlertBolt introduce un-serializble member 
> --
>
> Key: EAGLE-471
> URL: https://issues.apache.org/jira/browse/EAGLE-471
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
>Priority: Blocker
>
> Exception is as below:
> 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set 
> topology.message.timeout.secs as 3600
> Exception in thread "main" java.lang.RuntimeException: 
> java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor
>at 
> 

[jira] [Reopened] (EAGLE-471) AlertBolt introduce un-serializble member

[Zeng, Bryant (JIRA)]

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

Zeng, Bryant reopened EAGLE-471:


> AlertBolt introduce un-serializble member 
> --
>
> Key: EAGLE-471
> URL: https://issues.apache.org/jira/browse/EAGLE-471
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
>Priority: Blocker
>
> AlerBolt.executors  
> 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set 
> topology.message.timeout.secs as 3600
> Exception in thread "main" java.lang.RuntimeException: 
> java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor
>at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43)
> at backtype.storm.utils.Utils.serialize(Utils.java:85)
> at 
> backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193)
> at 
> org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: java.io.NotSerializableException: 
> java.util.concurrent.ThreadPoolExecutor
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15]
>   
> idea里跑UnitTopologyMain



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

[jira] [Resolved] (EAGLE-335) Show alert definition so that user could see the trigger condition of alert

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-335.

Resolution: Won't Fix

Alert UI is redesigned. This is PR is now deprecated. closed.

> Show alert definition so that user could see the trigger condition of alert
> ---
>
> Key: EAGLE-335
> URL: https://issues.apache.org/jira/browse/EAGLE-335
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> When user see a alert happens from a policy's evaluation. It would be better 
> to see the trigger condition in alert. Etc. in jmx metric cases, there would 
> alert with contents of
> The Policy "NameNodeLagPolicy" has been detected with the below information: 
> transactIdA="1.2623229E7" transactIdB="1.2623228E7" 
> showing the threshold would make it more intuitive for alert reader.



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

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

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-580.

Resolution: Fixed
  Assignee: Zeng, Bryant  (was: Su Ralph)

> MongodbMetadata: kafka have dot in topic name cause spec store failed
> -
>
> Key: EAGLE-580
> URL: https://issues.apache.org/jira/browse/EAGLE-580
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> It's possible that user have DOT in topic names. In this case, mongodb 
> metadata store of spoutspec would use the topic name as key in mongodb, which 
> rejected by mongodb since it doens't allow dot in key.
> Solution is to do covnert of SpoutSpec in mongdb storage, and do appropriate 
> transform when read from db.



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

[jira] [Resolved] (EAGLE-586) AlertEngine: multiple routing of alerts is broken because of event not copied

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-586.

Resolution: Fixed

> AlertEngine: multiple routing of alerts is broken because of event not copied
> -
>
> Key: EAGLE-586
> URL: https://issues.apache.org/jira/browse/EAGLE-586
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> AlertEngine: multiple routing of alerts is broken because of event not copied
> The default deduplicator contains a shallow copy of the events 
> (StreamEvent.data) is not copied, thus following change impact both two 
> event. 



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

[jira] [Updated] (EAGLE-586) AlertEngine: multiple routing of alerts is broken because of event not copied

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-586:
---
Description: 
AlertEngine: multiple routing of alerts is broken because of event not copied

The default deduplicator contains a shallow copy of the events 
(StreamEvent.data) is not copied, thus following change impact both two event. 

> AlertEngine: multiple routing of alerts is broken because of event not copied
> -
>
> Key: EAGLE-586
> URL: https://issues.apache.org/jira/browse/EAGLE-586
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> AlertEngine: multiple routing of alerts is broken because of event not copied
> The default deduplicator contains a shallow copy of the events 
> (StreamEvent.data) is not copied, thus following change impact both two 
> event. 



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

[jira] [Closed] (EAGLE-570) Refactor: Make sure engine publisher only have general feature.

[Zeng, Bryant (JIRA)]

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

Zeng, Bryant closed EAGLE-570.
--
Resolution: Fixed

> Refactor: Make sure engine publisher only have general feature.
> ---
>
> Key: EAGLE-570
> URL: https://issues.apache.org/jira/browse/EAGLE-570
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> Eagle-567 intend to provide better formatting of slack channel message.  But 
> the implementation introduce too much specific logic that beyond a common 
> alerting engine should have.
> Need to refactor to move the specific logic to either vendor specific 
> extension or have configurable formatting.



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