[jira] [Commented] (EAGLE-235) org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions for property "alertContext"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-235:
--

Github user asfgit closed the pull request at:

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


> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext"
> -
>
> Key: EAGLE-235
> URL: https://issues.apache.org/jira/browse/EAGLE-235
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> {code}
> java.io.IOException: Service side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> {code}



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

[GitHub] incubator-eagle pull request: Bug fix for dependency conflict and ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: issue about eagle

[Hao Chen]

The related bugs has been fixed in the latest patch on master branch:
https://github.com/apache/incubator-eagle/commit/60325aa2fccc81d47a3f2e27799bb697a6b06381

Could you please kindly download the latest code and retry?

- Hao

On Mon, Apr 11, 2016 at 10:54 PM, Hao Chen  wrote:

> Hi Ju,
>
> It's a known issue and has been resolved in
> https://github.com/apache/incubator-eagle/pull/142, please kindly be
> patient for us to review and merge the fix into master branch by end of
> tomorrow.
>
> - Hao
>
> On Mon, Apr 11, 2016 at 3:27 PM, Hao Chen  wrote:
>
>> Hi Jun,
>>
>> Thanks very much for reporting the issues, this problem is recently
>> included by some patches, and I am dedicatedly following the problem. Will
>> keep you update with the status ASAP.
>>
>> - Hao
>>
>>
>> On Wed, Apr 6, 2016 at 9:45 PM, He Ju(上海_技术部_架构部_大数据平台_何惧) 
>> wrote:
>>
>>> Hi,
>>>  I had setup Apache Eagle, but I can’t get alert even if I had
>>> configure policies like: from hdfsAuditLogEventStream[(src == ‘/test’)]
>>> select * insert into outputStrem;
>>> And  I use command “Hadoop fs –ls /test” to create the access log of
>>> hdfs .
>>>
>>> Where is the creation of table EAGLE_METRIC(created by Derby or Hbase?),
>>> and where to create the column like “ SITE  APPLICATION   POLICYID
>>>  ALERTEXECUTORID   SOURCE  PARTITIONSEQ” and et in table EAGLE_METRIC.
>>>
>>> Could someone give some response? Thanks in advanced.
>>>
>>>
>>> Sincerely
>>>
>>> 何惧 Joe He
>>> Sr. Architect, Architecture-Fundation, Tech Dept
>>> +86-18017743950
>>> Floor 3, 295 ZUCHONGZHI RD, Zhangjiang, Shanghai (201203)
>>>
>>>
>>
>

[Dev Tools] Added some development tools under: https://github.com/apache/incubator-eagle/tree/master/eagle-devsupport

[Hao Chen]

Added some development tools under:
https://github.com/apache/incubator-eagle/tree/master/eagle-devsupport

Hope to setup/resetup local development/example environment very quickyly:

The step (example) is:

*git clone https://github.com/apache/incubator-eagle.git
*

*cd incubator-eagle*
*eagle-examples/eagle-cassandra-example/bin/quick-start.sh*

Then the zk, kafka, webservice and topology will be running.

To trigger a alert, just execute:


*eagle-examples/eagle-cassandra-example/bin/send-sample-querylog.sh*

Then the alert could be found in topology log and also ui.

More information:

   - Example:
   
https://github.com/apache/incubator-eagle/tree/master/eagle-examples/eagle-cassandra-example
   - DevTools:
   https://github.com/apache/incubator-eagle/tree/master/eagle-devsupport


- Hao

Re: Change project version in master branch to "0.4.0-SNAPSHOT" since "v0.3.0" has been released.

[Hao Chen]

Yes, actually i am working on a document for releasing process.

- Hao

On Tue, Apr 12, 2016 at 2:05 PM, Liangfei.Su  wrote:

> Thanks, next time we might include change the project version as part of
> our release steps :)
>
> On Tue, Apr 12, 2016 at 1:42 PM, Hao Chen  wrote:
>
> > I will change project version in mater branch to "0.4.0-SNAPSHOT" by end
> of
> > tomorrow, since "v0.3.0" has been released.
> > https://issues.apache.org/jira/browse/EAGLE-236
> >
> > Please be noticed that if you have some work in progress, especially if
> > they have conflicts.
> >
> > - Hao
> >
>

[jira] [Resolved] (EAGLE-240) java.lang.ArrayIndexOutOfBoundsException thrown by MetricKeyCodeDecoder

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-240.

Resolution: Fixed

Fixed with 
https://github.com/apache/incubator-eagle/pull/142/commits/bb9ea0aa37164198566ea42f161464f13bbe2d36

> java.lang.ArrayIndexOutOfBoundsException thrown by MetricKeyCodeDecoder
> ---
>
> Key: EAGLE-240
> URL: https://issues.apache.org/jira/browse/EAGLE-240
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: policy-engine
>
> {code}
> 2016-04-12 12:56:43,491 ERROR [Thread-18-cassandraQueryLogExecutor_0] 
> executor.PolicyProcessExecutor[336]: cassandraQueryLogExecutor, partition 0, 
> error fetching alerts, but continue to run 
> java.lang.ArrayIndexOutOfBoundsException: 1 at 
> org.apache.eagle.metric.reportor.MetricKeyCodeDecoder.decodeMetricKey(MetricKeyCodeDecoder.java:45)
>   at 
> org.apache.eagle.metric.reportor.MetricKeyCodeDecoder.decodeTSMetricKey(MetricKeyCodeDecoder.java:60)
> at 
> org.apache.eagle.metric.reportor.MetricEntityAdaptor.convert(MetricEntityAdaptor.java:29)
> at 
> org.apache.eagle.metric.reportor.EagleServiceReporterMetricListener.onMetricFlushed(EagleServiceReporterMetricListener.java:48)
>   at 
> org.apache.eagle.metric.reportor.EagleCounterMetric.flush(EagleCounterMetric.java:47)
> at 
> org.apache.eagle.metric.reportor.EagleCounterMetric.update(EagleCounterMetric.java:67)
>at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.updateCounter(PolicyProcessExecutor.java:285)
>  at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.updateCounter(PolicyProcessExecutor.java:291)
>  at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.flatMap(PolicyProcessExecutor.java:325)
>at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.execute(JavaStormBoltWrapper.scala:38)
> at 
> backtype.storm.daemon.executor$fn__3441$tuple_action_fn__3443.invoke(executor.clj:633)
>at 
> backtype.storm.daemon.executor$mk_task_receiver$fn__3364.invoke(executor.clj:401)
> at 
> backtype.storm.disruptor$clojure_handler$reify__1447.onEvent(disruptor.clj:58)
>at 
> backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:125)
> at 
> backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:99)
> at 
> backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:80)
>at 
> backtype.storm.daemon.executor$fn__3441$fn__3453$fn__3500.invoke(executor.clj:748)
>at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463)  at 
> clojure.lang.AFn.run(AFn.java:24)at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Resolved] (EAGLE-237) Add development tools for quickly starting zookeeper, kafka and webservice without depending on sandbox

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-237.

Resolution: Fixed

https://github.com/apache/incubator-eagle/pull/142/commits/51a5cd4885daf17980bb5c6f211e8965f4b838aa

> Add development tools for quickly starting zookeeper, kafka and webservice 
> without depending on sandbox
> ---
>
> Key: EAGLE-237
> URL: https://issues.apache.org/jira/browse/EAGLE-237
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[jira] [Resolved] (EAGLE-235) org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions for property "alertContext"

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-235.

Resolution: Fixed

https://github.com/apache/incubator-eagle/pull/142/commits/823f04e8acff789fc61585f6b69bf4b0a7e087a6

> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext"
> -
>
> Key: EAGLE-235
> URL: https://issues.apache.org/jira/browse/EAGLE-235
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> {code}
> java.io.IOException: Service side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> {code}



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

[jira] [Resolved] (EAGLE-232) Create local Kafka/Zookeeper/Storm runner tools for quickstart examples and add related scripts to start/top zk/kafka

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-232.

   Resolution: Fixed
Fix Version/s: v0.4.0

https://github.com/apache/incubator-eagle/tree/master/eagle-devsupport

> Create local Kafka/Zookeeper/Storm runner tools for quickstart examples and 
> add related scripts to start/top zk/kafka
> -
>
> Key: EAGLE-232
> URL: https://issues.apache.org/jira/browse/EAGLE-232
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> Apache Kafka's scripts provide a good example to package external 
> dependencies like zookeeper together for quick start. 
> https://github.com/apache/kafka/blob/trunk/bin/zookeeper-server-start.sh
> For Eagle, we should add following scripts as well:
> {code}
> /bin/eagle-run-class.sh
> /bin/kafka-server-start.sh
> /bin/kafka-server-stop.sh
> /bin/zookeeper-server-start.sh
> /bin/zookeeper-server-stop.sh
> {code}



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

[jira] [Resolved] (EAGLE-230) Exception in persisting entitiesService side exception: org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions for property "alertContext"

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-230.

Resolution: Fixed

