[GitHub] incubator-eagle pull request: Eagle-61 classification supports sec...

[qingwen220]

GitHub user qingwen220 opened a pull request:

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

Eagle-61 classification supports secured cluster connection & enable Ldap 
authentication

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

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

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

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

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


commit 68ddab6430c2ed47967961578a94291cfdd34cbf
Author: Zhao, Qingwen 
Date:   2016-02-22T07:24:21Z

fix a bug in KafkaLog4jAppender.scala

commit a2e2b51f5b79b8d0bd7776c485fea8eebefe5a22
Author: Zhao, Qingwen 
Date:   2016-02-22T07:44:36Z

enable eagle login ldap authentication

commit 03b61d56772272b4cf2d96c38fd2f1fa592af07f
Author: Zhao, Qingwen 
Date:   2016-02-22T10:40:07Z

add kerberos authentication in hdfs/hbase web




---
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-61) HDFS classification supports HA and secured cluster connection

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-61:
-

GitHub user qingwen220 opened a pull request:

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

Eagle-61 classification supports secured cluster connection & enable Ldap 
authentication

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

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

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

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

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


commit 68ddab6430c2ed47967961578a94291cfdd34cbf
Author: Zhao, Qingwen 
Date:   2016-02-22T07:24:21Z

fix a bug in KafkaLog4jAppender.scala

commit a2e2b51f5b79b8d0bd7776c485fea8eebefe5a22
Author: Zhao, Qingwen 
Date:   2016-02-22T07:44:36Z

enable eagle login ldap authentication

commit 03b61d56772272b4cf2d96c38fd2f1fa592af07f
Author: Zhao, Qingwen 
Date:   2016-02-22T10:40:07Z

add kerberos authentication in hdfs/hbase web




> HDFS classification supports HA and secured cluster connection
> --
>
> Key: EAGLE-61
> URL: https://issues.apache.org/jira/browse/EAGLE-61
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> 1) support HA cluster connection
> 2) support kerberos secure cluster connection



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

[GitHub] incubator-eagle pull request: Eagle-61 classification supports sec...

[qingwen220]

Github user qingwen220 closed the pull request at:

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


---
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: Eagle-61 classification supports sec...

[qingwen220]

GitHub user qingwen220 reopened a pull request:

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

Eagle-61 classification supports secured cluster connection & enable Ldap 
authentication

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

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

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

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

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


commit 68ddab6430c2ed47967961578a94291cfdd34cbf
Author: Zhao, Qingwen 
Date:   2016-02-22T07:24:21Z

fix a bug in KafkaLog4jAppender.scala

commit a2e2b51f5b79b8d0bd7776c485fea8eebefe5a22
Author: Zhao, Qingwen 
Date:   2016-02-22T07:44:36Z

enable eagle login ldap authentication

commit 03b61d56772272b4cf2d96c38fd2f1fa592af07f
Author: Zhao, Qingwen 
Date:   2016-02-22T10:40:07Z

add kerberos authentication in hdfs/hbase web




---
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-61) HDFS classification supports HA and secured cluster connection

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-61:
-

Github user qingwen220 closed the pull request at:

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


> HDFS classification supports HA and secured cluster connection
> --
>
> Key: EAGLE-61
> URL: https://issues.apache.org/jira/browse/EAGLE-61
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> 1) support HA cluster connection
> 2) support kerberos secure cluster connection



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

[jira] [Commented] (EAGLE-61) HDFS classification supports HA and secured cluster connection

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-61:
-

GitHub user qingwen220 reopened a pull request:

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

Eagle-61 classification supports secured cluster connection & enable Ldap 
authentication

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

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

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

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

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


commit 68ddab6430c2ed47967961578a94291cfdd34cbf
Author: Zhao, Qingwen 
Date:   2016-02-22T07:24:21Z

fix a bug in KafkaLog4jAppender.scala

commit a2e2b51f5b79b8d0bd7776c485fea8eebefe5a22
Author: Zhao, Qingwen 
Date:   2016-02-22T07:44:36Z

enable eagle login ldap authentication

commit 03b61d56772272b4cf2d96c38fd2f1fa592af07f
Author: Zhao, Qingwen 
Date:   2016-02-22T10:40:07Z

add kerberos authentication in hdfs/hbase web




> HDFS classification supports HA and secured cluster connection
> --
>
> Key: EAGLE-61
> URL: https://issues.apache.org/jira/browse/EAGLE-61
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> 1) support HA cluster connection
> 2) support kerberos secure cluster connection



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

[jira] [Resolved] (EAGLE-166) Enhance metric collector script to extract hadoop ha status as metric

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-166.

Resolution: Fixed

