[jira] [Commented] (EAGLE-741) Make publishment settings both policy & stream awareness

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-741:
--

GitHub user garrettlish opened a pull request:

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

EAGLE-741: Make publishment settings both policy & stream awareness

Currently our publishment is defined policy specific, we cannot publish the 
alert into different places for one policy although there are multiple output 
streams for this policy.

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

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

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

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


commit 14d9bf133863514991594b044fd2507ad8c4810e
Author: Xiancheng Li 
Date:   2016-11-07T05:55:20Z

EAGLE-741: Make publishment settings both policy & stream awareness

Currently our publishment is defined policy specific, we cannot publish the 
alert into different places for one policy although there are multiple output 
streams for this policy.




> Make publishment settings both policy & stream awareness
> 
>
> Key: EAGLE-741
> URL: https://issues.apache.org/jira/browse/EAGLE-741
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Currently our publishment is defined policy specific, we cannot publish the 
> alert into different places for one policy although there are multiple output 
> streams for this policy. 



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

[GitHub] incubator-eagle pull request #613: EAGLE-741: Make publishment settings both...

[garrettlish]

GitHub user garrettlish opened a pull request:

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

EAGLE-741: Make publishment settings both policy & stream awareness

Currently our publishment is defined policy specific, we cannot publish the 
alert into different places for one policy although there are multiple output 
streams for this policy.

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

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

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

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


commit 14d9bf133863514991594b044fd2507ad8c4810e
Author: Xiancheng Li 
Date:   2016-11-07T05:55:20Z

EAGLE-741: Make publishment settings both policy & stream awareness

Currently our publishment is defined policy specific, we cannot publish the 
alert into different places for one policy although there are multiple output 
streams for this policy.




---
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-742) disable streams when site has been removed

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-742:
--
Summary: disable streams when site has been removed  (was: delete streams 
when site has been removed)

> disable streams when site has been removed
> --
>
> Key: EAGLE-742
> URL: https://issues.apache.org/jira/browse/EAGLE-742
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When site has been removed, streams defined are still there. We need remove 
> them.



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

[jira] [Created] (EAGLE-742) delete streams when site has been removed

[wujinhu (JIRA)]

wujinhu created EAGLE-742:
-

 Summary: delete streams when site has been removed
 Key: EAGLE-742
 URL: https://issues.apache.org/jira/browse/EAGLE-742
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


When site has been removed, streams defined are still there. We need remove 
them.



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

[jira] [Assigned] (EAGLE-736) Fix eagle-data-process checkstyle warnings

[luokun (JIRA)]

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

luokun reassigned EAGLE-736:


Assignee: luokun

> Fix eagle-data-process checkstyle warnings
> --
>
> Key: EAGLE-736
> URL: https://issues.apache.org/jira/browse/EAGLE-736
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
>Assignee: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-data-process



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

[GitHub] incubator-eagle pull request #594: adjust description of dataSourceConfig.rM...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-411) Improve code coverage of eagle-storage-hbase

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-411:
--

Github user asfgit closed the pull request at:

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


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



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

[GitHub] incubator-eagle pull request #608: [EAGLE-411] Improve code coverage of eagl...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-723) Add unit test for configbus

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-723:
--

Github user asfgit closed the pull request at:

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


> Add unit test for configbus
> ---
>
> Key: EAGLE-723
> URL: https://issues.apache.org/jira/browse/EAGLE-723
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Minor
>




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

[GitHub] incubator-eagle pull request #609: [EAGLE-723] Add unit test for configbus.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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] [Resolved] (EAGLE-724) Fix eagle-common checkstyle warnings

[luokun (JIRA)]

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

luokun resolved EAGLE-724.
--
Resolution: Fixed

> Fix eagle-common checkstyle warnings
> 
>
> Key: EAGLE-724
> URL: https://issues.apache.org/jira/browse/EAGLE-724
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
>Assignee: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-common



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

[jira] [Assigned] (EAGLE-724) Fix eagle-common checkstyle warnings