> Exception in persisting entitiesService side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext"
> -
>
> Key: EAGLE-230
> URL: https://issues.apache.org/jira/browse/EAGLE-230
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> 49144 [Thread-13-AlertPersistExecutor_6] ERROR 
> org.apache.eagle.service.client.impl.EagleServiceClientImpl - Failed to 
> create entities for service: AlertService
> 49145 [Thread-13-AlertPersistExecutor_6] ERROR 
> org.apache.eagle.alert.persist.EaglePersist - Got an exception in persisting 
> entitiesService side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:315)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.BasicDeserializerFactory.createCollectionDeserializer(BasicDeserializerFactory.java:284)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:389)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findTypedValueDeserializer(StdDeserializerProvider.java:180)
> org.codehaus.jackson.map.ObjectMapper._findRootDeserializer(ObjectMapper.java:2829)
> java.io.IOException: Service side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:315)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.BasicDeserializerFactory.createCollectionDeserializer(BasicDeserializerFactory.java:284)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:389)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findTypedValueDeserializer(StdDeserializerProvider.java:180)
> org.codehaus.jackson.map.ObjectMapper._findRootDeserializer(ObjectMapper.java:2829)
>   at 
> org.apache.eagle.service.client.impl.EagleServiceClientImpl.create(EagleServiceClientImpl.java:77)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.alert.persist.EaglePersist.doPersist(EaglePersist.java:55) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.alert.persist.AlertPersistExecutor.flatMap(AlertPersistExecutor.java:54)
>  [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.execute(JavaStormBoltWrapper.scala:38)
>  [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> backtype.storm.daemon.executor$fn__4722$tuple_action_fn__4724.invoke(executor.clj:633)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.daemon.executor$mk_task_receiver$fn__4645.invoke(executor.clj:401)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.disruptor$clojure_handler$reify__1446.onEvent(disruptor.clj:58)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.utils.DisruptorQueue.co

[jira] [Resolved] (EAGLE-229) java.lang.IncompatibleClassChangeError: class net.sf.extcos.internal.JavaResourceAccessor$AnnotatedClassVisitor has interface org.objectweb.asm.ClassVisitor as super clas

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-229.

Resolution: Fixed

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

> java.lang.IncompatibleClassChangeError: class 
> net.sf.extcos.internal.JavaResourceAccessor$AnnotatedClassVisitor has 
> interface org.objectweb.asm.ClassVisitor as super class
> ---
>
> Key: EAGLE-229
> URL: https://issues.apache.org/jira/browse/EAGLE-229
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> h1. Exception
> {code}
> 21399 [eXtcos managed thread 1] ERROR 
> org.apache.storm.zookeeper.server.NIOServerCnxnFactory - Thread Thread[eXtcos 
> managed thread 1,5,main] died
> java.lang.IncompatibleClassChangeError: class 
> net.sf.extcos.internal.JavaResourceAccessor$AnnotatedClassVisitor has 
> interface org.objectweb.asm.ClassVisitor as super class
>   at java.lang.ClassLoader.defineClass1(Native Method) ~[na:1.7.0_75]
>   at java.lang.ClassLoader.defineClass(ClassLoader.java:800) 
> ~[na:1.7.0_75]
>   at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.access$100(URLClassLoader.java:71) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:361) ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[na:1.7.0_75]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[na:1.7.0_75]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[na:1.7.0_75]
>   at java.lang.ClassLoader.defineClass1(Native Method) ~[na:1.7.0_75]
>   at java.lang.ClassLoader.defineClass(ClassLoader.java:800) 
> ~[na:1.7.0_75]
>   at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.access$100(URLClassLoader.java:71) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:361) ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[na:1.7.0_75]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[na:1.7.0_75]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[na:1.7.0_75]
>   at 
> net.sf.extcos.internal.JavaResourceAccessor.readClassData(JavaResourceAccessor.java:363)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.JavaResourceAccessor.setResourceUrl(JavaResourceAccessor.java:333)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.URLResource.getResourceAccessor(URLResource.java:93) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at net.sf.extcos.internal.URLResource.isClass(URLResource.java:126) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at net.sf.extcos.internal.RootFilter.filter(RootFilter.java:22) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.AbstractChainedFilter.filter(AbstractChainedFilter.java:89)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.ThreadingFilterInterceptor$1.run(ThreadingFilterInterceptor.java:48)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_75]
> {code}
> h1. Root Cause
> Included "asm" or "asm-all" in "eagle-topology-assembly" by following 
> dependencies:
> {code}
> 
> org.apache.eagle
> eagle-metric-collection
> ${project.version}
>  
> {code}
> h1. Validation
> It will cause above problem if the jar  contains class 
> "org.objectweb.asm.ClassVisitor"
> {code}
> jar -tf lib/topology/eagle-topology-0.3.0-incubating-assembly.jar  | grep 
> org.objectweb.asm.ClassVisitor
> {code}
> h1. Solution
> {code}
> 
> 
> org.ow2.asm
> asm-all
> 
> 
> org.ow2.asm
> asm
> 
> 
> asm
> asm
> 
> 
>   

[jira] [Resolved] (EAGLE-228) org.apache.eagle.notification.plugin.NotificationPluginManagerImpl - fail invoking plugin's onAlert, continue java.lang.NullPointerException: null

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-228.

Resolution: Fixed

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

> org.apache.eagle.notification.plugin.NotificationPluginManagerImpl - fail 
> invoking plugin's onAlert, continue  java.lang.NullPointerException: null
> ---
>
> Key: EAGLE-228
> URL: https://issues.apache.org/jira/browse/EAGLE-228
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> 18087 [Thread-11-AlertNotificationExecutor_8] ERROR 
> org.apache.eagle.notification.plugin.NotificationPluginManagerImpl - fail 
> invoking plugin's onAlert, continue 
> java.lang.NullPointerException: null
>   at 
> org.apache.eagle.notification.plugin.NotificationPluginManagerImpl.notifyAlert(NotificationPluginManagerImpl.java:83)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.alert.notification.AlertNotificationExecutor.processAlerts(AlertNotificationExecutor.java:98)
>  [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.alert.notification.AlertNotificationExecutor.flatMap(AlertNotificationExecutor.java:93)
>  [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.execute(JavaStormBoltWrapper.scala:38)
>  [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> backtype.storm.daemon.executor$fn__4722$tuple_action_fn__4724.invoke(executor.clj:633)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.daemon.executor$mk_task_receiver$fn__4645.invoke(executor.clj:401)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.disruptor$clojure_handler$reify__1446.onEvent(disruptor.clj:58)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:125)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:99)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:80)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.daemon.executor$fn__4722$fn__4734$fn__4781.invoke(executor.clj:748)
>  [storm-core-0.9.4.jar:0.9.4]
>   at backtype.storm.util$async_loop$fn__458.invoke(util.clj:463) 
> [storm-core-0.9.4.jar:0.9.4]
>   at clojure.lang.AFn.run(AFn.java:24) 
> [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at java.lang.Thread.run(Thread.java:745) [na:1.7.0_75]
> 18255 [Thread-13-AlertPersistExecutor_6] ERROR 
> org.apache.eagle.service.client.impl.EagleServiceClientImpl - Failed to 
> create entities for service: AlertService
> 18255 [Thread-13-AlertPersistExecutor_6] ERROR 
> org.apache.eagle.alert.persist.EaglePersist - Got an exception in persisting 
> entitiesService side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:315)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.BasicDeserializerFactory.createCollectionDeserializer(BasicDeserializerFactory.java:284)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:389)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findTypedValueDeserializer(StdDeserializerProvider.java:180)
> org.codehaus.jackson.map.ObjectMapper._findRootDeserializer(ObjectMapper.java:2829)
> java.io.IOException: Service side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> org.codehaus.jackson.map.deser.StdDese

[jira] [Updated] (EAGLE-240) java.lang.ArrayIndexOutOfBoundsException thrown by MetricKeyCodeDecoder

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-240:
---
Fix Version/s: v0.4.0

> java.lang.ArrayIndexOutOfBoundsException thrown by MetricKeyCodeDecoder
> ---
>
> Key: EAGLE-240
> URL: https://issues.apache.org/jira/browse/EAGLE-240
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: policy-engine
> Fix For: v0.4.0
>
>
> {code}
> 2016-04-12 12:56:43,491 ERROR [Thread-18-cassandraQueryLogExecutor_0] 
> executor.PolicyProcessExecutor[336]: cassandraQueryLogExecutor, partition 0, 
> error fetching alerts, but continue to run 
> java.lang.ArrayIndexOutOfBoundsException: 1 at 
> org.apache.eagle.metric.reportor.MetricKeyCodeDecoder.decodeMetricKey(MetricKeyCodeDecoder.java:45)
>   at 
> org.apache.eagle.metric.reportor.MetricKeyCodeDecoder.decodeTSMetricKey(MetricKeyCodeDecoder.java:60)
> at 
> org.apache.eagle.metric.reportor.MetricEntityAdaptor.convert(MetricEntityAdaptor.java:29)
> at 
> org.apache.eagle.metric.reportor.EagleServiceReporterMetricListener.onMetricFlushed(EagleServiceReporterMetricListener.java:48)
>   at 
> org.apache.eagle.metric.reportor.EagleCounterMetric.flush(EagleCounterMetric.java:47)
> at 
> org.apache.eagle.metric.reportor.EagleCounterMetric.update(EagleCounterMetric.java:67)
>at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.updateCounter(PolicyProcessExecutor.java:285)
>  at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.updateCounter(PolicyProcessExecutor.java:291)
>  at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.flatMap(PolicyProcessExecutor.java:325)
>at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.execute(JavaStormBoltWrapper.scala:38)
> at 
> backtype.storm.daemon.executor$fn__3441$tuple_action_fn__3443.invoke(executor.clj:633)
>at 
> backtype.storm.daemon.executor$mk_task_receiver$fn__3364.invoke(executor.clj:401)
> at 
> backtype.storm.disruptor$clojure_handler$reify__1447.onEvent(disruptor.clj:58)
>at 
> backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:125)
> at 
> backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:99)
> at 
> backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:80)
>at 
> backtype.storm.daemon.executor$fn__3441$fn__3453$fn__3500.invoke(executor.clj:748)
>at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463)  at 
> clojure.lang.AFn.run(AFn.java:24)at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Updated] (EAGLE-239) Alert list and details are not correctly displayed

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-239:
---
Fix Version/s: v0.4.0