> Enhance metric collector script to extract hadoop ha status as metric
> -
>
> Key: EAGLE-166
> URL: https://issues.apache.org/jira/browse/EAGLE-166
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> - hadoop.resourcemanager.hastate.total.count
> - hadoop.resourcemanager.hastate.active.count
> - hadoop.resourcemanager.hastate.standby.count
> - hadoop.resourcemanager.hastate.failed.count
> - hadoop.namenode.hastate.total.count
> - hadoop.namenode.hastate.active.count
> - hadoop.namenode.hastate.standby.count
> - hadoop.namenode.hastate.failed.count



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

[jira] [Updated] (EAGLE-166) Enhance metric collector script to extract hadoop ha status as metric

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-166:
---
Fix Version/s: 0.3.0

> Enhance metric collector script to extract hadoop ha status as metric
> -
>
> Key: EAGLE-166
> URL: https://issues.apache.org/jira/browse/EAGLE-166
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> - hadoop.resourcemanager.hastate.total.count
> - hadoop.resourcemanager.hastate.active.count
> - hadoop.resourcemanager.hastate.standby.count
> - hadoop.resourcemanager.hastate.failed.count
> - hadoop.namenode.hastate.total.count
> - hadoop.namenode.hastate.active.count
> - hadoop.namenode.hastate.standby.count
> - hadoop.namenode.hastate.failed.count



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

[jira] [Created] (EAGLE-167) Refine JMX Collector Code

[Hao Chen (JIRA)]

Hao Chen created EAGLE-167:
--

 Summary: Refine JMX Collector Code
 Key: EAGLE-167
 URL: https://issues.apache.org/jira/browse/EAGLE-167
 Project: Eagle
  Issue Type: Improvement
Reporter: Hao Chen
Assignee: Hao Chen






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

[jira] [Commented] (EAGLE-167) Refine JMX Collector Code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-167:
--

GitHub user haoch opened a pull request:

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

EAGLE-167 refactor metric collector script

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


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

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

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

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


commit 8cfffce55fe860a2a72e5745aaa148fe9da77a81
Author: Hao Chen 
Date:   2016-02-22T15:47:40Z

EAGLE-167 Refactor metric collector script for better code style and 
extensibility

commit 51874652be4b4278682474208816957b1a5dc26f
Author: Hao Chen 
Date:   2016-02-22T15:50:43Z

EAGLE-167 Remove deprecated hadoop_jmx_kafka.py and metric_extensions.py




> Refine JMX Collector Code
> -
>
> Key: EAGLE-167
> URL: https://issues.apache.org/jira/browse/EAGLE-167
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[GitHub] incubator-eagle pull request: EAGLE-167 refactor metric collector ...

[haoch]

GitHub user haoch opened a pull request:

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

EAGLE-167 refactor metric collector script

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


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

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

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

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


commit 8cfffce55fe860a2a72e5745aaa148fe9da77a81
Author: Hao Chen 
Date:   2016-02-22T15:47:40Z

EAGLE-167 Refactor metric collector script for better code style and 
extensibility

commit 51874652be4b4278682474208816957b1a5dc26f
Author: Hao Chen 
Date:   2016-02-22T15:50:43Z

EAGLE-167 Remove deprecated hadoop_jmx_kafka.py and metric_extensions.py




---
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-168) Notification Plugin AlertEmailPlugin Error

[Senthilkumar (JIRA)]

Senthilkumar created EAGLE-168:
--

 Summary: Notification Plugin AlertEmailPlugin Error
 Key: EAGLE-168
 URL: https://issues.apache.org/jira/browse/EAGLE-168
 Project: Eagle
  Issue Type: Bug
Affects Versions: 0.3.0
Reporter: Senthilkumar
Assignee: Senthilkumar


Alert Email Plugin Initialization failed .

com.typesafe.config.ConfigException$Missing: No configuration setting found for 
key 'eagleProps'
at com.typesafe.config.impl.SimpleConfig.findKey(SimpleConfig.java:124) 
~[stormjar.jar:na]
at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:145) 
~[stormjar.jar:na]
at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:159) 
~[stormjar.jar:na]
at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:164) 
~[stormjar.jar:na]
at 
com.typesafe.config.impl.SimpleConfig.getObject(SimpleConfig.java:218) 
~[stormjar.jar:




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

[GitHub] incubator-eagle pull request: Eagle -168 - AlertEmail Initializati...

[senthilec566]

GitHub user senthilec566 opened a pull request:

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

Eagle -168 - AlertEmail Initialization Issue



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

$ git pull https://github.com/senthilec566/incubator-eagle EAGLE-168

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

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


commit 00d2aa49de50dc23ee41e164e0e0a6db0ff3c81d
Author: senthilkumar 
Date:   2016-02-22T17:27:59Z

config obj refactored




---
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: Eagle -168 - AlertEmail Initializati...

[yonzhang]

Github user yonzhang commented on the pull request:

https://github.com/apache/incubator-eagle/pull/101#issuecomment-187293016
  
code is good, please go ahead to 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-169) Dynamic security event correlation in Eagle

[Edward Zhang (JIRA)]

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

Edward Zhang updated EAGLE-169:
---
Summary: Dynamic security event correlation in Eagle  (was: Dynamic 
security event correlation platform in Eagle)

