[jira] [Created] (EAGLE-1104) Eagle 1.0 preparation

2020-04-18 Thread Edward Zhang (Jira) 
Edward Zhang created EAGLE-1104:
---

 Summary: Eagle 1.0 preparation
 Key: EAGLE-1104
 URL: https://issues.apache.org/jira/browse/EAGLE-1104
 Project: Eagle
  Issue Type: New Feature
  Components: Core::Eagle Server
Affects Versions: 1.0
Reporter: Edward Zhang
Assignee: Edward Zhang


Here I want to propose Eagle 1.0, which targets for decoupling eagle 
applications from monitoring framework, which we had discussed long time ago.

This story is for preparation of Eagle 1.0 development.

- Create a small runnable application easily to start development from



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (EAGLE-1092) Start example app but it tries to retrieve data from Kafka due to incorrect config

2018-10-12 Thread Edward Zhang (JIRA) 


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

Edward Zhang commented on EAGLE-1092:
-

in class GuiceBundleLoader, 

Config config = ConfigFactory.load();

seemed have problem as it is dangerous that load configuration without 
specifying actual config file name but use config in classpath

> Start example app but it tries to retrieve data from Kafka due to incorrect 
> config
> --
>
> Key: EAGLE-1092
> URL: https://issues.apache.org/jira/browse/EAGLE-1092
> Project: Eagle
>  Issue Type: Bug
>  Components: Core::App Engine
>Reporter: Edward Zhang
>Assignee: Hao Chen
>Priority: Major
>
> Start eagle in local machine, and try to install/ru{color:#33}n Example 
> Monitor APP, but it also uses a random config which actually try to fetch 
> message from Kafka with topic {color}hbase_audit_log_parsed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EAGLE-1092) Start example app but it tries to retrieve data from Kafka due to incorrect config

2018-10-12 Thread Edward Zhang (JIRA) 


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

Edward Zhang commented on EAGLE-1092:
-

Another issue is because it uses default config, appid is wrong, for example 
example monitor application uses appid HBaseAuditLogApp. So localizing config 
seems important

> Start example app but it tries to retrieve data from Kafka due to incorrect 
> config
> --
>
> Key: EAGLE-1092
> URL: https://issues.apache.org/jira/browse/EAGLE-1092
> Project: Eagle
>  Issue Type: Bug
>  Components: Core::App Engine
>Reporter: Edward Zhang
>Assignee: Hao Chen
>Priority: Major
>
> Start eagle in local machine, and try to install/ru{color:#33}n Example 
> Monitor APP, but it also uses a random config which actually try to fetch 
> message from Kafka with topic {color}hbase_audit_log_parsed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EAGLE-1092) Start example app but it tries to retrieve data from Kafka due to incorrect config

2018-10-12 Thread Edward Zhang (JIRA) 


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

Edward Zhang commented on EAGLE-1092:
-

looks that is because the property dataSinkConfig.topic is not configured, so 
it uses the config which is in the classpath. That is dangerous, we should make 
sure each application only uses its own config