[luokun (JIRA)]

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

luokun reassigned EAGLE-724:


Assignee: luokun

> Fix eagle-common checkstyle warnings
> 
>
> Key: EAGLE-724
> URL: https://issues.apache.org/jira/browse/EAGLE-724
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
>Assignee: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-common



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

[jira] [Assigned] (EAGLE-738) Fix eagle-metadata checkstyle warnings

[luokun (JIRA)]

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

luokun reassigned EAGLE-738:


Assignee: luokun

> Fix eagle-metadata checkstyle warnings
> --
>
> Key: EAGLE-738
> URL: https://issues.apache.org/jira/browse/EAGLE-738
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
>Assignee: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-metadata



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

[jira] [Assigned] (EAGLE-740) Fix eagle-query checkstyle warnings

[luokun (JIRA)]

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

luokun reassigned EAGLE-740:


Assignee: luokun  (was: luokun)

> Fix eagle-query checkstyle warnings
> ---
>
> Key: EAGLE-740
> URL: https://issues.apache.org/jira/browse/EAGLE-740
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
>Assignee: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-query



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

[jira] [Updated] (EAGLE-739) Fix eagle-metric checkstyle warnings

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-739:
---
Assignee: luokun

> Fix eagle-metric checkstyle warnings
> 
>
> Key: EAGLE-739
> URL: https://issues.apache.org/jira/browse/EAGLE-739
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
>Assignee: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-metric



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

[GitHub] incubator-eagle issue #609: [EAGLE-723] Add unit test for configbus.

[haoch]

Github user haoch commented on the issue:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-723) Add unit test for configbus

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-723:
--

Github user haoch commented on the issue:

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


> Add unit test for configbus
> ---
>
> Key: EAGLE-723
> URL: https://issues.apache.org/jira/browse/EAGLE-723
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Minor
>




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

[GitHub] incubator-eagle pull request #609: [EAGLE-723] Add unit test for configbus.

[r7raul1984]

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

https://github.com/apache/incubator-eagle/pull/609#discussion_r86718380
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/config/ConfigBusConsumer.java
 ---
@@ -54,7 +54,12 @@ public ConfigBusConsumer(ZKConfig config, String topic, 
ConfigChangeCallback cal
 
 public ConfigValue getConfigValue() throws Exception {
 byte[] value = curator.getData().forPath(zkPath);
-ConfigValue v = mapper.readValue(value, ConfigValue.class);
+ConfigValue v;
+try {
+v = mapper.readValue(value, ConfigValue.class);
+} catch (JsonParseException e) {
+v = new ConfigValue();
--- End diff --

OK


---
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-728) Application can't load application.properties when running local mode

[Lingang Deng (JIRA)]

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

Lingang Deng commented on EAGLE-728:


[~wujinhu]I have considered this choice, I think user don't know this 
properties if we use "Custom" function, it's not a cool user experience.  So I 
define it in Provider xml files without any impact to the applications.

> Application can't load application.properties when running local mode
> -
>
> Key: EAGLE-728
> URL: https://issues.apache.org/jira/browse/EAGLE-728
> Project: Eagle
>  Issue Type: Bug
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>
> When running local mode, jpm app can't get property 
> "job.name.normalization.rules.key", then get exception
> {code}
> ERROR [2016-11-02 15:18:04,382] 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO: fail reading 
> job history file
> ! java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.eagle.jpm.util.JobNameNormalization
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.handleJob(JHFEventReaderBase.java:199)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleJobSubmitted(JHFMRVer2EventReader.java:187)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleEvent(JHFMRVer2EventReader.java:53)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser.parse(JHFMRVer2Parser.java:61)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:58)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:123)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:166)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:160)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> backtype.storm.daemon.executor$fn__3373$fn__3388$fn__3417.invoke(executor.clj:565)
>  [storm-core-0.9.3.jar:0.9.3]
> ! at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463) 
> [storm-core-0.9.3.jar:0.9.3]
> ! at clojure.lang.AFn.run(AFn.java:24) 
> [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {code}



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

[GitHub] incubator-eagle pull request #602: EAGLE-728 Application can't load applicat...

[chitin]

Github user chitin closed the pull request at:

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


---
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-723) Add unit test for configbus

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-723:
--

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