> Dynamic security event correlation in Eagle
> ---
>
> Key: EAGLE-169
> URL: https://issues.apache.org/jira/browse/EAGLE-169
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>
> The idea is to develop security event correlation platform for user to easily 
> onboard new metric and model metric correlation.
> Eagle project was invited to HackIllinois event https://www.hackillinois.org/
> Thanks Tyler Brown, Subasree Venkatsubhramaniyen, Yunsheng Wei to make this 
> Hackathon amazing ...
> Rest API : Tyler Browner (University of Missouri)
> Spout routing: Yunsheng Wei (Urbana-Champaign of Illinois University)
> Bolt dispatching: Subasree Venkatsubhramaniyen (University of 
> Wisconsin-Madison)
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61340204



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

[jira] [Created] (EAGLE-169) Dynamic security event correlation platform in Eagle

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-169:
--

 Summary: Dynamic security event correlation platform in Eagle
 Key: EAGLE-169
 URL: https://issues.apache.org/jira/browse/EAGLE-169
 Project: Eagle
  Issue Type: New Feature
Reporter: Edward Zhang
Assignee: Edward Zhang


The idea is to develop security event correlation platform for user to easily 
onboard new metric and model metric correlation.

Eagle project was invited to HackIllinois event https://www.hackillinois.org/
Thanks Tyler Brown, Subasree Venkatsubhramaniyen, Yunsheng Wei to make this 
Hackathon amazing ...
Rest API : Tyler Browner (University of Missouri)
Spout routing: Yunsheng Wei (Urbana-Champaign of Illinois University)
Bolt dispatching: Subasree Venkatsubhramaniyen (University of Wisconsin-Madison)

https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61340204



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

[jira] [Closed] (EAGLE-108) a tool tests performace between mongodb3.0 and couchDB1.6.1

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-108.
---
Resolution: Fixed

>  a tool   tests performace between mongodb3.0 and couchDB1.6.1
> --
>
> Key: EAGLE-108
> URL: https://issues.apache.org/jira/browse/EAGLE-108
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Malie
>Assignee: Su Ralph
>  Labels: eagle
>




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

[jira] [Reopened] (EAGLE-117) update Build Status Link and make it point to CI job building upon master

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-117:
-

re-opened to update "fix Version".

> update Build Status Link and make it point to CI job building upon master
> -
>
> Key: EAGLE-117
> URL: https://issues.apache.org/jira/browse/EAGLE-117
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> shall point to https://builds.apache.org/job/incubator-eagle-main/



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

[jira] [Reopened] (EAGLE-108) a tool tests performace between mongodb3.0 and couchDB1.6.1

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-108:
-

re-opened to update "fix Version".

>  a tool   tests performace between mongodb3.0 and couchDB1.6.1
> --
>
> Key: EAGLE-108
> URL: https://issues.apache.org/jira/browse/EAGLE-108
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Malie
>Assignee: Su Ralph
>  Labels: eagle
>




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

[jira] [Reopened] (EAGLE-85) Fix unit test failure.

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-85:


re-opened to update "fix Version".

> Fix unit test failure.
> --
>
> Key: EAGLE-85
> URL: https://issues.apache.org/jira/browse/EAGLE-85
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>




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

[jira] [Closed] (EAGLE-85) Fix unit test failure.

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-85.
--
Resolution: Fixed

> Fix unit test failure.
> --
>
> Key: EAGLE-85
> URL: https://issues.apache.org/jira/browse/EAGLE-85
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>




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

[jira] [Reopened] (EAGLE-70) Fix Goovy into Groovy in pom

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-70:


re-opened to update "fix Version".

> Fix Goovy into Groovy in pom
> 
>
> Key: EAGLE-70
> URL: https://issues.apache.org/jira/browse/EAGLE-70
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>




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

[jira] [Closed] (EAGLE-117) update Build Status Link and make it point to CI job building upon master

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-117.
---
Resolution: Fixed

> update Build Status Link and make it point to CI job building upon master
> -
>
> Key: EAGLE-117
> URL: https://issues.apache.org/jira/browse/EAGLE-117
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> shall point to https://builds.apache.org/job/incubator-eagle-main/



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

[jira] [Updated] (EAGLE-85) Fix unit test failure.

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri updated EAGLE-85:
---
Fix Version/s: 0.3.0

> Fix unit test failure.
> --
>
> Key: EAGLE-85
> URL: https://issues.apache.org/jira/browse/EAGLE-85
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>




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

[jira] [Closed] (EAGLE-70) Fix Goovy into Groovy in pom

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-70.
--
Resolution: Fixed

> Fix Goovy into Groovy in pom
> 
>
> Key: EAGLE-70
> URL: https://issues.apache.org/jira/browse/EAGLE-70
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>




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

[jira] [Updated] (EAGLE-70) Fix Goovy into Groovy in pom

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri updated EAGLE-70:
---
Fix Version/s: 0.3.0