> Start example app but it tries to retrieve data from Kafka due to incorrect 
> config
> --
>
> Key: EAGLE-1092
> URL: https://issues.apache.org/jira/browse/EAGLE-1092
> Project: Eagle
>  Issue Type: Bug
>  Components: Core::App Engine
>Reporter: Edward Zhang
>Assignee: Hao Chen
>Priority: Major
>
> Start eagle in local machine, and try to install/ru{color:#33}n Example 
> Monitor APP, but it also uses a random config which actually try to fetch 
> message from Kafka with topic {color}hbase_audit_log_parsed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (EAGLE-1092) Start example app but it tries to retrieve data from Kafka due to incorrect config

2018-10-12 Thread Edward Zhang (JIRA) 


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

Edward Zhang updated EAGLE-1092:

Description: Start eagle in local machine, and try to 
install/ru{color:#33}n Example Monitor APP, but it also uses a random 
config which actually try to fetch message from Kafka with topic 
{color}hbase_audit_log_parsed.

> Start example app but it tries to retrieve data from Kafka due to incorrect 
> config
> --
>
> Key: EAGLE-1092
> URL: https://issues.apache.org/jira/browse/EAGLE-1092
> Project: Eagle
>  Issue Type: Bug
>  Components: Core::App Engine
>Reporter: Edward Zhang
>Assignee: Hao Chen
>Priority: Major
>
> Start eagle in local machine, and try to install/ru{color:#33}n Example 
> Monitor APP, but it also uses a random config which actually try to fetch 
> message from Kafka with topic {color}hbase_audit_log_parsed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (EAGLE-1092) Start example app but it tries to retrieve data from Kafka due to incorrect config

2018-10-12 Thread Edward Zhang (JIRA) 
Edward Zhang created EAGLE-1092:
---

 Summary: Start example app but it tries to retrieve data from 
Kafka due to incorrect config
 Key: EAGLE-1092
 URL: https://issues.apache.org/jira/browse/EAGLE-1092
 Project: Eagle
  Issue Type: Bug
  Components: Core::App Engine
Reporter: Edward Zhang
Assignee: Hao Chen






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (EAGLE-449) clean inner process alert engine code

2018-08-15 Thread Edward Zhang (JIRA) 


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

Edward Zhang resolved EAGLE-449.

Resolution: Fixed

resolved but not closed

> clean inner process alert engine code
> -
>
> Key: EAGLE-449
> URL: https://issues.apache.org/jira/browse/EAGLE-449
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Major
> Fix For: v0.5.1
>
>
> alert engine now is separated into a standalone storm topology, it is not 
> necessary to keep inner process alert engine



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EAGLE-1090) make merge-pr script python 3 compatible

2018-08-04 Thread Edward Zhang (JIRA) 


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

Edward Zhang commented on EAGLE-1090:
-

Sorry, my bad, the PR was actually merged a few weeks before, so we are safe to 
close this ticket

> make merge-pr script python 3 compatible
> 
>
> Key: EAGLE-1090
> URL: https://issues.apache.org/jira/browse/EAGLE-1090
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
>
> * use requests instead of urllib
>  * update print statements



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EAGLE-1090) make merge-pr script python 3 compatible

2018-08-03 Thread Edward Zhang (JIRA) 


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

Edward Zhang commented on EAGLE-1090:
-

I checked the code, it is actually not in master, but seemed it was system 
message. [~jhsenjaliya] are you able to merge this PR?

> make merge-pr script python 3 compatible
> 
>
> Key: EAGLE-1090
> URL: https://issues.apache.org/jira/browse/EAGLE-1090
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
>
> * use requests instead of urllib
>  * update print statements



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (EAGLE-215) Add hadoop metric monitoring tutorial and user guide documents

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-215.
--
Resolution: Fixed

the documents are in eagle web site, so close this jira

> Add hadoop metric monitoring tutorial and user guide documents
> --
>
> Key: EAGLE-215
> URL: https://issues.apache.org/jira/browse/EAGLE-215
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (EAGLE-396) Support for Sum/Count in Druid Query - System Metrics

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-396.
--
Resolution: Fixed

druid will not be supported in apache eagle, we should close this ticket

> Support for Sum/Count in Druid Query - System Metrics
> -
>
> Key: EAGLE-396
> URL: https://issues.apache.org/jira/browse/EAGLE-396
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.1
>Reporter: Senthilkumar
>Assignee: Senthilkumar
>Priority: Major
> Fix For: v0.3.1
>
>
> Support for Sum/Count in Druid Query - System Metrics



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (EAGLE-513) Add DataNodes usages Metrics in JMX Collector

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-513.
--
Resolution: Fixed

> Add DataNodes usages Metrics in JMX Collector
> -
>
> Key: EAGLE-513
> URL: https://issues.apache.org/jira/browse/EAGLE-513
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Senthilkumar
>Assignee: Senthilkumar
>Priority: Major
>
> Instead of Capacity check , Its better to track "DataNodes usages" Median 
> Values. As we won't hit 90% DFS utilisation before that will have More Jobs 
> failures because of DataNode Issues..
> So we should clear/Balance the Cluster effectively By tracking DataNode 
> Median. 95% Median would be Nice to Start. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (EAGLE-179) email generator code should be refactored

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-179.
--
Resolution: Fixed
  Assignee: Edward Zhang

Looked at the code, email generator was already refactored to be shared

> email generator code should be refactored
> -
>
> Key: EAGLE-179
> URL: https://issues.apache.org/jira/browse/EAGLE-179
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
>
> After notification plugin framework is done, we have 2 places where eagle 
> send email, we should refactor the code to have only one place handling email



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (EAGLE-279) Create Documentation for Sandbox Quick starter and JMX monitring

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-279.
--
Resolution: Fixed

based on comments, close this ticket

> Create Documentation for Sandbox Quick starter and JMX monitring
> 
>
> Key: EAGLE-279
> URL: https://issues.apache.org/jira/browse/EAGLE-279
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (EAGLE-135) Run Eagle in Spark Streaming

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-135.
--
Resolution: Fixed

based on comments, close this Jira ticket

> Run Eagle in Spark Streaming
> 
>
> Key: EAGLE-135
> URL: https://issues.apache.org/jira/browse/EAGLE-135
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhaokun Qin
>Assignee: Zhaokun Qin
>Priority: Minor
>  Labels: new
>
> Eagle can run in Storm for now, to achieve Cross-platform feature, Eagle must 
> run in other streaming process platforms. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (EAGLE-510) Refactor HDFS audit log parser

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-510.
--
Resolution: Fixed

PR merged, so close this ticket

> Refactor HDFS audit log parser
> --
>
> Key: EAGLE-510
> URL: https://issues.apache.org/jira/browse/EAGLE-510
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Peter Kim
>Priority: Minor
>
> The current HDFS audit log parser can be refactored by leveraging regex 
> instead of the substring methods it uses.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (EAGLE-334) clean user profile code in Eagle 0.5 and redesign in Eagle 0.6

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-334.
--
Resolution: Fixed

the code was already cleaned up, so close this ticket

> clean user profile code in Eagle 0.5 and redesign in Eagle 0.6
> --
>
> Key: EAGLE-334
> URL: https://issues.apache.org/jira/browse/EAGLE-334
> Project: Eagle
>  Issue Type: Task
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
>
> User profile is used for analyzing user behaviors and finding out anomaly in 
> real time through machine learning algorithms. We accumulated some experience 
> in machine learning and will redesign that in Eagle 0.6 and make it better 
> and useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (EAGLE-101) cannot compile eagle successfully with jdk1.8

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-101.
--
Resolution: Fixed

already fixed, need clean up this jira

> cannot compile eagle successfully with jdk1.8
> -
>
> Key: EAGLE-101
> URL: https://issues.apache.org/jira/browse/EAGLE-101
> Project: Eagle
>  Issue Type: Bug
> Environment: 1. mac
> 2. jenkins CI job
>Reporter: Michael Wu
>Assignee: H Lu
>Priority: Trivial
>  Time Spent: 48h
>  Remaining Estimate: 0h
>
> While using jdk1.8 to compile the project, there are constantly errors thrown 
> as  following:
> [INFO] --- maven-scala-plugin:2.15.0:compile (scala-compile-first) @ 
> eagle-stream-process-base ---
> [INFO] Checking for multiple versions of scala
> [WARNING]  Expected all dependencies to require Scala version: 2.10.0
> [WARNING]  org.apache.kafka:kafka_2.10:0.8.1.2.2.0.0-2041 requires scala 
> version: 2.10.4
> [WARNING] Multiple versions of scala libraries detected!
> [INFO] includes = [**/*.java,**/*.scala,]
> [INFO] excludes = []
> [INFO] 
> /Users/ziwu/test/incubator-eagle/eagle-core/eagle-data-process/eagle-stream-process-base/src/main/java:-1:
>  info: compiling
> [INFO] 
> /Users/ziwu/test/incubator-eagle/eagle-core/eagle-data-process/eagle-stream-process-base/src/main/scala:-1:
>  info: compiling
> [INFO] Compiling 17 source files to 
> /Users/ziwu/test/incubator-eagle/eagle-core/eagle-data-process/eagle-stream-process-base/target/classes
>  at 1451275265312
> [ERROR] error: error while loading CharSequence, class file 
> '/Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/lib/rt.jar(java/lang/CharSequence.class)'
>  is broken
> [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 10)
> [ERROR] error: error while loading AnnotatedElement, class file 
> '/Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/lib/rt.jar(java/lang/reflect/AnnotatedElement.class)'
>  is broken
> [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 76)
> [ERROR] error: error while loading ConcurrentMap, class file 
> '/Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/lib/rt.jar(java/util/concurrent/ConcurrentMap.class)'
>  is broken
> [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 61)
> [ERROR] three errors found
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Eagle Parent  SUCCESS [  0.494 
> s]
> [INFO] eagle core . SUCCESS [  0.012 
> s]
> [INFO] eagle-query-parent . SUCCESS [  0.099 
> s]
> [INFO] eagle-common ... SUCCESS [  2.992 
> s]
> [INFO] eagle-data-process-parent .. SUCCESS [  0.009 
> s]
> [INFO] eagle-stream-process-base .. FAILURE [  2.843 
> s]
> [INFO] eagle-embed-parent . SKIPPED
> [INFO] eagle-embed-server . SKIPPED
> [INFO] eagle-embed-hbase .. SKIPPED
> [INFO] eagle-antlr  SKIPPED
> [INFO] eagle-entity-base .. SKIPPED
> [INFO] eagle-client-base .. SKIPPED
> [INFO] eagle-alert-parent . SKIPPED
> [INFO] eagle-alert-base ... SKIPPED
> [INFO] eagle-metric ... SKIPPED
> [INFO] eagle-alert-process  SKIPPED
> [INFO] eagle-stream-process-api ... SKIPPED
> [INFO] eagle-job-common ... SKIPPED
> [INFO] eagle-storm-jobrunning-spout ... SKIPPED
> [INFO] eagle-query-base ... SKIPPED
> [INFO] eagle-storage-base . SKIPPED
> [INFO] eagle-storage-hbase  SKIPPED
> [INFO] eagle-service-base . SKIPPED
> [INFO] eagle-alert-service  SKIPPED
> [INFO] eagle-storage-jdbc . SKIPPED
> [INFO] eagle-machinelearning-parent ... SKIPPED
> [INFO] eagle-machinelearning-base . SKIPPED
> [INFO] eagle-security-parent .. SKIPPED
> [INFO] eagle-security-common .. SKIPPED
> [INFO] eagle-security-hbase-web ... SKIPPED
> [INFO] eagle-security-hive-web  SKIPPED
> [INFO] eagle-security-hdfs-web

[jira] [Closed] (EAGLE-490) KafkaStreamSink should not assume fixed field user to do partition

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang closed EAGLE-490.
--
Resolution: Not A Problem

I looked at the code, it is not the case anymore

> KafkaStreamSink should not assume fixed field user to do partition
> --
>
> Key: EAGLE-490
> URL: https://issues.apache.org/jira/browse/EAGLE-490
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Major
> Fix For: v0.5.1
>
>
> KafkaStreamSink assumes user as the field to do partition. This should be 
> configurable in application metadata file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EAGLE-490) KafkaStreamSink should not assume fixed field user to do partition

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang commented on EAGLE-490:


this is not the case now, we should close this jira

> KafkaStreamSink should not assume fixed field user to do partition
> --
>
> Key: EAGLE-490
> URL: https://issues.apache.org/jira/browse/EAGLE-490
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Major
> Fix For: v0.5.1
>
>
> KafkaStreamSink assumes user as the field to do partition. This should be 
> configurable in application metadata file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (EAGLE-985) Upgrade hbase dependency to 1.2.5

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang resolved EAGLE-985.

Resolution: Won't Fix

we need additional discussion about upgrading hbase, now close this Jira 

> Upgrade hbase dependency to 1.2.5
> -
>
> Key: EAGLE-985
> URL: https://issues.apache.org/jira/browse/EAGLE-985
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Fix For: v0.6.0
>
> Attachments: Screen Shot 2017-04-04 at 11.24.38 AM.png
>
>
> hbase 0.98.4 release is very old.
> There wouldn't be any new 0.98 release.
> We should upgrade to 1.2.5 which is the latest stable release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (EAGLE-1038) Support alertDuplication customization for each policy

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang resolved EAGLE-1038.
-
Resolution: Won't Fix

based on comments in the jira, close this jira

> Support alertDuplication customization for each policy 
> ---
>
> Key: EAGLE-1038
> URL: https://issues.apache.org/jira/browse/EAGLE-1038
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.1
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>Priority: Major
>
> Requirements
> * compatible with old versions
> * enable alertDuplication check for each policy 
> * optimize DefaultDeduplicator



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (EAGLE-332) Build failed to due to [EAGLE-325]

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang resolved EAGLE-332.