https://github.com/apache/incubator-eagle/pull/609#discussion_r86718175
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/config/ConfigBusConsumer.java
 ---
@@ -54,7 +54,12 @@ public ConfigBusConsumer(ZKConfig config, String topic, 
ConfigChangeCallback cal
 
 public ConfigValue getConfigValue() throws Exception {
 byte[] value = curator.getData().forPath(zkPath);
-ConfigValue v = mapper.readValue(value, ConfigValue.class);
+ConfigValue v;
+try {
+v = mapper.readValue(value, ConfigValue.class);
+} catch (JsonParseException e) {
+v = new ConfigValue();
--- End diff --

Pls. add `LOG.warn(e.getMessage())` for the ignored exception.


> Add unit test for configbus
> ---
>
> Key: EAGLE-723
> URL: https://issues.apache.org/jira/browse/EAGLE-723
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Minor
>




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

[GitHub] incubator-eagle pull request #609: [EAGLE-723] Add unit test for configbus.

[haoch]

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

https://github.com/apache/incubator-eagle/pull/609#discussion_r86718175
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/config/ConfigBusConsumer.java
 ---
@@ -54,7 +54,12 @@ public ConfigBusConsumer(ZKConfig config, String topic, 
ConfigChangeCallback cal
 
 public ConfigValue getConfigValue() throws Exception {
 byte[] value = curator.getData().forPath(zkPath);
-ConfigValue v = mapper.readValue(value, ConfigValue.class);
+ConfigValue v;
+try {
+v = mapper.readValue(value, ConfigValue.class);
+} catch (JsonParseException e) {
+v = new ConfigValue();
--- End diff --

Pls. add `LOG.warn(e.getMessage())` for the ignored exception.


---
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-740) Fix eagle-query checkstyle warnings

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-740:
---
Assignee: luokun

> Fix eagle-query checkstyle warnings
> ---
>
> Key: EAGLE-740
> URL: https://issues.apache.org/jira/browse/EAGLE-740
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
>Assignee: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-query



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

[jira] [Updated] (EAGLE-741) Make publishment settings both policy & stream awareness

[Garrett Li (JIRA)]

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

Garrett Li updated EAGLE-741:
-
Summary: Make publishment settings both policy & stream awareness  (was: 
Make publishment both policy & stream specific)

> Make publishment settings both policy & stream awareness
> 
>
> Key: EAGLE-741
> URL: https://issues.apache.org/jira/browse/EAGLE-741
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Currently our publishment is defined policy specific, we cannot publish the 
> alert into different places for one policy although there are multiple output 
> streams for this policy. 



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

[jira] [Created] (EAGLE-741) Make publishment both policy & stream specific

[Garrett Li (JIRA)]

Garrett Li created EAGLE-741:


 Summary: Make publishment both policy & stream specific
 Key: EAGLE-741
 URL: https://issues.apache.org/jira/browse/EAGLE-741
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Garrett Li
Assignee: Garrett Li
 Fix For: v0.5.0


Currently our publishment is defined policy specific, we cannot publish the 
alert into different places for one policy although there are multiple output 
streams for this policy. 



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

[jira] [Commented] (EAGLE-728) Application can't load application.properties when running local mode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-728:
--

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

https://github.com/apache/incubator-eagle/pull/612#discussion_r86710130
  
--- Diff: 
eagle-jpm/eagle-hadoop-queue/src/main/resources/META-INF/providers/org.apache.eagle.hadoop.queue.HadoopQueueRunningAppProvider.xml
 ---
@@ -47,6 +47,12 @@
   interval seconds of fetching metric from resource 
manager
   10
 
+
+  job.name.normalization.rules.key
+  Job Name Normalization Rules Key
+  User use -Dkey=job name normalization 
rules
+  ^(.*)[0-9]{4}/[0-9]{2}/[0-9]{2}/[0-9]{2}$ => $1~ ; 
^(oozie:launcher):T=(.*):W=(.*):A=(.*):ID=(?:.*)$ => $1-$2-$3-$4~ ; 
^(.*)([0-9]{10})$ => $1~ ; 
^[0-9a-z]{8}-[0-9a-z]{4}-[0-9a-z]{4}-[0-9a-z]{4}-[0-9a-z]{12}$ => uuid~ ; 
^(.*)(?:[0-9]{8}/[0-9]{2}_[0-9]{2})$ => $1~
+
   
--- End diff --

Please remove this configuration from these Provider xml files. Since we 
have 'Custom' function so that advanced users can add other configurations(like 
this) if they want.
If user passes this custom defined configuration, it will override the 
predefined value.


> Application can't load application.properties when running local mode
> -
>
> Key: EAGLE-728
> URL: https://issues.apache.org/jira/browse/EAGLE-728
> Project: Eagle
>  Issue Type: Bug
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>
> When running local mode, jpm app can't get property 
> "job.name.normalization.rules.key", then get exception
> {code}
> ERROR [2016-11-02 15:18:04,382] 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO: fail reading 
> job history file
> ! java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.eagle.jpm.util.JobNameNormalization
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.handleJob(JHFEventReaderBase.java:199)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleJobSubmitted(JHFMRVer2EventReader.java:187)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleEvent(JHFMRVer2EventReader.java:53)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser.parse(JHFMRVer2Parser.java:61)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:58)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:123)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:166)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:160)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> backtype.storm.daemon.executor$fn__3373$fn__3388$fn__3417.invoke(executor.clj:565)
>  [storm-core-0.9.3.jar:0.9.3]
> ! at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463) 
> [storm-core-0.9.3.jar:0.9.3]
> ! at clojure.lang.AFn.run(AFn.java:24) 
> [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {code}



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

[GitHub] incubator-eagle pull request #612: EAGLE-728 Application can't load applicat...

[wujinhu]

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

https://github.com/apache/incubator-eagle/pull/612#discussion_r86710130
  
--- Diff: 
eagle-jpm/eagle-hadoop-queue/src/main/resources/META-INF/providers/org.apache.eagle.hadoop.queue.HadoopQueueRunningAppProvider.xml
 ---
@@ -47,6 +47,12 @@
   interval seconds of fetching metric from resource 
manager
   10
 
+
+  job.name.normalization.rules.key
+  Job Name Normalization Rules Key
+  User use -Dkey=job name normalization 
rules
+  ^(.*)[0-9]{4}/[0-9]{2}/[0-9]{2}/[0-9]{2}$ => $1~ ; 
^(oozie:launcher):T=(.*):W=(.*):A=(.*):ID=(?:.*)$ => $1-$2-$3-$4~ ; 
^(.*)([0-9]{10})$ => $1~ ; 
^[0-9a-z]{8}-[0-9a-z]{4}-[0-9a-z]{4}-[0-9a-z]{4}-[0-9a-z]{12}$ => uuid~ ; 
^(.*)(?:[0-9]{8}/[0-9]{2}_[0-9]{2})$ => $1~
+
   
--- End diff --

Please remove this configuration from these Provider xml files. Since we 
have 'Custom' function so that advanced users can add other configurations(like 
this) if they want.
If user passes this custom defined configuration, it will override the 
predefined value.


---
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 #612: EAGLE-728 Application can't load applicat...

[wujinhu]

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

https://github.com/apache/incubator-eagle/pull/612#discussion_r86709972
  
--- Diff: 
eagle-jpm/eagle-jpm-util/src/main/java/org/apache/eagle/jpm/util/JobNameNormalization.java
 ---
@@ -64,7 +67,7 @@ private JobNameNormalization() {
 // load normalization rules
 Config conf = ConfigFactory.load();
--- End diff --

Please remove this line(Config conf = ConfigFactory.load();) from code. 
Since our application is a storm topology, it will be better if we pass 
configure to it when we initialize it so that it won't load dynamically.

Please do a simple refactor and just pass Config object to this class. 


---
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-728) Application can't load application.properties when running local mode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-728:
--

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

https://github.com/apache/incubator-eagle/pull/612#discussion_r86709972
  
--- Diff: 
eagle-jpm/eagle-jpm-util/src/main/java/org/apache/eagle/jpm/util/JobNameNormalization.java
 ---
@@ -64,7 +67,7 @@ private JobNameNormalization() {
 // load normalization rules
 Config conf = ConfigFactory.load();
--- End diff --

Please remove this line(Config conf = ConfigFactory.load();) from code. 
Since our application is a storm topology, it will be better if we pass 
configure to it when we initialize it so that it won't load dynamically.

Please do a simple refactor and just pass Config object to this class. 


> Application can't load application.properties when running local mode
> -
>
> Key: EAGLE-728
> URL: https://issues.apache.org/jira/browse/EAGLE-728
> Project: Eagle
>  Issue Type: Bug
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>
> When running local mode, jpm app can't get property 
> "job.name.normalization.rules.key", then get exception
> {code}
> ERROR [2016-11-02 15:18:04,382] 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO: fail reading 
> job history file
> ! java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.eagle.jpm.util.JobNameNormalization
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.handleJob(JHFEventReaderBase.java:199)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleJobSubmitted(JHFMRVer2EventReader.java:187)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleEvent(JHFMRVer2EventReader.java:53)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser.parse(JHFMRVer2Parser.java:61)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:58)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:123)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:166)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:160)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> backtype.storm.daemon.executor$fn__3373$fn__3388$fn__3417.invoke(executor.clj:565)
>  [storm-core-0.9.3.jar:0.9.3]
> ! at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463) 
> [storm-core-0.9.3.jar:0.9.3]
> ! at clojure.lang.AFn.run(AFn.java:24) 
> [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {code}



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

[jira] [Commented] (EAGLE-728) Application can't load application.properties when running local mode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-728:
--

Github user wujinhu commented on the issue:

https://github.com/apache/incubator-eagle/pull/602
  
Please close this, I see another PR has been opened for the same issue.


> Application can't load application.properties when running local mode
> -
>
> Key: EAGLE-728
> URL: https://issues.apache.org/jira/browse/EAGLE-728
> Project: Eagle
>  Issue Type: Bug
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>
> When running local mode, jpm app can't get property 
> "job.name.normalization.rules.key", then get exception
> {code}
> ERROR [2016-11-02 15:18:04,382] 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO: fail reading 
> job history file
> ! java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.eagle.jpm.util.JobNameNormalization
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.handleJob(JHFEventReaderBase.java:199)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleJobSubmitted(JHFMRVer2EventReader.java:187)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleEvent(JHFMRVer2EventReader.java:53)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser.parse(JHFMRVer2Parser.java:61)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:58)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:123)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:166)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:160)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> backtype.storm.daemon.executor$fn__3373$fn__3388$fn__3417.invoke(executor.clj:565)
>  [storm-core-0.9.3.jar:0.9.3]
> ! at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463) 
> [storm-core-0.9.3.jar:0.9.3]
> ! at clojure.lang.AFn.run(AFn.java:24) 
> [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {code}



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

[GitHub] incubator-eagle issue #602: EAGLE-728 Application can't load application.pro...

[wujinhu]

Github user wujinhu commented on the issue:

https://github.com/apache/incubator-eagle/pull/602
  
Please close this, I see another PR has been opened for the same issue.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-740) Fix eagle-query checkstyle warnings