> Fix Goovy into Groovy in pom
> 
>
> Key: EAGLE-70
> URL: https://issues.apache.org/jira/browse/EAGLE-70
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>




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

[jira] [Closed] (EAGLE-117) update Build Status Link and make it point to CI job building upon master

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-117.
---
   Resolution: Fixed
Fix Version/s: 0.3.0

> update Build Status Link and make it point to CI job building upon master
> -
>
> Key: EAGLE-117
> URL: https://issues.apache.org/jira/browse/EAGLE-117
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: 0.3.0
>
>
> shall point to https://builds.apache.org/job/incubator-eagle-main/



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

[jira] [Closed] (EAGLE-108) a tool tests performace between mongodb3.0 and couchDB1.6.1

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-108.
---
   Resolution: Fixed
Fix Version/s: 0.3.0

>  a tool   tests performace between mongodb3.0 and couchDB1.6.1
> --
>
> Key: EAGLE-108
> URL: https://issues.apache.org/jira/browse/EAGLE-108
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Malie
>Assignee: Su Ralph
>  Labels: eagle
> Fix For: 0.3.0
>
>




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

[jira] [Reopened] (EAGLE-108) a tool tests performace between mongodb3.0 and couchDB1.6.1

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-108:
-

re-opened to update "fix Version".

>  a tool   tests performace between mongodb3.0 and couchDB1.6.1
> --
>
> Key: EAGLE-108
> URL: https://issues.apache.org/jira/browse/EAGLE-108
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Malie
>Assignee: Su Ralph
>  Labels: eagle
> Fix For: 0.3.0
>
>




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

[jira] [Reopened] (EAGLE-117) update Build Status Link and make it point to CI job building upon master

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-117:
-

re-opened to update "fix Version".

> update Build Status Link and make it point to CI job building upon master
> -
>
> Key: EAGLE-117
> URL: https://issues.apache.org/jira/browse/EAGLE-117
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: 0.3.0
>
>
> shall point to https://builds.apache.org/job/incubator-eagle-main/



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

[jira] [Reopened] (EAGLE-74) in sandbox setup, change package name from eagle. to org.apache.eagle

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-74:


re-opened to update "fix Version".

> in sandbox setup, change package name from eagle. to org.apache.eagle
> -
>
> Key: EAGLE-74
> URL: https://issues.apache.org/jira/browse/EAGLE-74
> Project: Eagle
>  Issue Type: Bug
>Reporter: Edward Zhang
>Assignee: Zhao, Qingwen
>
> http://eagle.incubator.apache.org/docs/deployment-in-sandbox.html
> log4j.appender.KAFKA_HDFS_AUDIT=eagle.log4j.kafka.KafkaLog4jAppender should 
> be renamed package to prefixed by org.apache.



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

[jira] [Closed] (EAGLE-74) in sandbox setup, change package name from eagle. to org.apache.eagle

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-74.
--
   Resolution: Fixed
Fix Version/s: 0.3.0

> in sandbox setup, change package name from eagle. to org.apache.eagle
> -
>
> Key: EAGLE-74
> URL: https://issues.apache.org/jira/browse/EAGLE-74
> Project: Eagle
>  Issue Type: Bug
>Reporter: Edward Zhang
>Assignee: Zhao, Qingwen
> Fix For: 0.3.0
>
>
> http://eagle.incubator.apache.org/docs/deployment-in-sandbox.html
> log4j.appender.KAFKA_HDFS_AUDIT=eagle.log4j.kafka.KafkaLog4jAppender should 
> be renamed package to prefixed by org.apache.



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

[jira] [Reopened] (EAGLE-24) Load skew issue when partition by user

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-24:


re-opened to update "fix Version".

> Load skew issue when partition by user
> --
>
> Key: EAGLE-24
> URL: https://issues.apache.org/jira/browse/EAGLE-24
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Libin, Sun
>Assignee: Libin, Sun
>
> Today hdfs audit log/hive query log events are partitioned by user field and 
> pass all the way from source to spouts, bolts
> But due to the existence of heavy user, the load of spout/bolt are skewed, 
> especially for alert executors which may be computing/memory intensive
> We need to resolve this by dynamic partition events based on spout/bolt 
> capacity



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

[jira] [Closed] (EAGLE-24) Load skew issue when partition by user

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-24.
--
   Resolution: Fixed
Fix Version/s: 0.3.0

> Load skew issue when partition by user
> --
>
> Key: EAGLE-24
> URL: https://issues.apache.org/jira/browse/EAGLE-24
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Libin, Sun
>Assignee: Libin, Sun
> Fix For: 0.3.0
>
>
> Today hdfs audit log/hive query log events are partitioned by user field and 
> pass all the way from source to spouts, bolts
> But due to the existence of heavy user, the load of spout/bolt are skewed, 
> especially for alert executors which may be computing/memory intensive
> We need to resolve this by dynamic partition events based on spout/bolt 
> capacity



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