Resolution: Fixed

this was fixed based on comments in this jira

> Build failed to due to [EAGLE-325]
> --
>
> Key: EAGLE-332
> URL: https://issues.apache.org/jira/browse/EAGLE-332
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Priority: Major
>  Labels: build
> Fix For: v0.5.1
>
>
> When building codes on develop branch after [EAGLE-329] ??Dependency 
> incompatibility bug among jersey, asm and extcos under Java 8??, I get the 
> following errors:
> {quote}
> [ERROR] Failed to execute goal on project alert-assembly: Could not resolve 
> dependencies for project 
> org.apache.eagle:alert-assembly:jar:0.5.0-incubating-SNAPSHOT: The following 
> artifacts could not be resolved: org.apache.eagle:
> alert-coordinator:war:0.5.0-incubating-SNAPSHOT, 
> org.apache.eagle:alert-metadata-service:war:0.5.0-incubating-SNAPSHOT: 
> Failure to find 
> org.apache.eagle:alert-coordinator:war:0.5.0-incubating-SNAPSHOT in 
> http://repo.hortonworks.
> com/content/groups/public/ was cached in the local repository, resolution 
> will not be reattempted until the update interval of hdp has elapsed or 
> updates are forced -> [Help 1]
> {quote}
> It was introduced by EAGLE-325 which changed packaging type of 
> alert-coordinator and alert-metadata-service from *war* to *jar*, but 
> forgetted to update dependency in alert-assembly
> {code:xml}
> 
> org.apache.eagle
> alert-coordinator
> ${project.version}
> war 
> 
> 
> org.apache.eagle
> alert-metadata-service
> ${project.version}
> war 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (EAGLE-1088) Inconsistent method name