> Alert list and details are not correctly displayed
> --
>
> Key: EAGLE-239
> URL: https://issues.apache.org/jira/browse/EAGLE-239
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Jilin, Jiang
>  Labels: front-end
> Fix For: v0.4.0
>
> Attachments: alert-detail.png, alert-list.png
>
>
> Detail contents of policy alerts are empty, but the alert entity is
> {code}
> {"meta":{"elapsedms":2,"totalResults":1,"lastTimestamp":0,"firstTimestamp":0},"success":true,"obj":[{"prefix":"hadoop","timestamp":1460439827376,"tags":{"site":"sandbox","alertSource":"57347@LM-SHC-00950798","application":"cassandraQueryLog","sourceStreams":"cassandraQueryLogStream","policyId":"cf_
>  customer_details_and_ ks_ 
> dg_keyspace_policy","hostname":null,"alertExecutorId":"cassandraQueryLogExecutor"},"encodedRowkey":"tv4MJX___qv3ALxPlXeMWPh3G-THMWiXsK8Rgesfe8rGJjw3ADXfR28vvscgmSntlDikFVykBVAKa2NE","alertContext":"{\"site\":\"sandbox\",\"application\":\"cassandraQueryLog\",\"host\":\"/192.168.6.227\",\"ks\":\"dg_keyspace\",\"policyDetailUrl\":\"http://localhost:9099/eagle-service/#/dam/policyDetail?policy=cf_
>  customer_details_and_ ks_ 
> dg_keyspace_policy&site=sandbox&executor=cassandraQueryLogExecutor\",\"masked_columns\":\"bank|ccno|email|ip|name|sal|ssn|tel|url\",\"type\":\"CQL_SELECT\",\"alertMessage\":\"The
>  Policy \\\"cf_ customer_details_and_ ks_ dg_keyspace_policy\\\" has been 
> detected with the below information: timestamp=\\\"1455574202864\\\" 
> operation=\\\"CQL_SELECT\\\" category=\\\"QUERY\\\" 
> host=\\\"/192.168.6.227\\\" source=\\\"/192.168.6.227\\\" 
> ks=\\\"dg_keyspace\\\" other_columns=\\\"id|npi\\\" 
> masked_columns=\\\"bank|ccno|email|ip|name|sal|ssn|tel|url\\\" 
> type=\\\"CQL_SELECT\\\" user=\\\"jaspa\\\" cf=\\\"customer_details\\\" 
> \",\"alertEvent\":\"timestamp=\\\"1455574202864\\\" 
> operation=\\\"CQL_SELECT\\\" category=\\\"QUERY\\\" 
> host=\\\"/192.168.6.227\\\" source=\\\"/192.168.6.227\\\" 
> ks=\\\"dg_keyspace\\\" other_columns=\\\"id|npi\\\" 
> masked_columns=\\\"bank|ccno|email|ip|name|sal|ssn|tel|url\\\" 
> type=\\\"CQL_SELECT\\\" user=\\\"jaspa\\\" cf=\\\"customer_details\\\" 
> \",\"alertTimestamp\":\"2016-04-12 
> 05:43:47\",\"timestamp\":\"1455574202864\",\"operation\":\"CQL_SELECT\",\"category\":\"QUERY\",\"alertDetailUrl\":\"http://localhost:9099/eagle-service/#/dam/alertDetail/tv4MJX%5F%5F%5Fqv3ALxPlXeMWPh3G%2DTHMWiXsK8Rgesfe8rGJjw3ADXfR28vvscgmSntlDikFVykBVAKa2NE\",\"source\":\"/192.168.6.227\",\"sourceStreams\":\"cassandraQueryLogStream\",\"policyId\":\"cf_
>  customer_details_and_ ks_ 
> dg_keyspace_policy\",\"other_columns\":\"id|npi\",\"cf\":\"customer_details\",\"user\":\"jaspa\"}"}],"type":"org.apache.eagle.alert.entity.AlertAPIEntity"}
> {code}



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

[jira] [Resolved] (EAGLE-226) Refactor Eagle scripts to avoid heavily depending on Hortonworks Sandbox

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-226.

Resolution: Fixed

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

> Refactor Eagle scripts to avoid heavily depending on Hortonworks Sandbox
> 
>
> Key: EAGLE-226
> URL: https://issues.apache.org/jira/browse/EAGLE-226
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[jira] [Updated] (EAGLE-226) Refactor Eagle scripts to avoid heavily depending on Hortonworks Sandbox

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-226:
---
Fix Version/s: v0.4.0

> Refactor Eagle scripts to avoid heavily depending on Hortonworks Sandbox
> 
>
> Key: EAGLE-226
> URL: https://issues.apache.org/jira/browse/EAGLE-226
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>




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

[jira] [Updated] (EAGLE-226) Refactor Eagle scripts to avoid heavily depending on Hortonworks Sandbox

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-226:
---
Affects Version/s: v0.3.0

> Refactor Eagle scripts to avoid heavily depending on Hortonworks Sandbox
> 
>
> Key: EAGLE-226
> URL: https://issues.apache.org/jira/browse/EAGLE-226
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>




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

[jira] [Updated] (EAGLE-230) Exception in persisting entitiesService side exception: org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions for property "alertContext"

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-230:
---
Affects Version/s: v0.3.0

> Exception in persisting entitiesService side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext"
> -
>
> Key: EAGLE-230
> URL: https://issues.apache.org/jira/browse/EAGLE-230
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> 49144 [Thread-13-AlertPersistExecutor_6] ERROR 
> org.apache.eagle.service.client.impl.EagleServiceClientImpl - Failed to 
> create entities for service: AlertService
> 49145 [Thread-13-AlertPersistExecutor_6] ERROR 
> org.apache.eagle.alert.persist.EaglePersist - Got an exception in persisting 
> entitiesService side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:315)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.BasicDeserializerFactory.createCollectionDeserializer(BasicDeserializerFactory.java:284)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:389)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findTypedValueDeserializer(StdDeserializerProvider.java:180)
> org.codehaus.jackson.map.ObjectMapper._findRootDeserializer(ObjectMapper.java:2829)
> java.io.IOException: Service side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:315)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.BasicDeserializerFactory.createCollectionDeserializer(BasicDeserializerFactory.java:284)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:389)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findTypedValueDeserializer(StdDeserializerProvider.java:180)
> org.codehaus.jackson.map.ObjectMapper._findRootDeserializer(ObjectMapper.java:2829)
>   at 
> org.apache.eagle.service.client.impl.EagleServiceClientImpl.create(EagleServiceClientImpl.java:77)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.alert.persist.EaglePersist.doPersist(EaglePersist.java:55) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.alert.persist.AlertPersistExecutor.flatMap(AlertPersistExecutor.java:54)
>  [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.execute(JavaStormBoltWrapper.scala:38)
>  [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> backtype.storm.daemon.executor$fn__4722$tuple_action_fn__4724.invoke(executor.clj:633)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.daemon.executor$mk_task_receiver$fn__4645.invoke(executor.clj:401)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.disruptor$clojure_handler$reify__1446.onEvent(disruptor.clj:58)
>  [storm-core-0

[jira] [Updated] (EAGLE-229) java.lang.IncompatibleClassChangeError: class net.sf.extcos.internal.JavaResourceAccessor$AnnotatedClassVisitor has interface org.objectweb.asm.ClassVisitor as super class

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-229:
---
Fix Version/s: v0.4.0

> java.lang.IncompatibleClassChangeError: class 
> net.sf.extcos.internal.JavaResourceAccessor$AnnotatedClassVisitor has 
> interface org.objectweb.asm.ClassVisitor as super class
> ---
>
> Key: EAGLE-229
> URL: https://issues.apache.org/jira/browse/EAGLE-229
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> h1. Exception
> {code}
> 21399 [eXtcos managed thread 1] ERROR 
> org.apache.storm.zookeeper.server.NIOServerCnxnFactory - Thread Thread[eXtcos 
> managed thread 1,5,main] died
> java.lang.IncompatibleClassChangeError: class 
> net.sf.extcos.internal.JavaResourceAccessor$AnnotatedClassVisitor has 
> interface org.objectweb.asm.ClassVisitor as super class
>   at java.lang.ClassLoader.defineClass1(Native Method) ~[na:1.7.0_75]
>   at java.lang.ClassLoader.defineClass(ClassLoader.java:800) 
> ~[na:1.7.0_75]
>   at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.access$100(URLClassLoader.java:71) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:361) ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[na:1.7.0_75]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[na:1.7.0_75]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[na:1.7.0_75]
>   at java.lang.ClassLoader.defineClass1(Native Method) ~[na:1.7.0_75]
>   at java.lang.ClassLoader.defineClass(ClassLoader.java:800) 
> ~[na:1.7.0_75]
>   at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.access$100(URLClassLoader.java:71) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:361) ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[na:1.7.0_75]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[na:1.7.0_75]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[na:1.7.0_75]
>   at 
> net.sf.extcos.internal.JavaResourceAccessor.readClassData(JavaResourceAccessor.java:363)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.JavaResourceAccessor.setResourceUrl(JavaResourceAccessor.java:333)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.URLResource.getResourceAccessor(URLResource.java:93) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at net.sf.extcos.internal.URLResource.isClass(URLResource.java:126) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at net.sf.extcos.internal.RootFilter.filter(RootFilter.java:22) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.AbstractChainedFilter.filter(AbstractChainedFilter.java:89)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.ThreadingFilterInterceptor$1.run(ThreadingFilterInterceptor.java:48)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_75]
> {code}
> h1. Root Cause
> Included "asm" or "asm-all" in "eagle-topology-assembly" by following 
> dependencies:
> {code}
> 
> org.apache.eagle
> eagle-metric-collection
> ${project.version}
>  
> {code}
> h1. Validation
> It will cause above problem if the jar  contains class 
> "org.objectweb.asm.ClassVisitor"
> {code}
> jar -tf lib/topology/eagle-topology-0.3.0-incubating-assembly.jar  | grep 
> org.objectweb.asm.ClassVisitor
> {code}
> h1. Solution
> {code}
> 
> 
> org.ow2.asm
> asm-all
> 
> 
> org.ow2.asm
> asm
> 
> 
> asm
> asm
> 
>  

[jira] [Updated] (EAGLE-237) Add development tools for quickly starting zookeeper, kafka and webservice without depending on sandbox

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-237:
---
Affects Version/s: v0.4.0

> Add development tools for quickly starting zookeeper, kafka and webservice 
> without depending on sandbox
> ---
>
> Key: EAGLE-237
> URL: https://issues.apache.org/jira/browse/EAGLE-237
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.4.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>




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

[jira] [Updated] (EAGLE-237) Add development tools for quickly starting zookeeper, kafka and webservice without depending on sandbox

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-237:
---
Fix Version/s: v0.4.0

> Add development tools for quickly starting zookeeper, kafka and webservice 
> without depending on sandbox
> ---
>
> Key: EAGLE-237
> URL: https://issues.apache.org/jira/browse/EAGLE-237
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.4.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>




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

[jira] [Updated] (EAGLE-229) java.lang.IncompatibleClassChangeError: class net.sf.extcos.internal.JavaResourceAccessor$AnnotatedClassVisitor has interface org.objectweb.asm.ClassVisitor as super class

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-229:
---
Affects Version/s: v0.3.0

> java.lang.IncompatibleClassChangeError: class 
> net.sf.extcos.internal.JavaResourceAccessor$AnnotatedClassVisitor has 
> interface org.objectweb.asm.ClassVisitor as super class
> ---
>
> Key: EAGLE-229
> URL: https://issues.apache.org/jira/browse/EAGLE-229
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> h1. Exception
> {code}
> 21399 [eXtcos managed thread 1] ERROR 
> org.apache.storm.zookeeper.server.NIOServerCnxnFactory - Thread Thread[eXtcos 
> managed thread 1,5,main] died
> java.lang.IncompatibleClassChangeError: class 
> net.sf.extcos.internal.JavaResourceAccessor$AnnotatedClassVisitor has 
> interface org.objectweb.asm.ClassVisitor as super class
>   at java.lang.ClassLoader.defineClass1(Native Method) ~[na:1.7.0_75]
>   at java.lang.ClassLoader.defineClass(ClassLoader.java:800) 
> ~[na:1.7.0_75]
>   at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.access$100(URLClassLoader.java:71) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:361) ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[na:1.7.0_75]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[na:1.7.0_75]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[na:1.7.0_75]
>   at java.lang.ClassLoader.defineClass1(Native Method) ~[na:1.7.0_75]
>   at java.lang.ClassLoader.defineClass(ClassLoader.java:800) 
> ~[na:1.7.0_75]
>   at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.access$100(URLClassLoader.java:71) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:361) ~[na:1.7.0_75]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[na:1.7.0_75]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[na:1.7.0_75]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[na:1.7.0_75]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[na:1.7.0_75]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[na:1.7.0_75]
>   at 
> net.sf.extcos.internal.JavaResourceAccessor.readClassData(JavaResourceAccessor.java:363)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.JavaResourceAccessor.setResourceUrl(JavaResourceAccessor.java:333)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.URLResource.getResourceAccessor(URLResource.java:93) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at net.sf.extcos.internal.URLResource.isClass(URLResource.java:126) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at net.sf.extcos.internal.RootFilter.filter(RootFilter.java:22) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.AbstractChainedFilter.filter(AbstractChainedFilter.java:89)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> net.sf.extcos.internal.ThreadingFilterInterceptor$1.run(ThreadingFilterInterceptor.java:48)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_75]
> {code}
> h1. Root Cause
> Included "asm" or "asm-all" in "eagle-topology-assembly" by following 
> dependencies:
> {code}
> 
> org.apache.eagle
> eagle-metric-collection
> ${project.version}
>  
> {code}
> h1. Validation
> It will cause above problem if the jar  contains class 
> "org.objectweb.asm.ClassVisitor"
> {code}
> jar -tf lib/topology/eagle-topology-0.3.0-incubating-assembly.jar  | grep 
> org.objectweb.asm.ClassVisitor
> {code}
> h1. Solution
> {code}
> 
> 
> org.ow2.asm
> asm-all
> 
> 
> org.ow2.asm
> asm
> 
> 
> asm
> asm
> 