[jira] [Reopened] (EAGLE-58) Enhance Hive query parse model

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-58:


re-opened to update "fix Version".

> Enhance Hive query parse model 
> ---
>
> Key: EAGLE-58
> URL: https://issues.apache.org/jira/browse/EAGLE-58
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> 1) support create/drop/alert tableName parsing
> 2) enhance selectExpr parsing



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

[jira] [Closed] (EAGLE-58) Enhance Hive query parse model

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-58.
--
   Resolution: Fixed
Fix Version/s: 0.3.0

> Enhance Hive query parse model 
> ---
>
> Key: EAGLE-58
> URL: https://issues.apache.org/jira/browse/EAGLE-58
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: 0.3.0
>
>
> 1) support create/drop/alert tableName parsing
> 2) enhance selectExpr parsing



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

[jira] [Reopened] (EAGLE-55) JobCompletedConfigServiceURLBuilderImpl in hive running spout miss anonymous paramter

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-55:


re-opened to update "fix Version".

> JobCompletedConfigServiceURLBuilderImpl in hive running spout miss anonymous 
> paramter
> -
>
> Key: EAGLE-55
> URL: https://issues.apache.org/jira/browse/EAGLE-55
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Libin, Sun
>Assignee: Zhao, Qingwen
>
> JobCompletedConfigServiceURLBuilderImpl  miss anonymous pararmter, should add 
> "?anonymous=true"



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

[jira] [Reopened] (EAGLE-48) Alert message time is wrong in some cases

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-48:


re-opened to update "fix Version".

> Alert message time is wrong in some cases
> -
>
> Key: EAGLE-48
> URL: https://issues.apache.org/jira/browse/EAGLE-48
> Project: Eagle
>  Issue Type: Bug
> Environment: hortonworrks sandbox
>Reporter: Zhao, Qingwen
>
> Today I test HDFS security log topology, and create a policy “hdfs security"
> from hdfsSecurityLogEventStream[(allowed == false) and (user == 
> 'hbase')]#window.externalTime(timestamp,10 min) select user, count(timestamp) 
> as aggValue group by user having aggValue >= 2 insert into outputStream;
> And found the alert message time is always 1970-01-01 00:00:00[UTC]. The 
> importing log is 
> 2015-11-18 08:41:10,200 INFO 
> SecurityLogger.org.apache.hadoop.security.authorize.ServiceAuthorizationManager:
>  Authorization failed for hbase (auth:SIMPLE) for protocol=interface 
> org.apache.hadoop.hdfs.protocol.ClientProtocol
> Check the parsing code, found no problem. Then I create another testing 
> policy “testAnother"
> from hdfsSecurityLogEventStream[(allowed == false) and (user == 'hbase')] 
> select * insert into outputStream;
> This time the message time is OK. 



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

[jira] [Closed] (EAGLE-55) JobCompletedConfigServiceURLBuilderImpl in hive running spout miss anonymous paramter

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-55.
--
   Resolution: Fixed
Fix Version/s: 0.3.0

> JobCompletedConfigServiceURLBuilderImpl in hive running spout miss anonymous 
> paramter
> -
>
> Key: EAGLE-55
> URL: https://issues.apache.org/jira/browse/EAGLE-55
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Libin, Sun
>Assignee: Zhao, Qingwen
> Fix For: 0.3.0
>
>
> JobCompletedConfigServiceURLBuilderImpl  miss anonymous pararmter, should add 
> "?anonymous=true"



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

[jira] [Closed] (EAGLE-125) Add LICENSE in eagle external

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-125.
---
   Resolution: Fixed
Fix Version/s: 0.3.0

> Add LICENSE in eagle external
> -
>
> Key: EAGLE-125
> URL: https://issues.apache.org/jira/browse/EAGLE-125
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Zhaokun Qin
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> When use: mvn clean install -DskipTests to compile source code, There are 
> ERRORs due to LICENSE missing.



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

[jira] [Reopened] (EAGLE-125) Add LICENSE in eagle external

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-125:
-

re-opened to update "fix Version".

> Add LICENSE in eagle external
> -
>
> Key: EAGLE-125
> URL: https://issues.apache.org/jira/browse/EAGLE-125
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Zhaokun Qin
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> When use: mvn clean install -DskipTests to compile source code, There are 
> ERRORs due to LICENSE missing.



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

[jira] [Closed] (EAGLE-48) Alert message time is wrong in some cases

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-48.
--
   Resolution: Fixed
Fix Version/s: 0.3.0