[luokun (JIRA)]

luokun created EAGLE-740:


 Summary: Fix eagle-query checkstyle warnings
 Key: EAGLE-740
 URL: https://issues.apache.org/jira/browse/EAGLE-740
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.4.0
Reporter: luokun
 Fix For: v0.5.0


Fix checkstyle problems on eagle-common



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

[jira] [Updated] (EAGLE-740) Fix eagle-query checkstyle warnings

[luokun (JIRA)]

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

luokun updated EAGLE-740:
-
Description: Fix checkstyle problems on eagle-query  (was: Fix checkstyle 
problems on eagle-common)

> Fix eagle-query checkstyle warnings
> ---
>
> Key: EAGLE-740
> URL: https://issues.apache.org/jira/browse/EAGLE-740
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-query



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

[jira] [Created] (EAGLE-739) Fix eagle-metric checkstyle warnings

[luokun (JIRA)]

luokun created EAGLE-739:


 Summary: Fix eagle-metric checkstyle warnings
 Key: EAGLE-739
 URL: https://issues.apache.org/jira/browse/EAGLE-739
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.4.0
Reporter: luokun
 Fix For: v0.5.0


Fix checkstyle problems on eagle-common



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

[jira] [Updated] (EAGLE-737) Fix eagle-embed checkstyle warnings