[jira] [Updated] (EAGLE-230) Exception in persisting entitiesService side exception: org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions for property "alertContext"

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-230:
---
Fix Version/s: v0.4.0

> Exception in persisting entitiesService side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext"
> -
>
> Key: EAGLE-230
> URL: https://issues.apache.org/jira/browse/EAGLE-230
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> 49144 [Thread-13-AlertPersistExecutor_6] ERROR 
> org.apache.eagle.service.client.impl.EagleServiceClientImpl - Failed to 
> create entities for service: AlertService
> 49145 [Thread-13-AlertPersistExecutor_6] ERROR 
> org.apache.eagle.alert.persist.EaglePersist - Got an exception in persisting 
> entitiesService side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:315)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.BasicDeserializerFactory.createCollectionDeserializer(BasicDeserializerFactory.java:284)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:389)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findTypedValueDeserializer(StdDeserializerProvider.java:180)
> org.codehaus.jackson.map.ObjectMapper._findRootDeserializer(ObjectMapper.java:2829)
> java.io.IOException: Service side exception: 
> org.codehaus.jackson.map.JsonMappingException: Conflicting setter definitions 
> for property "alertContext": 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params) vs 
> org.apache.eagle.alert.entity.AlertAPIEntity#setAlertContext(1 params)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:315)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.BasicDeserializerFactory.createCollectionDeserializer(BasicDeserializerFactory.java:284)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:389)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
> org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
> org.codehaus.jackson.map.deser.StdDeserializerProvider.findTypedValueDeserializer(StdDeserializerProvider.java:180)
> org.codehaus.jackson.map.ObjectMapper._findRootDeserializer(ObjectMapper.java:2829)
>   at 
> org.apache.eagle.service.client.impl.EagleServiceClientImpl.create(EagleServiceClientImpl.java:77)
>  ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.alert.persist.EaglePersist.doPersist(EaglePersist.java:55) 
> ~[eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.alert.persist.AlertPersistExecutor.flatMap(AlertPersistExecutor.java:54)
>  [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.execute(JavaStormBoltWrapper.scala:38)
>  [eagle-topology-0.3.0-incubating-assembly.jar:na]
>   at 
> backtype.storm.daemon.executor$fn__4722$tuple_action_fn__4724.invoke(executor.clj:633)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.daemon.executor$mk_task_receiver$fn__4645.invoke(executor.clj:401)
>  [storm-core-0.9.4.jar:0.9.4]
>   at 
> backtype.storm.disruptor$clojure_handler$reify__1446.onEvent(disruptor.clj:58)
>  [storm-core-0.9.4

[jira] [Updated] (EAGLE-206) Fix apache-rat by enabling useDefaultExcludes

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-206:
---
Affects Version/s: v0.3.0

> Fix apache-rat by enabling useDefaultExcludes
> -
>
> Key: EAGLE-206
> URL: https://issues.apache.org/jira/browse/EAGLE-206
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.3.0
>
>




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

[jira] [Updated] (EAGLE-206) Fix apache-rat by enabling useDefaultExcludes

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-206:
---
Fix Version/s: v0.3.0

> Fix apache-rat by enabling useDefaultExcludes
> -
>
> Key: EAGLE-206
> URL: https://issues.apache.org/jira/browse/EAGLE-206
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.3.0
>
>




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

[jira] [Updated] (EAGLE-202) Specified key was too long; max key length is 1000 bytes for mysql

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-202:
---
Affects Version/s: v0.3.0

> Specified key was too long; max key length is 1000 bytes for mysql
> --
>
> Key: EAGLE-202
> URL: https://issues.apache.org/jira/browse/EAGLE-202
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> It didn’t create the required 24 tables automatically.
> Error  : Specified key was too long; max key length is 1000 bytes
> Cause: for UUID columns which is primary key the length is 1024.
> Fix  :  Change length for PK(UUID) columns to 100 and created tables 
> manually.
>  



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

[jira] [Updated] (EAGLE-204) JBDC Support Groupby and Timeseries Aggregation

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-204:
---
Affects Version/s: v0.3.0

> JBDC Support Groupby and Timeseries Aggregation
> ---
>
> Key: EAGLE-204
> URL: https://issues.apache.org/jira/browse/EAGLE-204
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.3.0
>
>




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

[jira] [Updated] (EAGLE-204) JBDC Support Groupby and Timeseries Aggregation

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-204:
---
Fix Version/s: v0.3.0

> JBDC Support Groupby and Timeseries Aggregation
> ---
>
> Key: EAGLE-204
> URL: https://issues.apache.org/jira/browse/EAGLE-204
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.3.0
>
>




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

[jira] [Updated] (EAGLE-213) Updates fail for MySql

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-213:
---
Fix Version/s: v0.4.0

> Updates fail for MySql  
> 
>
> Key: EAGLE-213
> URL: https://issues.apache.org/jira/browse/EAGLE-213
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
> Environment: Linux , Mysql as metadata storage.
>Reporter: Jaspaul Chahal
>Assignee: Su Ralph
> Fix For: v0.4.0
>
>
> All the updating are currently failing for UI actions.



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

[jira] [Updated] (EAGLE-202) Specified key was too long; max key length is 1000 bytes for mysql

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-202:
---
Fix Version/s: v0.3.0

> Specified key was too long; max key length is 1000 bytes for mysql
> --
>
> Key: EAGLE-202
> URL: https://issues.apache.org/jira/browse/EAGLE-202
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.3.0
>
>
> It didn’t create the required 24 tables automatically.
> Error  : Specified key was too long; max key length is 1000 bytes
> Cause: for UUID columns which is primary key the length is 1024.
> Fix  :  Change length for PK(UUID) columns to 100 and created tables 
> manually.
>  



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

[jira] [Assigned] (EAGLE-198) integrate new Siddhi version so that thread should not die when event evaluation fails

[Hao Chen (JIRA)]

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

Hao Chen reassigned EAGLE-198:
--

Assignee: Hao Chen

> integrate new Siddhi version so that thread should not die when event 
> evaluation fails
> --
>
> Key: EAGLE-198
> URL: https://issues.apache.org/jira/browse/EAGLE-198
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Edward Zhang
>Assignee: Hao Chen
> Fix For: v0.3.0
>
>
> Today when Siddhi engine evaluation thread has exception, the whole thread 
> will die which cause event processing halted, Siddhi already had fix on that, 
> we should integrate it.
> 2016-03-11T01:46:42.455+ o.a.s.z.s.NIOServerCnxnFactory [ERROR] Thread 
> Thread[Siddhi-2a19447c-c71d-44fe-a6b8-008e62c6d64a-executor-thread-0,5,main] 
> died
> java.lang.RuntimeException: java.lang.ClassCastException: java.lang.String 
> cannot be cast to java.lang.Double
> at 
> com.lmax.disruptor.FatalExceptionHandler.handleEventException(FatalExceptionHandler.java:45)
>  ~[disruptor-2.10.1.jar:na]
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128) 
> ~[disruptor-2.10.1.jar:na]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  ~[na:1.7.0_79]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  ~[na:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_79]
> Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to 
> java.lang.Double
> at 
> org.wso2.siddhi.core.executor.function.ConvertFunctionExecutor.execute(ConvertFunctionExecutor.java:104)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.function.FunctionExecutor.execute(FunctionExecutor.java:94)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.compare.CompareConditionExpressionExecutor.execute(CompareConditionExpressionExecutor.java:36)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.compare.CompareConditionExpressionExecutor.execute(CompareConditionExpressionExecutor.java:23)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.AndConditionExpressionExecutor.execute(AndConditionExpressionExecutor.java:53)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.AndConditionExpressionExecutor.execute(AndConditionExpressionExecutor.java:24)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.query.processor.filter.FilterProcessor.process(FilterProcessor.java:49)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.query.input.ProcessStreamReceiver.processAndClear(ProcessStreamReceiver.java:93)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.query.input.ProcessStreamReceiver.receive(ProcessStreamReceiver.java:65)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.stream.StreamJunction.sendEvent(StreamJunction.java:114) 
> ~[stormjar.jar:na]



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

[jira] [Updated] (EAGLE-198) integrate new Siddhi version so that thread should not die when event evaluation fails

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-198:
---
Fix Version/s: v0.3.0

> integrate new Siddhi version so that thread should not die when event 
> evaluation fails
> --
>
> Key: EAGLE-198
> URL: https://issues.apache.org/jira/browse/EAGLE-198
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Edward Zhang
>Assignee: Hao Chen
> Fix For: v0.3.0
>
>
> Today when Siddhi engine evaluation thread has exception, the whole thread 
> will die which cause event processing halted, Siddhi already had fix on that, 
> we should integrate it.
> 2016-03-11T01:46:42.455+ o.a.s.z.s.NIOServerCnxnFactory [ERROR] Thread 
> Thread[Siddhi-2a19447c-c71d-44fe-a6b8-008e62c6d64a-executor-thread-0,5,main] 
> died
> java.lang.RuntimeException: java.lang.ClassCastException: java.lang.String 
> cannot be cast to java.lang.Double
> at 
> com.lmax.disruptor.FatalExceptionHandler.handleEventException(FatalExceptionHandler.java:45)
>  ~[disruptor-2.10.1.jar:na]
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128) 
> ~[disruptor-2.10.1.jar:na]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  ~[na:1.7.0_79]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  ~[na:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_79]
> Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to 
> java.lang.Double
> at 
> org.wso2.siddhi.core.executor.function.ConvertFunctionExecutor.execute(ConvertFunctionExecutor.java:104)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.function.FunctionExecutor.execute(FunctionExecutor.java:94)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.compare.CompareConditionExpressionExecutor.execute(CompareConditionExpressionExecutor.java:36)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.compare.CompareConditionExpressionExecutor.execute(CompareConditionExpressionExecutor.java:23)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.AndConditionExpressionExecutor.execute(AndConditionExpressionExecutor.java:53)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.AndConditionExpressionExecutor.execute(AndConditionExpressionExecutor.java:24)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.query.processor.filter.FilterProcessor.process(FilterProcessor.java:49)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.query.input.ProcessStreamReceiver.processAndClear(ProcessStreamReceiver.java:93)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.query.input.ProcessStreamReceiver.receive(ProcessStreamReceiver.java:65)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.stream.StreamJunction.sendEvent(StreamJunction.java:114) 
> ~[stormjar.jar:na]



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

[jira] [Resolved] (EAGLE-198) integrate new Siddhi version so that thread should not die when event evaluation fails

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-198.

Resolution: Fixed

Fixed by upgrading siddhi version with patch contributed by [~haoch] about 
customizable exception handler.

> integrate new Siddhi version so that thread should not die when event 
> evaluation fails
> --
>
> Key: EAGLE-198
> URL: https://issues.apache.org/jira/browse/EAGLE-198
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Edward Zhang
>Assignee: Hao Chen
> Fix For: v0.3.0
>
>
> Today when Siddhi engine evaluation thread has exception, the whole thread 
> will die which cause event processing halted, Siddhi already had fix on that, 
> we should integrate it.
> 2016-03-11T01:46:42.455+ o.a.s.z.s.NIOServerCnxnFactory [ERROR] Thread 
> Thread[Siddhi-2a19447c-c71d-44fe-a6b8-008e62c6d64a-executor-thread-0,5,main] 
> died
> java.lang.RuntimeException: java.lang.ClassCastException: java.lang.String 
> cannot be cast to java.lang.Double
> at 
> com.lmax.disruptor.FatalExceptionHandler.handleEventException(FatalExceptionHandler.java:45)
>  ~[disruptor-2.10.1.jar:na]
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128) 
> ~[disruptor-2.10.1.jar:na]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  ~[na:1.7.0_79]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  ~[na:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_79]
> Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to 
> java.lang.Double
> at 
> org.wso2.siddhi.core.executor.function.ConvertFunctionExecutor.execute(ConvertFunctionExecutor.java:104)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.function.FunctionExecutor.execute(FunctionExecutor.java:94)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.compare.CompareConditionExpressionExecutor.execute(CompareConditionExpressionExecutor.java:36)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.compare.CompareConditionExpressionExecutor.execute(CompareConditionExpressionExecutor.java:23)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.AndConditionExpressionExecutor.execute(AndConditionExpressionExecutor.java:53)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.executor.condition.AndConditionExpressionExecutor.execute(AndConditionExpressionExecutor.java:24)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.query.processor.filter.FilterProcessor.process(FilterProcessor.java:49)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.query.input.ProcessStreamReceiver.processAndClear(ProcessStreamReceiver.java:93)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.query.input.ProcessStreamReceiver.receive(ProcessStreamReceiver.java:65)
>  ~[stormjar.jar:na]
> at 
> org.wso2.siddhi.core.stream.StreamJunction.sendEvent(StreamJunction.java:114) 
> ~[stormjar.jar:na]



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