2018-08-02 Thread Edward Zhang (JIRA) 


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

Edward Zhang updated EAGLE-1088:

Affects Version/s: v0.5.1

> Inconsistent method name
> 
>
> Key: EAGLE-1088
> URL: https://issues.apache.org/jira/browse/EAGLE-1088
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.1
>Reporter: KuiLIU
>Assignee: Edward Zhang
>Priority: Major
>
> The following the method is named "find", but the method does not find 
> anything, just returns a boolean-variable 'this.matched'. Thus, rename method 
> as "isMatched" should be more clear than "find".
> {code:java}
> public boolean find() {
> return this.matched;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (EAGLE-1091) serialize exception while processing field which length more than 64k

2018-06-11 Thread Edward Zhang (JIRA) 


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

Edward Zhang reassigned EAGLE-1091:
---

Assignee: Edward Zhang

> serialize exception while processing field which length more than 64k
> -
>
> Key: EAGLE-1091
> URL: https://issues.apache.org/jira/browse/EAGLE-1091
> Project: Eagle
>  Issue Type: Bug
>  Components: Core::Alert Engine
>Affects Versions: v0.5.0, v0.5.1
>Reporter: zhiwen wang
>Assignee: Edward Zhang
>Priority: Major
>
> java.lang.AssertionError: java.io.UTFDataFormatException: encoded string too 
> long: 228413 bytes
>  at 
> com.google.common.io.ByteStreams$ByteArrayDataOutputStream.writeUTF(ByteStreams.java:530)
>  ~[stormjar.jar:?]
>  at 
> org.apache.eagle.alert.engine.serialization.impl.StringSerializer.serialize(StringSerializer.java:28)
>  ~[stormjar.jar:?]
>  at 
> org.apache.eagle.alert.engine.serialization.impl.StringSerializer.serialize(StringSerializer.java:25)
>  ~[stormjar.jar:?]
>  at 
> org.apache.eagle.alert.engine.serialization.impl.StreamEventSerializer.serialize(StreamEventSerializer.java:79)
>  ~[stormjar.jar:?]
>  at 
> org.apache.eagle.alert.engine.serialization.impl.PartitionedEventSerializerImpl.serialize(PartitionedEventSerializerImpl.java:74)
>  ~[stormjar.jar:?]
>  at 
> org.apache.eagle.alert.engine.serialization.impl.PartitionedEventSerializerImpl.serialize(PartitionedEventSerializerImpl.java:81)
>  ~[stormjar.jar:?]
>  at 
> org.apache.eagle.alert.engine.spout.SpoutOutputCollectorWrapper.emit(SpoutOutputCollectorWrapper.java:156)
>  ~[stormjar.jar:?]
>  at org.apache.storm.kafka.PartitionManager.next(PartitionManager.java:160) 
> ~[stormjar.jar:?]
>  at org.apache.storm.kafka.KafkaSpout.nextTuple(KafkaSpout.java:135) 
> ~[stormjar.jar:?]
>  at 
> org.apache.eagle.alert.engine.spout.CorrelationSpout.nextTuple(CorrelationSpout.java:174)
>  ~[stormjar.jar:?]
>  at 
> org.apache.storm.daemon.executor$fn__6505$fn__6520$fn__6551.invoke(executor.clj:651)
>  ~[storm-core-1.0.1.2.5.5.0-157.jar:1.0.1.2.5.5.0-157]
>  at org.apache.storm.util$async_loop$fn__554.invoke(util.clj:484) 
> [storm-core-1.0.1.2.5.5.0-157.jar:1.0.1.2.5.5.0-157]
>  at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
>  at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
> Caused by: java.io.UTFDataFormatException: encoded string too long: 228413 
> bytes
>  at java.io.DataOutputStream.writeUTF(DataOutputStream.java:364) 
> ~[?:1.8.0_131]
>  at java.io.DataOutputStream.writeUTF(DataOutputStream.java:323) 
> ~[?:1.8.0_131]
>  at 
> com.google.common.io.ByteStreams$ByteArrayDataOutputStream.writeUTF(ByteStreams.java:528)
>  ~[stormjar.jar:?]
>  ... 13 more



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (EAGLE-1088) Inconsistent method name

2018-05-28 Thread Edward Zhang (JIRA) 


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

Edward Zhang reassigned EAGLE-1088:
---

Assignee: Edward Zhang

> Inconsistent method name
> 
>
> Key: EAGLE-1088
> URL: https://issues.apache.org/jira/browse/EAGLE-1088
> Project: Eagle
>  Issue Type: Improvement
>Reporter: KuiLIU
>Assignee: Edward Zhang
>Priority: Major
>
> The following the method is named "find", but the method does not find 
> anything, just returns a boolean-variable 'this.matched'. Thus, rename method 
> as "isMatched" should be more clear than "find".
> {code:java}
> public boolean find() {
> return this.matched;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EAGLE-251) Run eagle on flink/samza

2017-12-13 Thread Edward Zhang (JIRA) 

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

Edward Zhang commented on EAGLE-251:


[~ralphsu] looks with Flink we can't achieve equivalent feature for example 
dynamic adding/updating policies as Eagle did on top of Storm. For each new 
policy, with Flink we have to restart the flink job?

> Run eagle on flink/samza
> 
>
> Key: EAGLE-251
> URL: https://issues.apache.org/jira/browse/EAGLE-251
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Priority: Minor
>  Labels: new
>
> Eagle is running on storm. One might want to do some interesting port to 
> other stream framework like flink/samza.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (EAGLE-985) Upgrade hbase dependency to 1.2.5

2017-04-04 Thread Edward Zhang (JIRA) 

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

Edward Zhang commented on EAGLE-985:


Added. Thanks Ted.

> Upgrade hbase dependency to 1.2.5
> -
>
> Key: EAGLE-985
> URL: https://issues.apache.org/jira/browse/EAGLE-985
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: Screen Shot 2017-04-04 at 11.24.38 AM.png
>
>
> hbase 0.98.4 release is very old.
> There wouldn't be any new 0.98 release.
> We should upgrade to 1.2.5 which is the latest stable release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (EAGLE-985) Upgrade hbase dependency to 1.2.5

2017-04-04 Thread Edward Zhang (JIRA) 

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

Edward Zhang reassigned EAGLE-985:
--

Assignee: Ted Yu

> Upgrade hbase dependency to 1.2.5
> -
>
> Key: EAGLE-985
> URL: https://issues.apache.org/jira/browse/EAGLE-985
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: Screen Shot 2017-04-04 at 11.24.38 AM.png
>
>
> hbase 0.98.4 release is very old.
> There wouldn't be any new 0.98 release.
> We should upgrade to 1.2.5 which is the latest stable release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)