[luokun (JIRA)]

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

luokun updated EAGLE-737:
-
Description: Fix checkstyle problems on eagle-embed  (was: Fix checkstyle 
problems on eagle-data-process)

> Fix eagle-embed checkstyle warnings
> ---
>
> Key: EAGLE-737
> URL: https://issues.apache.org/jira/browse/EAGLE-737
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-embed



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

[jira] [Updated] (EAGLE-737) Fix eagle-embed checkstyle warnings

[luokun (JIRA)]

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

luokun updated EAGLE-737:
-
Summary: Fix eagle-embed checkstyle warnings  (was: Fix eagle-data-process 
checkstyle warnings)

> Fix eagle-embed checkstyle warnings
> ---
>
> Key: EAGLE-737
> URL: https://issues.apache.org/jira/browse/EAGLE-737
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-data-process



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

[jira] [Updated] (EAGLE-738) Fix eagle-metadata checkstyle warnings

[luokun (JIRA)]

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

luokun updated EAGLE-738:
-
Description: Fix checkstyle problems on eagle-metadata  (was: Fix 
checkstyle problems on eagle-common)

> Fix eagle-metadata checkstyle warnings
> --
>
> Key: EAGLE-738
> URL: https://issues.apache.org/jira/browse/EAGLE-738
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-metadata



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