[jira] [Updated] (EAGLE-241) Beautify script output or logs

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-241:
---
Priority: Minor  (was: Major)

> Beautify script output or logs
> --
>
> Key: EAGLE-241
> URL: https://issues.apache.org/jira/browse/EAGLE-241
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
>  Labels: scripts
>




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

[jira] [Created] (EAGLE-242) Import the notification plugin metadata when initializing

[Hao Chen (JIRA)]

Hao Chen created EAGLE-242:
--

 Summary:  Import the notification plugin metadata when initializing
 Key: EAGLE-242
 URL: https://issues.apache.org/jira/browse/EAGLE-242
 Project: Eagle
  Issue Type: Improvement
Reporter: Hao Chen
Assignee: Senthilkumar


Append the content about notification plugin metadata from:

https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh

into 

https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh




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

[jira] [Updated] (EAGLE-242) Import the notification plugin metadata when initializing

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-242:
---
Affects Version/s: v0.3.0

>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

[jira] [Updated] (EAGLE-242) Import the notification plugin metadata when initializing

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-242:
---
Fix Version/s: v0.4.0

>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

[jira] [Updated] (EAGLE-242) Import the notification plugin metadata when initializing

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-242:
---
Fix Version/s: (was: v0.4.0)

>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

[jira] [Updated] (EAGLE-242) Import the notification plugin metadata when initializing

[Hao Chen (JIRA)]

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

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

>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

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

[Hao Chen (JIRA)]

Hao Chen created EAGLE-243:
--

 Summary: Set up Eagle IT (Integration Test) Suite 
 Key: EAGLE-243
 URL: https://issues.apache.org/jira/browse/EAGLE-243
 Project: Eagle
  Issue Type: New Feature
Reporter: Hao Chen
Assignee: Michael Wu






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

[jira] [Created] (EAGLE-244) Add 'eagle-hdfsecruity-example' referring to 'eagle-examples/eagle-cassandra-example'

[Hao Chen (JIRA)]

Hao Chen created EAGLE-244:
--

 Summary: Add 'eagle-hdfsecruity-example' referring to 
'eagle-examples/eagle-cassandra-example'
 Key: EAGLE-244
 URL: https://issues.apache.org/jira/browse/EAGLE-244
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.3.0
Reporter: Hao Chen
Assignee: Hao Chen






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

[jira] [Updated] (EAGLE-244) Add 'eagle-hdfsecruity-example' referring to 'eagle-examples/eagle-cassandra-example'

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-244:
---
Description: 
h3. Requirements
1. Quick start scripts
2. Sample data scripts


> Add 'eagle-hdfsecruity-example' referring to 
> 'eagle-examples/eagle-cassandra-example'
> -
>
> Key: EAGLE-244
> URL: https://issues.apache.org/jira/browse/EAGLE-244
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> h3. Requirements
> 1. Quick start scripts
> 2. Sample data scripts



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

[jira] [Commented] (EAGLE-239) Alert list and details are not correctly displayed

[Jilin, Jiang (JIRA)]

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

Jilin, Jiang commented on EAGLE-239:


[~haoch][~ralphsu]Current alert entity has removed the 
`alertContext.properties.message`. And I found it has the prop `alertMessage`. 
Is that replacement of `alertContext.properties.message`? If so, I will do the 
update.

> Alert list and details are not correctly displayed
> --
>
> Key: EAGLE-239
> URL: https://issues.apache.org/jira/browse/EAGLE-239
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Jilin, Jiang
>  Labels: front-end
> Fix For: v0.4.0
>
> Attachments: alert-detail.png, alert-list.png
>
>
> Detail contents of policy alerts are empty, but the alert entity is
> {code}
> {"meta":{"elapsedms":2,"totalResults":1,"lastTimestamp":0,"firstTimestamp":0},"success":true,"obj":[{"prefix":"hadoop","timestamp":1460439827376,"tags":{"site":"sandbox","alertSource":"57347@LM-SHC-00950798","application":"cassandraQueryLog","sourceStreams":"cassandraQueryLogStream","policyId":"cf_
>  customer_details_and_ ks_ 
> dg_keyspace_policy","hostname":null,"alertExecutorId":"cassandraQueryLogExecutor"},"encodedRowkey":"tv4MJX___qv3ALxPlXeMWPh3G-THMWiXsK8Rgesfe8rGJjw3ADXfR28vvscgmSntlDikFVykBVAKa2NE","alertContext":"{\"site\":\"sandbox\",\"application\":\"cassandraQueryLog\",\"host\":\"/192.168.6.227\",\"ks\":\"dg_keyspace\",\"policyDetailUrl\":\"http://localhost:9099/eagle-service/#/dam/policyDetail?policy=cf_
>  customer_details_and_ ks_ 
> dg_keyspace_policy&site=sandbox&executor=cassandraQueryLogExecutor\",\"masked_columns\":\"bank|ccno|email|ip|name|sal|ssn|tel|url\",\"type\":\"CQL_SELECT\",\"alertMessage\":\"The
>  Policy \\\"cf_ customer_details_and_ ks_ dg_keyspace_policy\\\" has been 
> detected with the below information: timestamp=\\\"1455574202864\\\" 
> operation=\\\"CQL_SELECT\\\" category=\\\"QUERY\\\" 
> host=\\\"/192.168.6.227\\\" source=\\\"/192.168.6.227\\\" 
> ks=\\\"dg_keyspace\\\" other_columns=\\\"id|npi\\\" 
> masked_columns=\\\"bank|ccno|email|ip|name|sal|ssn|tel|url\\\" 
> type=\\\"CQL_SELECT\\\" user=\\\"jaspa\\\" cf=\\\"customer_details\\\" 
> \",\"alertEvent\":\"timestamp=\\\"1455574202864\\\" 
> operation=\\\"CQL_SELECT\\\" category=\\\"QUERY\\\" 
> host=\\\"/192.168.6.227\\\" source=\\\"/192.168.6.227\\\" 
> ks=\\\"dg_keyspace\\\" other_columns=\\\"id|npi\\\" 
> masked_columns=\\\"bank|ccno|email|ip|name|sal|ssn|tel|url\\\" 
> type=\\\"CQL_SELECT\\\" user=\\\"jaspa\\\" cf=\\\"customer_details\\\" 
> \",\"alertTimestamp\":\"2016-04-12 
> 05:43:47\",\"timestamp\":\"1455574202864\",\"operation\":\"CQL_SELECT\",\"category\":\"QUERY\",\"alertDetailUrl\":\"http://localhost:9099/eagle-service/#/dam/alertDetail/tv4MJX%5F%5F%5Fqv3ALxPlXeMWPh3G%2DTHMWiXsK8Rgesfe8rGJjw3ADXfR28vvscgmSntlDikFVykBVAKa2NE\",\"source\":\"/192.168.6.227\",\"sourceStreams\":\"cassandraQueryLogStream\",\"policyId\":\"cf_
>  customer_details_and_ ks_ 
> dg_keyspace_policy\",\"other_columns\":\"id|npi\",\"cf\":\"customer_details\",\"user\":\"jaspa\"}"}],"type":"org.apache.eagle.alert.entity.AlertAPIEntity"}
> {code}



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

[jira] [Created] (EAGLE-245) Add eagle-devsupport/mvn to support automatically loading Apache Maven Tool

[Hao Chen (JIRA)]

Hao Chen created EAGLE-245:
--

 Summary: Add eagle-devsupport/mvn to support automatically loading 
Apache Maven Tool
 Key: EAGLE-245
 URL: https://issues.apache.org/jira/browse/EAGLE-245
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.3.0
Reporter: Hao Chen
Priority: Minor






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

[jira] [Created] (EAGLE-246) Separate bin/ and conf/ from eagle-assembly into root for user better learn how to use (scripts) and configure (conf) from source code

[Hao Chen (JIRA)]

Hao Chen created EAGLE-246:
--

 Summary: Separate bin/ and conf/ from eagle-assembly into root for 
user better learn how to use (scripts) and configure (conf) from source code
 Key: EAGLE-246
 URL: https://issues.apache.org/jira/browse/EAGLE-246
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.3.0
Reporter: Hao Chen
Priority: Minor


Separate bin/ and conf/ from eagle-assembly into root for user better learn how 
to use (scripts) and configure (conf) from source code



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

[jira] [Created] (EAGLE-247) Refactor Eagle Docker Image without depending on Ambari

[Hao Chen (JIRA)]

Hao Chen created EAGLE-247:
--

 Summary: Refactor Eagle Docker Image without depending on Ambari 
 Key: EAGLE-247
 URL: https://issues.apache.org/jira/browse/EAGLE-247
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.3.0
Reporter: Hao Chen


Current version of Eagle docker is based on Ambari, which is really unstable. 
From the scripts like 
https://github.com/apache/incubator-eagle/tree/master/eagle-devsupport, we 
could learn that we could definitely set up eagle without depending on Ambari 
at all, and it will be much more clear and light-weight for end-user.



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

[jira] [Resolved] (EAGLE-225) Create eagle bootstrap scripts for examples

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-225.

Resolution: Fixed

> Create eagle bootstrap scripts for examples 
> 
>
> Key: EAGLE-225
> URL: https://issues.apache.org/jira/browse/EAGLE-225
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[GitHub] incubator-eagle pull request: EAGLE-242 - added notification init ...

[senthilec566]

GitHub user senthilec566 opened a pull request:

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

EAGLE-242 -  added notification init script into topology init script



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

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

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

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


commit 00cd9ec17f2e6a1b158a634ce0fc19eefaef831b
Author: senthilkumar 
Date:   2016-04-12T11:06:18Z

 added notification init script




---
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-242) Import the notification plugin metadata when initializing

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-242:
--

GitHub user senthilec566 opened a pull request:

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

EAGLE-242 -  added notification init script into topology init script



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

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

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

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


commit 00cd9ec17f2e6a1b158a634ce0fc19eefaef831b
Author: senthilkumar 
Date:   2016-04-12T11:06:18Z

 added notification init script




>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

[GitHub] incubator-eagle pull request: EAGLE-242 - added notification init ...

[haoch]

Github user haoch commented on the pull request:

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

[GitHub] incubator-eagle pull request: EAGLE-242 - added notification init ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-242) Import the notification plugin metadata when initializing

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-242:
--