> Alert message time is wrong in some cases
> -
>
> Key: EAGLE-48
> URL: https://issues.apache.org/jira/browse/EAGLE-48
> Project: Eagle
>  Issue Type: Bug
> Environment: hortonworrks sandbox
>Reporter: Zhao, Qingwen
> Fix For: 0.3.0
>
>
> Today I test HDFS security log topology, and create a policy “hdfs security"
> from hdfsSecurityLogEventStream[(allowed == false) and (user == 
> 'hbase')]#window.externalTime(timestamp,10 min) select user, count(timestamp) 
> as aggValue group by user having aggValue >= 2 insert into outputStream;
> And found the alert message time is always 1970-01-01 00:00:00[UTC]. The 
> importing log is 
> 2015-11-18 08:41:10,200 INFO 
> SecurityLogger.org.apache.hadoop.security.authorize.ServiceAuthorizationManager:
>  Authorization failed for hbase (auth:SIMPLE) for protocol=interface 
> org.apache.hadoop.hdfs.protocol.ClientProtocol
> Check the parsing code, found no problem. Then I create another testing 
> policy “testAnother"
> from hdfsSecurityLogEventStream[(allowed == false) and (user == 'hbase')] 
> select * insert into outputStream;
> This time the message time is OK. 



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

[jira] [Reopened] (EAGLE-7) expose storm config as individual eagle topology config

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-7:
---

re-opened to update "fix Version".

> expose storm config as individual eagle topology config
> ---
>
> Key: EAGLE-7
> URL: https://issues.apache.org/jira/browse/EAGLE-7
> Project: Eagle
>  Issue Type: Improvement
> Environment: production linux
>Reporter: Edward Zhang
>Assignee: Zhao, Qingwen
> Fix For: 0.3.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Storm has many configurations which can be configured through storm.yaml, and 
> those configurations are actually can be per topology. Eagle should have a 
> capability to expose all the configurations through Eagle configuration. Some 
> examples are 
> topology.acker.executors: 2
> topology.tasks: 8 
> topology.max.spout.pending: 1000
> topology.executor.receive.buffer.size: 16384
> topology.executor.send.buffer.size: 16384
> Today we only have parallelism of bolt/spout can be configured through eagle 
> configuration.



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

[jira] [Closed] (EAGLE-7) expose storm config as individual eagle topology config

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-7.
-
   Resolution: Fixed
Fix Version/s: 0.3.0

> expose storm config as individual eagle topology config
> ---
>
> Key: EAGLE-7
> URL: https://issues.apache.org/jira/browse/EAGLE-7
> Project: Eagle
>  Issue Type: Improvement
> Environment: production linux
>Reporter: Edward Zhang
>Assignee: Zhao, Qingwen
> Fix For: 0.3.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Storm has many configurations which can be configured through storm.yaml, and 
> those configurations are actually can be per topology. Eagle should have a 
> capability to expose all the configurations through Eagle configuration. Some 
> examples are 
> topology.acker.executors: 2
> topology.tasks: 8 
> topology.max.spout.pending: 1000
> topology.executor.receive.buffer.size: 16384
> topology.executor.send.buffer.size: 16384
> Today we only have parallelism of bolt/spout can be configured through eagle 
> configuration.



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

[jira] [Reopened] (EAGLE-4) configure parallelism with bolt/spout friendly name

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-4:
---

re-opened to update "fix Version".

> configure parallelism with bolt/spout friendly name
> ---
>
> Key: EAGLE-4
> URL: https://issues.apache.org/jira/browse/EAGLE-4
> Project: Eagle
>  Issue Type: Bug
> Environment: production
>Reporter: Edward Zhang
>Assignee: Zhao, Qingwen
>Priority: Minor
> Fix For: 0.3.0
>
>
> In order to define parallelism for each spout/bolt, we should use friendly 
> name. Today normally Eagle API does not require bolt name is provided, but to 
> define parallelism, we have to use a friendly name.
> An alternative is to use rebalance command like bin/storm rebalance 
> apollo-phx-hdfsAuditLog-topology -n 10 -e kafkaMsgConsumer=1 -e 
> FileSensitivityDataJoinExecutor_2=1 -e JavaStormExecutorForAlertWrapper_5=1 
> -e hdfsAuditLogAlertExecutor_0=1
> But the best is to provide a way of defining parallelism in configuration file
> "parallelismConfig" : {
>   "kafkaMsgConsumer" : 2,
>   "FileSensitivityDataJoinExecutor_2" : 2,
>   "hdfsAuditLogAlertExecutor*" : 1
> }



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

[jira] [Closed] (EAGLE-4) configure parallelism with bolt/spout friendly name

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-4.
-
   Resolution: Fixed
Fix Version/s: 0.3.0

> configure parallelism with bolt/spout friendly name
> ---
>
> Key: EAGLE-4
> URL: https://issues.apache.org/jira/browse/EAGLE-4
> Project: Eagle
>  Issue Type: Bug
> Environment: production
>Reporter: Edward Zhang
>Assignee: Zhao, Qingwen
>Priority: Minor
> Fix For: 0.3.0
>
>
> In order to define parallelism for each spout/bolt, we should use friendly 
> name. Today normally Eagle API does not require bolt name is provided, but to 
> define parallelism, we have to use a friendly name.
> An alternative is to use rebalance command like bin/storm rebalance 
> apollo-phx-hdfsAuditLog-topology -n 10 -e kafkaMsgConsumer=1 -e 
> FileSensitivityDataJoinExecutor_2=1 -e JavaStormExecutorForAlertWrapper_5=1 
> -e hdfsAuditLogAlertExecutor_0=1
> But the best is to provide a way of defining parallelism in configuration file
> "parallelismConfig" : {
>   "kafkaMsgConsumer" : 2,
>   "FileSensitivityDataJoinExecutor_2" : 2,
>   "hdfsAuditLogAlertExecutor*" : 1
> }



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