[jira] [Created] (EAGLE-738) Fix eagle-metadata checkstyle warnings

[luokun (JIRA)]

luokun created EAGLE-738:


 Summary: Fix eagle-metadata checkstyle warnings
 Key: EAGLE-738
 URL: https://issues.apache.org/jira/browse/EAGLE-738
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.4.0
Reporter: luokun
 Fix For: v0.5.0


Fix checkstyle problems on eagle-common



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

[jira] [Created] (EAGLE-737) Fix eagle-data-process checkstyle warnings

[luokun (JIRA)]

luokun created EAGLE-737:


 Summary: Fix eagle-data-process checkstyle warnings
 Key: EAGLE-737
 URL: https://issues.apache.org/jira/browse/EAGLE-737
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.4.0
Reporter: luokun
 Fix For: v0.5.0


Fix checkstyle problems on eagle-common



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

[jira] [Updated] (EAGLE-737) Fix eagle-data-process checkstyle warnings

[luokun (JIRA)]

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

luokun updated EAGLE-737:
-
Description: Fix checkstyle problems on eagle-data-process  (was: Fix 
checkstyle problems on eagle-common)

> Fix eagle-data-process checkstyle warnings
> --
>
> Key: EAGLE-737
> URL: https://issues.apache.org/jira/browse/EAGLE-737
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-data-process



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

[jira] [Commented] (EAGLE-728) Application can't load application.properties when running local mode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-728:
--

GitHub user chitin opened a pull request:

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

EAGLE-728 Application can't load application.properties when running local 
mode

EAGLE-728 Application can't load application.properties when running local 
mode
- Use hard code, and overwrite it if user passes this configuration form 
web ui.

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

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