Github user asfgit closed the pull request at:

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


>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

[jira] [Commented] (EAGLE-242) Import the notification plugin metadata when initializing

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-242:
--

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/143#issuecomment-208987949
  
LGTM


>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

[jira] [Resolved] (EAGLE-242) Import the notification plugin metadata when initializing

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-242.

Resolution: Fixed

>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>  Labels: metadata, scripts
> Fix For: v0.4.0
>
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

[jira] [Updated] (EAGLE-242) Import the notification plugin metadata when initializing

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-242:
---
Labels: metadata scripts  (was: )

>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>  Labels: metadata, scripts
> Fix For: v0.4.0
>
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

[jira] [Updated] (EAGLE-242) Import the notification plugin metadata when initializing

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-242:
---
Fix Version/s: v0.4.0

>  Import the notification plugin metadata when initializing
> --
>
> Key: EAGLE-242
> URL: https://issues.apache.org/jira/browse/EAGLE-242
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Senthilkumar
>  Labels: metadata, scripts
> Fix For: v0.4.0
>
>
> Append the content about notification plugin metadata from:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert/eagle-alert-notification-plugin/src/main/resources/notification-plugins-init.sh
> into 
> https://github.com/apache/incubator-eagle/blob/master/eagle-assembly/src/main/bin/eagle-topology-init.sh



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

[jira] [Created] (EAGLE-248) Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and move 'eagle-devsupport' into 'eagle-contrib/eagle-devtools'

[Hao Chen (JIRA)]

Hao Chen created EAGLE-248:
--

 Summary: Rename 'eagle-external' to 'eagle-contrib' in industrial 
common sense and move 'eagle-devsupport' into 'eagle-contrib/eagle-devtools'
 Key: EAGLE-248
 URL: https://issues.apache.org/jira/browse/EAGLE-248
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.3.0
Reporter: Hao Chen
Assignee: Hao Chen
Priority: Minor
 Fix For: Future


Only do it after dev-tools are finalized and work smoothly for our development.



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

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #74

[Apache Jenkins Server]

The Apache Jenkins build system has built incubator-eagle-main (build #74) 
Status: Failure Check console output at 
https://builds.apache.org/job/incubator-eagle-main/74/ to view the results. 
Test Report is at: Test Result

[jira] [Created] (EAGLE-249) Support Postgres as hive metadata

[Su Ralph (JIRA)]

Su Ralph created EAGLE-249:
--

 Summary: Support Postgres as hive metadata
 Key: EAGLE-249
 URL: https://issues.apache.org/jira/browse/EAGLE-249
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.3.0
Reporter: Su Ralph
Assignee: Su Ralph
 Fix For: v0.4.0


>From Capital One case


It looks very interesting that Postgres has this behavior. Is Postgres your 
production setting for holding hive metadata?
If that is the case, I think we need extend Eagle a little bit to support 
Postgres. (Hive metadata tables use upper case for both table name and column 
name)

Thanks
Edward

On Mon, Apr 11, 2016 at 9:02 PM, Carnali, Matthew R. 
 wrote:
Here are the correct queries:
1.
select "NAME" from "DBS”;
2. 
select "t"."TBL_NAME" from "TBLS" t, "DBS" d where "t"."DB_ID"="d"."DB_ID" and 
"d"."NAME"='%s’;
3.
select "c"."COLUMN_NAME" from "DBS" d join "TBLS" t on "d"."DB_ID"="t"."DB_ID" 
join "SDS" s on "t"."SD_ID"="s"."SD_ID" join "COLUMNS_V2" c on 
"s"."CD_ID"="c"."CD_ID" where "d"."NAME"='%s' and "t"."TBL_NAME"='%s';

From: "Carnali, Matthew R." 
Date: Monday, April 11, 2016 at 8:11 PM
To: Edward Zhang 
Cc: "qingwz...@ebay.com" , Hao Chen , 
"li...@ebay.com" 
Subject: Re: Fail to get WEB_CONFIG configurations for data classification

So what I found is the following:
http://stackoverflow.com/questions/6331504/omitting-the-double-quote-to-do-query-on-postgresql
I modified the queries to have quotes like so (but it still does not seem like 
it is working correctly, I am investigating further):

1. select ’NAME' from "DBS";
2. select 't.TBL_NAME' from "TBLS" t, "DBS" d where 't.db_id'='d.db_id' and 
'd.name'='%s’;
3. select 'c.column_name' from "DBS" d join "TBLS" t on 'd.db_id'='t.db_id' 
join "SDS" s on 't.sd_id'='s.sd_id' join "COLUMNS_V2" c on 's.cd_id'='c.cd_id' 
where 'd.name'='%s' and 't.tbl_name'='%s’;


From: Edward Zhang 
Date: Monday, April 11, 2016 at 3:52 PM
To: "Carnali, Matthew R." 
Cc: "qingwz...@ebay.com" , Hao Chen , 
"li...@ebay.com" 
Subject: Re: Fail to get WEB_CONFIG configurations for data classification

We use the following queries, let me know if any of queries can't be run 
directly against postgres?
1. to get databases
String sql = "select name from DBS";

2. to get tables
String sql_format = "select t.tbl_name from TBLS t, DBS d where t.db_id=d.db_id 
and d.name='%s'";

3. to get columns
String sql_format =
"select c.column_name " +
"from DBS d join TBLS t on d.db_id=t.db_id " +
"join SDS s on t.sd_id=s.sd_id " +
"join COLUMNS_V2 c on s.cd_id=c.cd_id " +
"where d.name='%s' and t.tbl_name='%s';";





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

[jira] [Created] (EAGLE-250) Metadata on mongodb

[Su Ralph (JIRA)]

Su Ralph created EAGLE-250:
--

 Summary: Metadata on mongodb
 Key: EAGLE-250
 URL: https://issues.apache.org/jira/browse/EAGLE-250
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.3.0
Reporter: Su Ralph
Priority: Minor


Currently, eagle support metadata on hbase/jdbc. One might want to extend to 
mongdb which is widely used as configuration store.



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

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

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-135:
---
Due Date: (was: 28/Feb/17)
  Labels: new  (was: )
Priority: Minor  (was: Major)

> 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
(v6.3.4#6332)

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

[Su Ralph (JIRA)]

Su Ralph created EAGLE-251:
--

 Summary: Run eagle on flink/samza
 Key: EAGLE-251
 URL: https://issues.apache.org/jira/browse/EAGLE-251
 Project: Eagle
  Issue Type: New Feature
Reporter: Su Ralph
Priority: Minor


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.3.4#6332)

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

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-251:
---
Affects Version/s: v0.3.0

> 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.3.4#6332)

[jira] [Updated] (EAGLE-248) Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and move 'eagle-devsupport' into 'eagle-contrib/eagle-devtools'

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-248:
---
Fix Version/s: v0.4.0

> Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and 
> move 'eagle-devsupport' into 'eagle-contrib/eagle-devtools'
> -
>
> Key: EAGLE-248
> URL: https://issues.apache.org/jira/browse/EAGLE-248
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
> Fix For: Future, v0.4.0
>
>
> Only do it after dev-tools are finalized and work smoothly for our 
> development.



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

[jira] [Commented] (EAGLE-248) Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and move 'eagle-devsupport' into 'eagle-contrib/eagle-devtools'

[Su Ralph (JIRA)]

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

Su Ralph commented on EAGLE-248:


Move this to v0.4.0. Directory change happens as early as possible would be 
better.

> Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and 
> move 'eagle-devsupport' into 'eagle-contrib/eagle-devtools'
> -
>
> Key: EAGLE-248
> URL: https://issues.apache.org/jira/browse/EAGLE-248
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
> Fix For: Future, v0.4.0
>
>
> Only do it after dev-tools are finalized and work smoothly for our 
> development.



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

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

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-243:
---
Affects Version/s: v0.3.0

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




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

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

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-243:
---
Fix Version/s: v0.4.0

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




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

[jira] [Updated] (EAGLE-241) Beautify script output or logs

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-241:
---
Labels: new scripts  (was: scripts)

> Beautify script output or logs
> --
>
> Key: EAGLE-241
> URL: https://issues.apache.org/jira/browse/EAGLE-241
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
>  Labels: new, scripts
>




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

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

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-234:
---
Fix Version/s: v0.4.0

> Clean maven build warning in eagle
> --
>
> Key: EAGLE-234
> URL: https://issues.apache.org/jira/browse/EAGLE-234
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Hao Chen
>Assignee: Michael Wu
>  Labels: new
> Fix For: v0.4.0
>
>




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

[jira] [Updated] (EAGLE-238) Support scheduling topology in local mode including start/stop/status operations

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-238:
---
Fix Version/s: v0.4.0

> Support scheduling topology in local mode including start/stop/status 
> operations
> 
>
> Key: EAGLE-238
> URL: https://issues.apache.org/jira/browse/EAGLE-238
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Zhao, Qingwen
> Fix For: v0.4.0
>
>




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

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

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-234:
---
Labels: new  (was: )

> Clean maven build warning in eagle
> --
>
> Key: EAGLE-234
> URL: https://issues.apache.org/jira/browse/EAGLE-234
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Hao Chen
>Assignee: Michael Wu
>  Labels: new
> Fix For: v0.4.0
>
>




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

[jira] [Updated] (EAGLE-231) Refactor Eagle Document Website

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-231:
---
Fix Version/s: v0.4.0

> Refactor Eagle Document Website
> ---
>
> Key: EAGLE-231
> URL: https://issues.apache.org/jira/browse/EAGLE-231
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Michael Wu
> Fix For: v0.4.0
>
>
> h1. Research
> Learned from https://github.com/apache/spark/tree/master/docs and 
> https://github.com/apache/flink/tree/master/docs
> The website should consist of two parts in git repository:  
> 1) document branch: A shared Landing Page of Apache Eagle with some static 
> production introduction and also a list/menu navigation to different version 
> of document sites
> 2) master branch: a version specific documentation site under doc/ directory
> When and How to release to apache SVN?
> 1) When having changes in landing page, build and commit the "document" 
> branch into SVN root directory: SVN_REPO/site
> 2) When releasing any new version say v0.3.0, build the current site under 
> docs/ and commit into SVN_REPO/site/docs/${CURRENT_VERSION}
> It seems that flink is working in a more smart way, it trigger the docs build 
> for every branch and serve the doc sites build CI: 
> https://ci.apache.org/projects/
> h1. Design
> 1. Use "document" branch to host the landing site.
> 2. Use "docs/" directory to host document contents and use Apache CI 
> https://ci.apache.org/projects/ to host and sync documentations by each 
> versions.
> h1. TODO
> 1. Modify as consistant branch and tags name
> branch: release-$version
> tags: v$version
> 2. Create a new landing pages which contains some basic introduction and list 
> documents in different versions.
> 3. Add a new doc-style jekyll site into "docs/" for all branches
> 4. Add Setup a Jenkins/CI task to build docs/ into CI site.



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