[jira] [Closed] (EAGLE-62) Add jshint for front end UI building

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-62.
--
   Resolution: Fixed
Fix Version/s: 0.3.0

> Add jshint for front end UI building
> 
>
> Key: EAGLE-62
> URL: https://issues.apache.org/jira/browse/EAGLE-62
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Minor
> Fix For: 0.3.0
>
>
> Currently use grunt for front-end building. Add jshint for code check.



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

[jira] [Reopened] (EAGLE-62) Add jshint for front end UI building

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-62:


re-opened to update "fix Version".

> Add jshint for front end UI building
> 
>
> Key: EAGLE-62
> URL: https://issues.apache.org/jira/browse/EAGLE-62
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Minor
> Fix For: 0.3.0
>
>
> Currently use grunt for front-end building. Add jshint for code check.



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

[jira] [Closed] (EAGLE-28) Znode root should be configurable.

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri closed EAGLE-28.
--
   Resolution: Fixed
Fix Version/s: 0.3.0

> Znode root should be configurable.   
> -
>
> Key: EAGLE-28
> URL: https://issues.apache.org/jira/browse/EAGLE-28
> Project: Eagle
>  Issue Type: Bug
> Environment: Production
>Reporter: hemanth dendukuri
>Assignee: Zhao, Qingwen
>Priority: Minor
> Fix For: 0.3.0
>
>
> deployed eagle topology storm cluster and encountered below issues 
> java.lang.RuntimeException: java.lang.RuntimeException: 
> org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = 
> NoNode for /brokers/topics/sandbox_hdfs_audit_log/partitions
> at 
> storm.kafka.DynamicBrokersReader.getBrokerInfo(DynamicBrokersReader.java:81) 
> ~[stormjar.jar:na]
> Topic was created under 
> /DAMKafka/brokers/topics/sandbox_hdfs_audit_log/partitions.
> We need an option to provide zookeeper “Znode” root in 
> config(sandbox-hdfsAuditLog-application.conf)



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

[jira] [Reopened] (EAGLE-28) Znode root should be configurable.

[hemanth dendukuri (JIRA)]

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

hemanth dendukuri reopened EAGLE-28:


re-opened to update "fix Version".

> Znode root should be configurable.   
> -
>
> Key: EAGLE-28
> URL: https://issues.apache.org/jira/browse/EAGLE-28
> Project: Eagle
>  Issue Type: Bug
> Environment: Production
>Reporter: hemanth dendukuri
>Assignee: Zhao, Qingwen
>Priority: Minor
> Fix For: 0.3.0
>
>
> deployed eagle topology storm cluster and encountered below issues 
> java.lang.RuntimeException: java.lang.RuntimeException: 
> org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = 
> NoNode for /brokers/topics/sandbox_hdfs_audit_log/partitions
> at 
> storm.kafka.DynamicBrokersReader.getBrokerInfo(DynamicBrokersReader.java:81) 
> ~[stormjar.jar:na]
> Topic was created under 
> /DAMKafka/brokers/topics/sandbox_hdfs_audit_log/partitions.
> We need an option to provide zookeeper “Znode” root in 
> config(sandbox-hdfsAuditLog-application.conf)



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

Creating a Release Branch.

[Dendukuri, Hemanth]

 Hi All,

 I am creating a release branch in git.  Please hold off any 
commits until this is finished.

Regards
Hemanth

[jira] [Commented] (EAGLE-103) add comments to readme to tell users: currently, eagle is tested under jdk1.7.x, may have compile error with jdk1.8.x

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-103:
--

GitHub user hdendukuri opened a pull request:

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

EAGLE-103 Updated Read me for Java jdk compatibility.

Updated Read me for Java jdk compatibility.
https://issues.apache.org/jira/browse/EAGLE-103

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

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

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

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