$ git pull https://github.com/chitin/incubator-eagle EAGLE-728-2

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

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


commit ab6ae575dc53ad65766b359422d26e44f7783476
Author: chitin 
Date:   2016-11-07T02:27:21Z

EAGLE-728 Application can't load application.properties when running local 
mode
- Use hard code, and overwrite it if user passes this configuration form 
web ui.
https://issues.apache.org/jira/browse/EAGLE-728




> Application can't load application.properties when running local mode
> -
>
> Key: EAGLE-728
> URL: https://issues.apache.org/jira/browse/EAGLE-728
> Project: Eagle
>  Issue Type: Bug
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>
> When running local mode, jpm app can't get property 
> "job.name.normalization.rules.key", then get exception
> {code}
> ERROR [2016-11-02 15:18:04,382] 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO: fail reading 
> job history file
> ! java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.eagle.jpm.util.JobNameNormalization
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.handleJob(JHFEventReaderBase.java:199)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleJobSubmitted(JHFMRVer2EventReader.java:187)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.handleEvent(JHFMRVer2EventReader.java:53)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser.parse(JHFMRVer2Parser.java:61)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:58)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:123)
>  ~[eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:166)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:160)
>  [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at 
> backtype.storm.daemon.executor$fn__3373$fn__3388$fn__3417.invoke(executor.clj:565)
>  [storm-core-0.9.3.jar:0.9.3]
> ! at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463) 
> [storm-core-0.9.3.jar:0.9.3]
> ! at clojure.lang.AFn.run(AFn.java:24) 
> [eagle-topology-0.5.0-incubating-SNAPSHOT-assembly.jar:na]
> ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {code}



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

[jira] [Updated] (EAGLE-736) Fix eagle-data-process checkstyle warnings

[luokun (JIRA)]

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

luokun updated EAGLE-736:
-
Description: Fix checkstyle problems on eagle-data-process  (was: Fix 
checkstyle problems on eagle-common)

> Fix eagle-data-process checkstyle warnings
> --
>
> Key: EAGLE-736
> URL: https://issues.apache.org/jira/browse/EAGLE-736
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
>Reporter: luokun
> Fix For: v0.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix checkstyle problems on eagle-data-process



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

[GitHub] incubator-eagle pull request #612: EAGLE-728 Application can't load applicat...

[chitin]

GitHub user chitin opened a pull request:

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

EAGLE-728 Application can't load application.properties when running local 
mode

EAGLE-728 Application can't load application.properties when running local 
mode
- Use hard code, and overwrite it if user passes this configuration form 
web ui.

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

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

$ git pull https://github.com/chitin/incubator-eagle EAGLE-728-2

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

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


commit ab6ae575dc53ad65766b359422d26e44f7783476
Author: chitin 
Date:   2016-11-07T02:27:21Z

EAGLE-728 Application can't load application.properties when running local 
mode
- Use hard code, and overwrite it if user passes this configuration form 
web ui.
https://issues.apache.org/jira/browse/EAGLE-728




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-736) Fix eagle-data-process checkstyle warnings

[luokun (JIRA)]

luokun created EAGLE-736:


 Summary: Fix eagle-data-process checkstyle warnings
 Key: EAGLE-736
 URL: https://issues.apache.org/jira/browse/EAGLE-736
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.4.0
Reporter: luokun
 Fix For: v0.5.0


Fix checkstyle problems on eagle-common



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

[jira] [Created] (EAGLE-735) Policy detail UI update

[Jilin, Jiang (JIRA)]

Jilin, Jiang created EAGLE-735:
--

 Summary: Policy detail UI update
 Key: EAGLE-735
 URL: https://issues.apache.org/jira/browse/EAGLE-735
 Project: Eagle
  Issue Type: Improvement
Reporter: Jilin, Jiang
Assignee: Jilin, Jiang
Priority: Critical






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

[jira] [Resolved] (EAGLE-707) Mark "Task Statistic" page title as "Task Statistic (Beta)" instead of "(beta) Task Statistic"