[jira] [Updated] (EAGLE-231) Refactor Eagle Document Website

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-231:
---
Affects Version/s: v0.3.0

> Refactor Eagle Document Website
> ---
>
> Key: EAGLE-231
> URL: https://issues.apache.org/jira/browse/EAGLE-231
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Michael Wu
> Fix For: v0.4.0
>
>
> h1. Research
> Learned from https://github.com/apache/spark/tree/master/docs and 
> https://github.com/apache/flink/tree/master/docs
> The website should consist of two parts in git repository:  
> 1) document branch: A shared Landing Page of Apache Eagle with some static 
> production introduction and also a list/menu navigation to different version 
> of document sites
> 2) master branch: a version specific documentation site under doc/ directory
> When and How to release to apache SVN?
> 1) When having changes in landing page, build and commit the "document" 
> branch into SVN root directory: SVN_REPO/site
> 2) When releasing any new version say v0.3.0, build the current site under 
> docs/ and commit into SVN_REPO/site/docs/${CURRENT_VERSION}
> It seems that flink is working in a more smart way, it trigger the docs build 
> for every branch and serve the doc sites build CI: 
> https://ci.apache.org/projects/
> h1. Design
> 1. Use "document" branch to host the landing site.
> 2. Use "docs/" directory to host document contents and use Apache CI 
> https://ci.apache.org/projects/ to host and sync documentations by each 
> versions.
> h1. TODO
> 1. Modify as consistant branch and tags name
> branch: release-$version
> tags: v$version
> 2. Create a new landing pages which contains some basic introduction and list 
> documents in different versions.
> 3. Add a new doc-style jekyll site into "docs/" for all branches
> 4. Add Setup a Jenkins/CI task to build docs/ into CI site.



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

[jira] [Updated] (EAGLE-222) Documentation for eagle alert plugin mechnism

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-222:
---
Affects Version/s: v0.3.0

> Documentation for eagle alert plugin mechnism
> -
>
> Key: EAGLE-222
> URL: https://issues.apache.org/jira/browse/EAGLE-222
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Assignee: Senthilkumar
> Fix For: v0.4.0
>
>
> Eagle alert plugin is supported in backend. EAGLE-221 will support in user 
> interface side. This JIRA to provide end-user documentation including:
> 1. How to create policy with different alert notification type.
> 2. How to write an customized notification
> 3. How notification plugin would be called during data flow.



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

[jira] [Updated] (EAGLE-217) Fix unstable unit tests about state snapshot management

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-217:
---
Fix Version/s: v0.4.0

> Fix unstable unit tests about state snapshot management
> ---
>
> Key: EAGLE-217
> URL: https://issues.apache.org/jira/browse/EAGLE-217
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> Following unit tests failed sometimes:
> https://builds.apache.org/job/incubator-eagle-main/68/console 
> {code} 
> testLengthSlideWindowWithGroupby(org.apache.eagle.alert.state.TestSiddhiStateSnapshotAndRestore)
>  
> testTimeSlideWindow(org.apache.eagle.alert.state.TestSiddhiStateSnapshotAndRestore)
> {code}



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

[jira] [Updated] (EAGLE-212) Fix AlertDataSourceEntity Bug in Hive web

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-212:
---
Affects Version/s: (was: v0.4.0)
   v0.3.0

> Fix AlertDataSourceEntity Bug in Hive web
> -
>
> Key: EAGLE-212
> URL: https://issues.apache.org/jira/browse/EAGLE-212
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.4.0
>
>
> This bug is fixed before, but now is incurred by some commit again. 



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

[jira] [Updated] (EAGLE-212) Fix AlertDataSourceEntity Bug in Hive web

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-212:
---
Fix Version/s: v0.4.0

> Fix AlertDataSourceEntity Bug in Hive web
> -
>
> Key: EAGLE-212
> URL: https://issues.apache.org/jira/browse/EAGLE-212
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.4.0
>
>
> This bug is fixed before, but now is incurred by some commit again. 



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

[jira] [Resolved] (EAGLE-201) Change maven group name to org.apache.eagle instead of eagle

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-201.

Resolution: Fixed

this already be fixed in v0.3.0

> Change maven group name to org.apache.eagle instead of eagle
> 
>
> Key: EAGLE-201
> URL: https://issues.apache.org/jira/browse/EAGLE-201
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[jira] [Updated] (EAGLE-196) eagle-topology.sh should have jar file path as parameter

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-196:
---
Labels: new script  (was: )

> eagle-topology.sh should have jar file path as parameter
> 
>
> Key: EAGLE-196
> URL: https://issues.apache.org/jira/browse/EAGLE-196
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Edward Zhang
>Priority: Minor
>  Labels: new, script
> Fix For: v0.4.0
>
>
> eagle-topology.sh today assume the jar provided as following
> jarName=$(ls ${EAGLE_HOME}/lib/topology/eagle-topology-*-assembly.jar)
> We probably need an extra parameter for jar file



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

[jira] [Updated] (EAGLE-196) eagle-topology.sh should have jar file path as parameter

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-196:
---
Fix Version/s: v0.4.0

> eagle-topology.sh should have jar file path as parameter
> 
>
> Key: EAGLE-196
> URL: https://issues.apache.org/jira/browse/EAGLE-196
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Edward Zhang
>Priority: Minor
>  Labels: new, script
> Fix For: v0.4.0
>
>
> eagle-topology.sh today assume the jar provided as following
> jarName=$(ls ${EAGLE_HOME}/lib/topology/eagle-topology-*-assembly.jar)
> We probably need an extra parameter for jar file



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

[jira] [Commented] (EAGLE-180) Add Resource Manager Use Case Policy in Hadoop Metric

[Su Ralph (JIRA)]

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

Su Ralph commented on EAGLE-180:


I think this has been added into v0.3.0 release. Could we close this one.

> Add Resource Manager Use Case Policy in Hadoop Metric 
> --
>
> Key: EAGLE-180
> URL: https://issues.apache.org/jira/browse/EAGLE-180
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.3.0
>Reporter: Senthilkumar
>Assignee: Senthilkumar
>
> Create Resource Manager Related Use Case Policies and Verify it.



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

[jira] [Updated] (EAGLE-146) SiddhiExtensionLoader Error: viewing zip file for jar:./lib/ojdbc6.jar

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-146:
---
Fix Version/s: v0.4.0

> SiddhiExtensionLoader Error: viewing zip file for jar:./lib/ojdbc6.jar
> --
>
> Key: EAGLE-146
> URL: https://issues.apache.org/jira/browse/EAGLE-146
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> {code}
> 2016-02-02 02:46:23 o.a.e.p.PolicyManager [INFO] Supported policy type : 
> siddhiCEPEngine
> 2016-02-02 02:46:23 o.a.e.p.PolicyManager [INFO] Supported policy type : 
> MachineLearning
> 2016-02-02 02:46:23 o.w.s.c.u.SiddhiExtensionLoader [ERROR] Error viewing zip 
> file for jar:./lib/ojdbc6.jar
> java.io.FileNotFoundException: ./lib/ojdbc6.jar (No such file or directory)
> at java.util.zip.ZipFile.open(Native Method) ~[na:1.7.0_60]
> at java.util.zip.ZipFile.(ZipFile.java:215) ~[na:1.7.0_60]
> at java.util.zip.ZipFile.(ZipFile.java:145) ~[na:1.7.0_60]
> at java.util.zip.ZipFile.(ZipFile.java:159) ~[na:1.7.0_60]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromJarFile(SiddhiExtensionLoader.java:111)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:82)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromDirectory(SiddhiExtensionLoader.java:101)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:77)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromDirectory(SiddhiExtensionLoader.java:101)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:77)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getResources(SiddhiExtensionLoader.java:71)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.loadSiddhiExtensions(SiddhiExtensionLoader.java:51)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.config.SiddhiContext.(SiddhiContext.java:35) 
> [stormjar.jar:na]
> at org.wso2.siddhi.core.SiddhiManager.(SiddhiManager.java:40) 
> [stormjar.jar:na]
> at 
> org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.createSiddhiRuntime(SiddhiPolicyEvaluator.java:108)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.init(SiddhiPolicyEvaluator.java:83)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.(SiddhiPolicyEvaluator.java:79)
>  [stormjar.jar:na]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method) [na:1.7.0_60]
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>  [na:1.7.0_60]
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  [na:1.7.0_60]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526) 
> [na:1.7.0_60]
> at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.createPolicyEvaluator(PolicyProcessExecutor.java:243)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.init(PolicyProcessExecutor.java:188)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.prepare(JavaStormBoltWrapper.scala:36)
>  [stormjar.jar:na]
> at 
> backtype.storm.daemon.executor$fn__5697$fn__5710.invoke(executor.clj:732) 
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at backtype.storm.util$async_loop$fn__452.invoke(util.clj:463) 
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
> 2016-02-02 02:46:23 o.w.s.c.u.SiddhiExtensionLoader [ERROR] Error viewing zip 
> file for jar:./lib/ojdbc6.jar
> java.io.FileNotFoundException: ./lib/ojdbc6.jar (No such file or directory)
> {code}



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

[jira] [Updated] (EAGLE-145) Send mail failed for javax.mail.internet.AddressException: Illegal semicolon, not in group

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-145:
---
Fix Version/s: v0.4.0