> add comments to readme to tell users: currently, eagle is tested under 
> jdk1.7.x, may have compile error with jdk1.8.x
> -
>
> Key: EAGLE-103
> URL: https://issues.apache.org/jira/browse/EAGLE-103
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Michael Wu
>Assignee: Hao Chen
>Priority: Minor
>
> Compilation error found while building with JDK1.8.x (refer to 
> https://issues.apache.org/jira/browse/EAGLE-101).
> I think we should update the required version of jdk in readme file of the 
> project.



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

[GitHub] incubator-eagle pull request: EAGLE-103 Updated Read me for Java j...

[hdendukuri]

GitHub user hdendukuri opened a pull request:

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

EAGLE-103 Updated Read me for Java jdk compatibility.

Updated Read me for Java jdk compatibility.
https://issues.apache.org/jira/browse/EAGLE-103

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

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

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

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






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

Re: Creating a Release Branch.

[Dendukuri, Hemanth]

I was able to create branch 
branch-0.3.0
 https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=summary

Please resume your commits.


From: "Dendukuri, Hemanth" mailto:hdenduk...@ebay.com>>
Date: Monday, February 22, 2016 at 2:56 PM
To: "dev@eagle.incubator.apache.org" 
mailto:dev@eagle.incubator.apache.org>>
Subject: Creating a Release Branch.

 Hi All,

 I am creating a release branch in git.  Please hold off any 
commits until this is finished.

Regards
Hemanth

[GitHub] incubator-eagle pull request: Eagle -168 - AlertEmail Initializati...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Eagle -168 - AlertEmail Initializati...

[RalphSu]

Github user RalphSu commented on the pull request:

https://github.com/apache/incubator-eagle/pull/101#issuecomment-187479574
  
Merged, with a fix of the assembly.xml


---
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-168) Notification Plugin AlertEmailPlugin Error

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-168:
---
Fix Version/s: 0.3.0

> Notification Plugin AlertEmailPlugin Error
> --
>
> Key: EAGLE-168
> URL: https://issues.apache.org/jira/browse/EAGLE-168
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Senthilkumar
>Assignee: Senthilkumar
> Fix For: 0.3.0
>
>
> Alert Email Plugin Initialization failed .
> com.typesafe.config.ConfigException$Missing: No configuration setting found 
> for key 'eagleProps'
> at 
> com.typesafe.config.impl.SimpleConfig.findKey(SimpleConfig.java:124) 
> ~[stormjar.jar:na]
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:145) 
> ~[stormjar.jar:na]
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:159) 
> ~[stormjar.jar:na]
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:164) 
> ~[stormjar.jar:na]
> at 
> com.typesafe.config.impl.SimpleConfig.getObject(SimpleConfig.java:218) 
> ~[stormjar.jar:



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

[jira] [Commented] (EAGLE-168) Notification Plugin AlertEmailPlugin Error

[Su Ralph (JIRA)]

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

Su Ralph commented on EAGLE-168:


Merged.

> Notification Plugin AlertEmailPlugin Error
> --
>
> Key: EAGLE-168
> URL: https://issues.apache.org/jira/browse/EAGLE-168
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Senthilkumar
>Assignee: Senthilkumar
> Fix For: 0.3.0
>
>
> Alert Email Plugin Initialization failed .
> com.typesafe.config.ConfigException$Missing: No configuration setting found 
> for key 'eagleProps'
> at 
> com.typesafe.config.impl.SimpleConfig.findKey(SimpleConfig.java:124) 
> ~[stormjar.jar:na]
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:145) 
> ~[stormjar.jar:na]
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:159) 
> ~[stormjar.jar:na]
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:164) 
> ~[stormjar.jar:na]
> at 
> com.typesafe.config.impl.SimpleConfig.getObject(SimpleConfig.java:218) 
> ~[stormjar.jar:



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

[GitHub] incubator-eagle pull request: EAGLE-164 add a missing license in a...

[qingwen220]

Github user qingwen220 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/96#issuecomment-187481896
  
Have been fixed in another pr, and this one will be closed


---
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: EAGLE-164 add a missing license in a...

[qingwen220]

Github user qingwen220 closed the pull request at:

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


---
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-164) Tutorial for setting up the development environment on mac

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-164:
--

Github user qingwen220 closed the pull request at:

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


> Tutorial for setting up the development environment on mac
> --
>
> Key: EAGLE-164
> URL: https://issues.apache.org/jira/browse/EAGLE-164
> Project: Eagle
>  Issue Type: Task
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Zhao, Qingwen
> Fix For: 0.3.0
>
>




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

[jira] [Commented] (EAGLE-164) Tutorial for setting up the development environment on mac

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-164:
--

Github user qingwen220 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/96#issuecomment-187481896
  
Have been fixed in another pr, and this one will be closed


> Tutorial for setting up the development environment on mac
> --
>
> Key: EAGLE-164
> URL: https://issues.apache.org/jira/browse/EAGLE-164
> Project: Eagle
>  Issue Type: Task
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Zhao, Qingwen
> Fix For: 0.3.0
>
>




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

[jira] [Closed] (EAGLE-164) Tutorial for setting up the development environment on mac

[Zhao, Qingwen (JIRA)]

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

Zhao, Qingwen closed EAGLE-164.
---
Resolution: Fixed

> Tutorial for setting up the development environment on mac
> --
>
> Key: EAGLE-164
> URL: https://issues.apache.org/jira/browse/EAGLE-164
> Project: Eagle
>  Issue Type: Task
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Zhao, Qingwen
> Fix For: 0.3.0
>
>




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