[Jilin, Jiang (JIRA)]

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

Jilin, Jiang resolved EAGLE-707.

Resolution: Fixed

> Mark "Task Statistic" page title as "Task Statistic (Beta)" instead of 
> "(beta) Task Statistic"
> --
>
> Key: EAGLE-707
> URL: https://issues.apache.org/jira/browse/EAGLE-707
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: jianzhong.chen
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>




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

[jira] [Resolved] (EAGLE-725) Policy list UI improvement

[Jilin, Jiang (JIRA)]

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

Jilin, Jiang resolved EAGLE-725.

Resolution: Fixed

> Policy list UI improvement
> --
>
> Key: EAGLE-725
> URL: https://issues.apache.org/jira/browse/EAGLE-725
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>
> * Name | Description (or N/A) | Action (Enable/Disable) as in future most of 
> policy are immutable -> Click into detail view with 
> "Delete/Modify/Enable/Disable".
> * Add filter by siteId/appId. 



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

Re: Eagle graduation steps

[Edward Zhang]

Hi Henry and Eagle Mentors,

Seems we have gone through most of check list for graduation, can I start
formal community vote on graduation according to
http://incubator.apache.org/guides/graduation.html#process?



   - a charter for your project(Draft resolution was done)
   - a positive community graduation VOTE
   
   - a positive IPMC recommendation VOTE
   
   - the acceptance of the resolution
    by
   the Board

Also, do you have any remaining issues about graduation before we do vote?


   - Ensure Mentors
   

and IPMC
   

have
   no remaining issues
   



Thanks
Edward

On Sun, Oct 30, 2016 at 8:59 PM, Edward Zhang 
wrote:

> Hi Eagle community,
>
> As one step towards graduation, the following is proposed project
> destination and resolution and please provide your feedback.
>
> For destination, according to the guide line http://incubator.apache.org/
> guides/graduation.html#subproject-or-top-level, because Apache Eagle is
> sponsored by IPMC, we should put it to be top-level project instead of
> subproject.
>
> For revision, here is the template, template https://svn.apache.
> org/repos/private/committers/board/templates/podling-tlp-resolution.txt.
> I put initial committers there and we need a chair for this project.
>
> Destination: Top-level project
>
> Revision:
>
>   Establish the Apache Eagle Project
>
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to
>   the public, related to a distributed monitoring solution for
> identifying security and performance issues in real time on big data
> platforms, including Hadoop and Spark etc.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Eagle Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Eagle Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to a distributed monitoring solution for identifying
> security and performance issues in real time on big data platforms,
> including Hadoop and Spark etc.;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Eagle" be
>   and hereby is created, the person holding such office to
>   serve at the direction of the Board of Directors as the chair
>   of the Apache Eagle Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Eagle Project; and be it further
>
>   RESOLVED, that the persons listed immediately below be and
>   hereby are appointed to serve as the initial members of the
>   Apache Eagle Project:
>
>
> * yonzhang2...@apache.org
>
> * h...@apache.org
>
> * qingwz...@apache.org
>
> * ji...@apache.org
>
> * ralp...@apache.org
>
> * jinh...@apache.org
>
> * daz...@apache.org
>
> * senthilec...@apache.org
>
> * hdenduk...@apache.org
>
> * m...@apache.org
>
> * arunmanoha...@apache.org
>
> * cgu...@apache.org
>
> * lib...@apache.org
>
>
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that {$name}
>   be appointed to the office of Vice President, Apache Eagle, to
>   serve in accordance with and subject to the direction of the
>   Board of Directors and the Bylaws of the Foundation until
>   death, resignation, retirement, removal or disqualification,
>   or until a successor is appointed; and be it further
>
>   RESOLVED, that the initial Apache Eagle PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Eagle Project; and be it further
>
>   RESOLVED, that the Apache Eagle Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Eagle podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Eagle podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.
>
>
> On Sun, Oct 23, 2016 at 8:16 PM, Edward Zhang