> Send mail failed for javax.mail.internet.AddressException: Illegal semicolon, 
> not in group
> --
>
> Key: EAGLE-145
> URL: https://issues.apache.org/jira/browse/EAGLE-145
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> {code}
> 2016-02-02 02:52:03 o.a.e.p.e.PolicyProcessExecutor [INFO] Detected 1 alerts 
> for policy missingBlockPolicy
> 2016-02-02 02:52:03 o.a.e.m.r.EagleServiceReporterMetricListener [INFO] Wrote 
> 1 entities to service
> 2016-02-02 02:52:03 o.a.e.a.p.EaglePersist [INFO] Going to persist entities, 
> type:  AlertAPIEntity, list size: 1
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Initialized 
> Thread-4-AlertNotificationExecutor_10: origin is : 
> druid-test-host1-556191.slc01.dev.ebayc3.com(pid:14052), recipient of the 
> email: li...@ebay.com;hch...@ebay.com, velocity TPL file: ALERT_DEFAULT.vm
> 2016-02-02 02:52:03 o.a.e.a.n.AlertEmailGenerator [INFO] Sending email  in 
> asynchronous to: h...@apache.org, cc: null
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Sending email, tried: 
> 1, max: 3
> 2016-02-02 02:52:03 STDIO [INFO] DEBUG: setDebug: JavaMail version 1.4ea
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Env is: prod
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] After calling 
> generateCommonContext...
> 2016-02-02 02:52:03 o.a.velocity [ERROR] ResourceManager : unable to find 
> resource 'templates/ALERT_DEFAULT.vm' in any resource loader.
> 2016-02-02 02:52:03 o.a.e.c.e.EagleMailClient [INFO] Send mail failed, got an 
> AddressException: Illegal semicolon, not in group
> javax.mail.internet.AddressException: Illegal semicolon, not in group
>   at javax.mail.internet.InternetAddress.parse(InternetAddress.java:780) 
> ~[stormjar.jar:na]
>   at javax.mail.internet.InternetAddress.parse(InternetAddress.java:555) 
> ~[stormjar.jar:na]
>   at javax.mail.internet.InternetAddress.parse(InternetAddress.java:532) 
> ~[stormjar.jar:na]
>   at 
> org.apache.eagle.common.email.EagleMailClient._send(EagleMailClient.java:104) 
> [stormjar.jar:na]
>   at 
> org.apache.eagle.common.email.EagleMailClient.send(EagleMailClient.java:167) 
> [stormjar.jar:na]
>   at 
> org.apache.eagle.common.email.EagleMailClient.send(EagleMailClient.java:187) 
> [stormjar.jar:na]
>   at 
> org.apache.eagle.common.email.EagleMailClient.send(EagleMailClient.java:193) 
> [stormjar.jar:na]
>   at 
> org.apache.eagle.alert.common.AlertEmailSender.run(AlertEmailSender.java:129) 
> [stormjar.jar:na]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
> [na:1.7.0_60]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262) 
> [na:1.7.0_60]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  [na:1.7.0_60]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  [na:1.7.0_60]
>   at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Success of sending 
> email: false
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Sleep for a while 
> before retrying
> {code}



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

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

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-134:
---
Fix Version/s: v0.4.0

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




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

[jira] [Commented] (EAGLE-115) Fix licenses headers for webapp files

[Su Ralph (JIRA)]

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

Su Ralph commented on EAGLE-115:


With v0.3.0 released, this is already fixed.

> Fix licenses headers for webapp files
> -
>
> Key: EAGLE-115
> URL: https://issues.apache.org/jira/browse/EAGLE-115
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Prasad Mujumdar
>
> This is a followup ticket to EAGLE-114 to track the files in webapp under 
> eagle-webservice. There are a large number of non source code files that 
> needs to be handled.



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

[jira] [Updated] (EAGLE-73) Put docker steps to site tutorial

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-73:
--
Fix Version/s: v0.4.0

> Put docker steps to site tutorial
> -
>
> Key: EAGLE-73
> URL: https://issues.apache.org/jira/browse/EAGLE-73
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.3.0
>Reporter: Su Ralph
> Fix For: v0.4.0
>
>
> Dockerize code already checked, please help to push the dockerize steps to 
> eagle site documentation under installation topic.



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

[jira] [Updated] (EAGLE-73) Put docker steps to site tutorial

[Su Ralph (JIRA)]

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

Su Ralph updated EAGLE-73:
--
Assignee: Zhaokun Qin

> Put docker steps to site tutorial
> -
>
> Key: EAGLE-73
> URL: https://issues.apache.org/jira/browse/EAGLE-73
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Assignee: Zhaokun Qin
> Fix For: v0.4.0
>
>
> Dockerize code already checked, please help to push the dockerize steps to 
> eagle site documentation under installation topic.



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

[jira] [Resolved] (EAGLE-18) Follow up with infra about website creation

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-18.
---
Resolution: Fixed

> Follow up with infra about website creation
> ---
>
> Key: EAGLE-18
> URL: https://issues.apache.org/jira/browse/EAGLE-18
> Project: Eagle
>  Issue Type: Bug
>Reporter: Henry Saputra
>
> This is Eagle side for issue filed for INFRA:
>   https://issues.apache.org/jira/browse/INFRA-10747



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

[jira] [Commented] (EAGLE-18) Follow up with infra about website creation

[Su Ralph (JIRA)]

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

Su Ralph commented on EAGLE-18:
---

This should be fixed. Closed

> Follow up with infra about website creation
> ---
>
> Key: EAGLE-18
> URL: https://issues.apache.org/jira/browse/EAGLE-18
> Project: Eagle
>  Issue Type: Bug
>Reporter: Henry Saputra
>
> This is Eagle side for issue filed for INFRA:
>   https://issues.apache.org/jira/browse/INFRA-10747



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

[jira] [Updated] (EAGLE-248) Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and move 'eagle-devsupport' into 'eagle-contrib/eagle-devtools'

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-248:
---
Description: 
Only do it after dev-tools are finalized and work smoothly for our development.

Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and move 
'eagle-devsupport' into 'dev-support'

  was:Only do it after dev-tools are finalized and work smoothly for our 
development.


> Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and 
> move 'eagle-devsupport' into 'eagle-contrib/eagle-devtools'
> -
>
> Key: EAGLE-248
> URL: https://issues.apache.org/jira/browse/EAGLE-248
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
> Fix For: Future, v0.4.0
>
>
> Only do it after dev-tools are finalized and work smoothly for our 
> development.
> Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and 
> move 'eagle-devsupport' into 'dev-support'



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

[jira] [Updated] (EAGLE-248) Rename directories according industrial common sense

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-248:
---
Summary: Rename directories according industrial common sense  (was: Rename 
'eagle-external' to 'eagle-contrib' in industrial common sense and move 
'eagle-devsupport' into 'eagle-contrib/eagle-devtools')

> Rename directories according industrial common sense
> 
>
> Key: EAGLE-248
> URL: https://issues.apache.org/jira/browse/EAGLE-248
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
> Fix For: Future, v0.4.0
>
>
> Only do it after dev-tools are finalized and work smoothly for our 
> development.
> Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and 
> move 'eagle-devsupport' into 'dev-support'



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

[jira] [Commented] (EAGLE-248) Rename directories according industrial common sense

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-248:
--

GitHub user haoch opened a pull request:

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

EAGLE-248 Rename eagle-tutorial to eagle-docs

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

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

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

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

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


commit 0b7f58f4b0009bcc881c4f018eed5bcdc6c45fb0
Author: Hao Chen 
Date:   2016-04-13T04:39:19Z

EAGLE-248 Rename eagle-tutorial to eagle-docs




> Rename directories according industrial common sense
> 
>
> Key: EAGLE-248
> URL: https://issues.apache.org/jira/browse/EAGLE-248
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
> Fix For: Future, v0.4.0
>
>
> Only do it after dev-tools are finalized and work smoothly for our 
> development.
> Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and 
> move 'eagle-devsupport' into 'dev-support'



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

[GitHub] incubator-eagle pull request: EAGLE-248 Rename eagle-tutorial to e...

[haoch]

GitHub user haoch opened a pull request:

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

EAGLE-248 Rename eagle-tutorial to eagle-docs

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

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

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

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

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


commit 0b7f58f4b0009bcc881c4f018eed5bcdc6c45fb0
Author: Hao Chen 
Date:   2016-04-13T04:39:19Z

EAGLE-248 Rename eagle-tutorial to eagle-docs




---
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-248 Rename eagle-tutorial to e...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-248) Rename directories according industrial common sense

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-248:
--

Github user asfgit closed the pull request at:

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


> Rename directories according industrial common sense
> 
>
> Key: EAGLE-248
> URL: https://issues.apache.org/jira/browse/EAGLE-248
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
> Fix For: Future, v0.4.0
>
>
> Only do it after dev-tools are finalized and work smoothly for our 
> development.
> Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and 
> move 'eagle-devsupport' into 'dev-support'



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

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #75

[Apache Jenkins Server]

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

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #76

[Apache Jenkins Server]

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

[jira] [Updated] (EAGLE-248) Rename directories according industrial common sense

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-248:
---
Description: Rename eagle-tutorial to eagle-docs and eagle-devsupport to 
eagle-dev  (was: Only do it after dev-tools are finalized and work smoothly for 
our development.

Rename 'eagle-external' to 'eagle-contrib' in industrial common sense and move 
'eagle-devsupport' into 'dev-support')

> Rename directories according industrial common sense
> 
>
> Key: EAGLE-248
> URL: https://issues.apache.org/jira/browse/EAGLE-248
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
> Fix For: Future, v0.4.0
>
>
> Rename eagle-tutorial to eagle-docs and eagle-devsupport to eagle-dev



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

[jira] [Resolved] (EAGLE-248) Rename directories according industrial common sense

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-248.

   Resolution: Fixed
Fix Version/s: (was: Future)

Renamed eagle-tutorial to eagle-docs and eagle-devsupport to eagle-dev

> Rename directories according industrial common sense
> 
>
> Key: EAGLE-248
> URL: https://issues.apache.org/jira/browse/EAGLE-248
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Minor
> Fix For: v0.4.0
>
>
> Rename eagle-tutorial to eagle-docs and eagle-devsupport to eagle-dev



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

[GitHub] incubator-eagle pull request: EAGLE-239 UI Fix alert detail contex...

[zombieJ]

GitHub user zombieJ opened a pull request:

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

EAGLE-239 UI Fix alert detail context

Alert entity use alertContext directly instead of alertContext.properties. 
Which sync update with UI.

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

$ git pull https://github.com/zombieJ/incubator-eagle fixAlert

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

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


commit 4e3f59f1a1490de95b9cb6cc03196a159fdb034c
Author: jiljiang 
Date:   2016-04-12T09:26:57Z

add json parse

commit 7a509d7108ccf22b38d031120e3f5778e075f297
Author: jiljiang 
Date:   2016-04-13T05:41:48Z

add raw data

commit 1894c16a0698267e1fc995271bb940ab78c9b370
Author: jiljiang 
Date:   2016-04-13T05:47:31Z

add host




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