date:20160218

[GitHub] incubator-eagle pull request: EAGLE-158 Remove org.apache.eagle.da...

2016-02-18 Thread haoch

GitHub user haoch opened a pull request:

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

EAGLE-158 Remove org.apache.eagle.datastream.EagleTuple

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

- Remove org.apache.eagle.datastream.EagleTuple 
- Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN

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

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

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

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


commit 1b98dbc1935a05ab4a3fd0f5e0de43dc7e39ce43
Author: Hao Chen 
Date:   2016-02-18T08:00:02Z

Remove org.apache.eagle.datastream.EagleTuple and use scala.TupleN replace 
org.apache.eagle.datastream.TupleN




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

[jira] [Updated] (EAGLE-158) Disable org.apache.eagle.datastream.EagleTuple

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-158:
---
Description: 
- Remove org.apache.eagle.datastream.EagleTuple 
- Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN

> Disable org.apache.eagle.datastream.EagleTuple
> --
>
> Key: EAGLE-158
> URL: https://issues.apache.org/jira/browse/EAGLE-158
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> - Remove org.apache.eagle.datastream.EagleTuple 
> - Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN



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

[jira] [Commented] (EAGLE-158) Disable org.apache.eagle.datastream.EagleTuple

2016-02-18 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-158:
--

GitHub user haoch opened a pull request:

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

EAGLE-158 Remove org.apache.eagle.datastream.EagleTuple

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

- Remove org.apache.eagle.datastream.EagleTuple 
- Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN

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

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

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

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


commit 1b98dbc1935a05ab4a3fd0f5e0de43dc7e39ce43
Author: Hao Chen 
Date:   2016-02-18T08:00:02Z

Remove org.apache.eagle.datastream.EagleTuple and use scala.TupleN replace 
org.apache.eagle.datastream.TupleN




> Disable org.apache.eagle.datastream.EagleTuple
> --
>
> Key: EAGLE-158
> URL: https://issues.apache.org/jira/browse/EAGLE-158
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> - Remove org.apache.eagle.datastream.EagleTuple 
> - Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN



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

[jira] [Resolved] (EAGLE-142) Replace AlertDefinitionDAOImpl with PolicyDefinitionDAOImpl

2016-02-18 Thread Su Ralph (JIRA)


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

Su Ralph resolved EAGLE-142.

Resolution: Fixed

This is fixed, and commited

> Replace AlertDefinitionDAOImpl with PolicyDefinitionDAOImpl
> ---
>
> Key: EAGLE-142
> URL: https://issues.apache.org/jira/browse/EAGLE-142
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
>Priority: Minor
> Fix For: 0.3.0
>
>




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

[jira] [Resolved] (EAGLE-149) Enable hadoop jmx metric cases

2016-02-18 Thread Su Ralph (JIRA)


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

Su Ralph resolved EAGLE-149.

Resolution: Fixed

Add all cases into the eagle-hadoop-metric projects. Fix and resolve

> Enable hadoop jmx metric cases
> --
>
> Key: EAGLE-149
> URL: https://issues.apache.org/jira/browse/EAGLE-149
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> In our practice of hadoop monitoring, below cases will be mostly worth to be 
> monitored, we could build this case into eagle like other applications.
> Identify whenever one of the Namenodes goes into SafeMode.
> Lag between Active and Standby Namenode
> Full GC Alerts on Namenodes
> Identify NN/RM HA state changes
> Sudden change in count on live DN or NM nodes
> Missing Blocks
> Last checkpoint time



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

[jira] [Updated] (EAGLE-34) Dynamic stream metadata loading

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-34:
--
Fix Version/s: (was: 0.3.0)

> Dynamic stream metadata loading
> ---
>
> Key: EAGLE-34
> URL: https://issues.apache.org/jira/browse/EAGLE-34
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> 1. Allow user to change stream metadata and dynamically loaded into topology 
> for use
> 2. Support implicit field type convention like string to double/float and so 
> on.



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

[jira] [Updated] (EAGLE-34) Dynamic stream metadata loading

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-34:
--
Affects Version/s: 0.3.0

> Dynamic stream metadata loading
> ---
>
> Key: EAGLE-34
> URL: https://issues.apache.org/jira/browse/EAGLE-34
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> 1. Allow user to change stream metadata and dynamically loaded into topology 
> for use
> 2. Support implicit field type convention like string to double/float and so 
> on.



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

[jira] [Updated] (EAGLE-34) Dynamic stream metadata loading

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-34:
--
Affects Version/s: (was: 0.3.0)

> Dynamic stream metadata loading
> ---
>
> Key: EAGLE-34
> URL: https://issues.apache.org/jira/browse/EAGLE-34
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> 1. Allow user to change stream metadata and dynamically loaded into topology 
> for use
> 2. Support implicit field type convention like string to double/float and so 
> on.



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

[jira] [Updated] (EAGLE-34) Dynamic stream metadata loading

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-34:
--
Affects Version/s: 0.3.0

> Dynamic stream metadata loading
> ---
>
> Key: EAGLE-34
> URL: https://issues.apache.org/jira/browse/EAGLE-34
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> 1. Allow user to change stream metadata and dynamically loaded into topology 
> for use
> 2. Support implicit field type convention like string to double/float and so 
> on.



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

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-146:
---
Fix Version/s: (was: 0.3.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: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> {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] [Resolved] (EAGLE-138) Extend JMX Collector to support "hadoop.namenode.JournalTransaction"

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen resolved EAGLE-138.

Resolution: Resolved

> Extend JMX Collector to support "hadoop.namenode.JournalTransaction"
> 
>
> Key: EAGLE-138
> URL: https://issues.apache.org/jira/browse/EAGLE-138
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> Convert
> {code}
> {
> name: "Hadoop:service=NameNode,name=NameNodeInfo",
> JournalTransactionInfo: 
> "{\"LastAppliedOrWrittenTxId\":\"75672\",\"MostRecentCheckpointTxId\":\"38894\"}",
> }
> {code}
> to 
> * hadoop.namenode.JournalTransactionInfo.LastAppliedOrWrittenTxId
> * hadoop.namenode.JournalTransactionInfo.MostRecentCheckpointTxId



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

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-145:
---
Fix Version/s: (was: 0.3.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: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> {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] [Closed] (EAGLE-78) eagle-lib.sh script not work for mac osx and windows

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen closed EAGLE-78.
-

> eagle-lib.sh script not work for mac osx and windows
> 
>
> Key: EAGLE-78
> URL: https://issues.apache.org/jira/browse/EAGLE-78
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: mac osx, windows
>Reporter: Hao Chen
>Assignee: Zhaokun Qin
> Fix For: 0.3.0
>
>
> Error under MacOSX
> {code}
> $ source eagle-external/eagle-docker/bin/eagle-lib.sh
> -sh: `run-command': not a valid identifier
> -sh: `amb-clean': not a valid identifier
> -sh: `get-ambari-server-ip': not a valid identifier
> -sh: `get-host-ip': not a valid identifier
> -sh: `amb-members': not a valid identifier
> -sh: `amb-settings': not a valid identifier
> -sh: `docker-ps': not a valid identifier
> -sh: `docker-psa': not a valid identifier
> -sh: `amb-start-cluster': not a valid identifier
> -sh: `amb-shell': not a valid identifier
> -sh: `eagle-deploy-cluster': not a valid identifier
> -sh: `amb-start-first': not a valid identifier
> -sh: `amb-copy-to-hdfs': not a valid identifier
> -sh: `amb-create-hdfs-dir': not a valid identifier
> -sh: `amb-scp-to-first': not a valid identifier
> -sh: `amb-start-node': not a valid identifier
> {code}



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

[jira] [Resolved] (EAGLE-118) Siddhi contains is neither a function extension nor an aggregated attribute extension

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen resolved EAGLE-118.

Resolution: Won't Fix

> Siddhi contains is neither a function extension nor an aggregated attribute 
> extension 
> --
>
> Key: EAGLE-118
> URL: https://issues.apache.org/jira/browse/EAGLE-118
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Edward Zhang
> Fix For: 0.3.0
>
>
> HdfsUserCommandReassembler failed to initialize with exception: 
> **org.wso2.siddhi.core.exception.ExecutionPlanCreationException: contains is 
> neither a function extension nor an aggregated attribute extension**
> {code}
> org.wso2.siddhi.query.api.exception.ExecutionPlanValidationException: 
> contains is neither a function extension nor an aggregated attribute 
> extension, when creating query copyFromLocal in execution plan 
> "b38f8f76-c2cf-4288-a26a-cb2a30161b42"
>   at 
> org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:127)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:51)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:59)
>  ~[stormjar.jar:na]
>   at 
> org.apache.eagle.security.auditlog.HdfsUserCommandReassembler.init(HdfsUserCommandReassembler.java:130)
>  ~[stormjar.jar:na]
>   at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.prepare(JavaStormBoltWrapper.scala:36)
>  ~[stormjar.jar:na]
>   at 
> backtype.storm.daemon.executor$fn__5017$fn__5030.invoke(executor.clj:732) 
> ~[storm-core-0.9.3.2.2.4.2-2.jar:0.9.3.2.2.4.2-2]
>   at backtype.storm.util$async_loop$fn__452.invoke(util.clj:463) 
> ~[storm-core-0.9.3.2.2.4.2-2.jar:0.9.3.2.2.4.2-2]
>   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_79]
> Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: 
> contains is neither a function extension nor an aggregated attribute 
> extension, when creating query copyFromLocal
>   at 
> org.wso2.siddhi.core.util.parser.QueryParser.parse(QueryParser.java:109) 
> ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:117)
>  ~[stormjar.jar:na]
>   ... 8 common frames omitted
> Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: 
> contains is neither a function extension nor an aggregated attribute extension
>   at 
> org.wso2.siddhi.core.util.parser.ExpressionParser.parseExpression(ExpressionParser.java:244)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.ExpressionParser.parseExpression(ExpressionParser.java:103)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.SingleInputStreamParser.generateProcessor(SingleInputStreamParser.java:129)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.SingleInputStreamParser.parseInputStream(SingleInputStreamParser.java:86)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:92)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:134)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:134)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:134)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:134)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:171)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parseInputStream(StateInputStreamParser.java:72)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.InputStreamParser.parse(InputStreamParser.java:57)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.QueryParser.parse(QueryParser.java:64) 
> ~[stormjar.jar:na]
>   ... 9 common frames omitted
> {code}



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

[jira] [Resolved] (EAGLE-78) eagle-lib.sh script not work for mac osx and windows

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen resolved EAGLE-78.
---
Resolution: Fixed

> eagle-lib.sh script not work for mac osx and windows
> 
>
> Key: EAGLE-78
> URL: https://issues.apache.org/jira/browse/EAGLE-78
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: mac osx, windows
>Reporter: Hao Chen
>Assignee: Zhaokun Qin
> Fix For: 0.3.0
>
>
> Error under MacOSX
> {code}
> $ source eagle-external/eagle-docker/bin/eagle-lib.sh
> -sh: `run-command': not a valid identifier
> -sh: `amb-clean': not a valid identifier
> -sh: `get-ambari-server-ip': not a valid identifier
> -sh: `get-host-ip': not a valid identifier
> -sh: `amb-members': not a valid identifier
> -sh: `amb-settings': not a valid identifier
> -sh: `docker-ps': not a valid identifier
> -sh: `docker-psa': not a valid identifier
> -sh: `amb-start-cluster': not a valid identifier
> -sh: `amb-shell': not a valid identifier
> -sh: `eagle-deploy-cluster': not a valid identifier
> -sh: `amb-start-first': not a valid identifier
> -sh: `amb-copy-to-hdfs': not a valid identifier
> -sh: `amb-create-hdfs-dir': not a valid identifier
> -sh: `amb-scp-to-first': not a valid identifier
> -sh: `amb-start-node': not a valid identifier
> {code}



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

[jira] [Closed] (EAGLE-118) Siddhi contains is neither a function extension nor an aggregated attribute extension

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen closed EAGLE-118.
--

> Siddhi contains is neither a function extension nor an aggregated attribute 
> extension 
> --
>
> Key: EAGLE-118
> URL: https://issues.apache.org/jira/browse/EAGLE-118
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Edward Zhang
> Fix For: 0.3.0
>
>
> HdfsUserCommandReassembler failed to initialize with exception: 
> **org.wso2.siddhi.core.exception.ExecutionPlanCreationException: contains is 
> neither a function extension nor an aggregated attribute extension**
> {code}
> org.wso2.siddhi.query.api.exception.ExecutionPlanValidationException: 
> contains is neither a function extension nor an aggregated attribute 
> extension, when creating query copyFromLocal in execution plan 
> "b38f8f76-c2cf-4288-a26a-cb2a30161b42"
>   at 
> org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:127)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:51)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:59)
>  ~[stormjar.jar:na]
>   at 
> org.apache.eagle.security.auditlog.HdfsUserCommandReassembler.init(HdfsUserCommandReassembler.java:130)
>  ~[stormjar.jar:na]
>   at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.prepare(JavaStormBoltWrapper.scala:36)
>  ~[stormjar.jar:na]
>   at 
> backtype.storm.daemon.executor$fn__5017$fn__5030.invoke(executor.clj:732) 
> ~[storm-core-0.9.3.2.2.4.2-2.jar:0.9.3.2.2.4.2-2]
>   at backtype.storm.util$async_loop$fn__452.invoke(util.clj:463) 
> ~[storm-core-0.9.3.2.2.4.2-2.jar:0.9.3.2.2.4.2-2]
>   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_79]
> Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: 
> contains is neither a function extension nor an aggregated attribute 
> extension, when creating query copyFromLocal
>   at 
> org.wso2.siddhi.core.util.parser.QueryParser.parse(QueryParser.java:109) 
> ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:117)
>  ~[stormjar.jar:na]
>   ... 8 common frames omitted
> Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: 
> contains is neither a function extension nor an aggregated attribute extension
>   at 
> org.wso2.siddhi.core.util.parser.ExpressionParser.parseExpression(ExpressionParser.java:244)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.ExpressionParser.parseExpression(ExpressionParser.java:103)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.SingleInputStreamParser.generateProcessor(SingleInputStreamParser.java:129)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.SingleInputStreamParser.parseInputStream(SingleInputStreamParser.java:86)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:92)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:134)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:134)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:134)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:134)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parse(StateInputStreamParser.java:171)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.StateInputStreamParser.parseInputStream(StateInputStreamParser.java:72)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.InputStreamParser.parse(InputStreamParser.java:57)
>  ~[stormjar.jar:na]
>   at 
> org.wso2.siddhi.core.util.parser.QueryParser.parse(QueryParser.java:64) 
> ~[stormjar.jar:na]
>   ... 9 common frames omitted
> {code}



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

[jira] [Updated] (EAGLE-35) [BUG] Policy sometimes can not be dynamically loaded correctly

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-35:
--
Fix Version/s: (was: 0.3.0)

> [BUG] Policy sometimes can not be dynamically loaded correctly
> --
>
> Key: EAGLE-35
> URL: https://issues.apache.org/jira/browse/EAGLE-35
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>Priority: Critical
>




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

[jira] [Closed] (EAGLE-109) add hdfs related ports mapping from docker container to host

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen closed EAGLE-109.
--
Resolution: Fixed

> add hdfs related ports mapping from docker container to host
> 
>
> Key: EAGLE-109
> URL: https://issues.apache.org/jira/browse/EAGLE-109
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhaokun Qin
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>




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

[jira] [Updated] (EAGLE-98) Eagle Pipeline Scheduler

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-98:
--
Fix Version/s: (was: 0.3.0)

> Eagle Pipeline Scheduler
> 
>
> Key: EAGLE-98
> URL: https://issues.apache.org/jira/browse/EAGLE-98
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Zhao, Qingwen
>
> h2. Features
> * High Level Stream-Oriented 
> * Declarative Streaming
> * Metadata Driven
> * Native Scala internal DSL
> * Support Scala Programing or Script/Configure in *.egl
> * Support static policy definition / dynamical policy loader
> * IDE friendly features like sql-prefix and xml as email template.
> * Name Reference
> h2. Syntax 
> {code:language=scala}
> // Topology Definition API by extends or script
> import org.apache.eagle.stream.dsl.experimental.KafkaInterface._
> import org.apache.eagle.stream.dsl.experimental.DruidInterface._
> // #!/bin/bash
> // exec scala "$0" "$@"
> // !#
> // # start
> define ("metricStream_1") as ("name" -> 'string, "value"->'double, 
> "timestamp"->'long) from
>   kafka(topic="metricStream_1",zk=conf"kafka.zk.hosts",deserializer="")
> define ("metricStream_2") as ("name" -> 'string, "value"->'double, 
> "timestamp"->'long) from
>   kafka(topic="metricStream_2")
> define ("logStream_3") from kafka(topic="logStream_3")
> // filter by function
> filter ("logStream_3") by {(line,collector) => collector.collect(line)} as 
> ("name" -> 'string, "value"->'double, "timestamp"->'long)
> // "logStream_3" as ("name" -> 'string, "value"->'double, "timestamp"->'long)
> // filter by pattern and rename stream
> filter("logStream_3"->"logStream_3_parsed") by 
> """(?\d{4}-\d{2}-\d{2})""".r as ("name" -> 'string, 
> "value"->'double, "timestamp"-> datetime("-MM-DD"))
> alert partitionBy "metricStream_1.metricType" parallism 1 by {sql"""
>   from metricStream_1[component=='dn' and 
> metricType=="RpcActivityForPort50020.RpcQueueTimeNumOps"].time[3600]
>   select sum(value) group by host output every 1 hour insert into alertStream;
> """}
> aggregate partitionBy "metricStream_1.metricType" parallism 2 by {sql"""
>   from metricStream_1[component=='dn' and 
> metricType=="RpcActivityForPort50020.RpcQueueTimeNumOps"].time[3600]
>   select sum(value) group by host output every 1 hour insert into 
> aggregatedMetricStream_1;
> """}
> 'alertStream ~> kafka("alert_topic",zk=conf"kafka.zk.hosts")
> "alertStream" to mail(
>   from = "sen...@eagle.incubator.apache.org",
>   to = "recei...@eagle.incubator.apache.org",
>   smtp = "localhost:25",
>   template =
> 
>   
>   Alert Notification
>   
>   
> Message
> $message
>   
> 
> )
> // split stream by logic
> 'aggregatedMetricStream_1 to kafka("aggregated_stream_dn") where "component 
> == 'dn'" partitionBy "aggregatedMetricStream_1.metricType"
> 'aggregatedMetricStream_1 ~> druid("aggregated_stream_nn")  where "component 
> == 'nn'" partitionBy "aggregatedMetricStream_1.metricType"
> // # end
> {code}



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

[jira] [Updated] (EAGLE-120) add system metric collector for hadoop performance monitoring

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-120:
---
Fix Version/s: (was: 0.3.0)

> add system metric collector for hadoop performance monitoring
> -
>
> Key: EAGLE-120
> URL: https://issues.apache.org/jira/browse/EAGLE-120
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Hao Chen
>
> today we have hadoop native metrics to collected, we need system metrics to 
> be collected and policy can be created upon that.
> https://github.com/apache/incubator-eagle/pull/49



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

[jira] [Updated] (EAGLE-77) Refactor config structure to avoid too many duplicated ugly config related code

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-77:
--
Fix Version/s: (was: 0.3.0)

> Refactor config structure to avoid too many duplicated ugly config related 
> code
> ---
>
> Key: EAGLE-77
> URL: https://issues.apache.org/jira/browse/EAGLE-77
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[GitHub] incubator-eagle pull request: tutorial for setting up the developm...

2016-02-18 Thread JingGe

GitHub user JingGe opened a pull request:

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

tutorial for setting up the development environment on mac



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

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

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

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


commit 67eab67aeecea120aff5d1fa803e876bd4a80759
Author: jinge 
Date:   2016-02-18T10:49:19Z

add new file

commit 5d15975ed9978c11077e9086923af6a2424ddb3e
Author: jinge 
Date:   2016-02-18T10:54:52Z

setup tutorial on mac

commit e1244302b5f2dc109765853a21496f9b83653bb8
Author: Jing Ge 
Date:   2016-02-18T10:59:19Z

Update SetupDevelopmentEnvOnMac.md

commit caf18d6f55b01dca9363996f9633664f8703ce92
Author: Jing Ge 
Date:   2016-02-18T11:00:57Z

Update SetupDevelopmentEnvOnMac.md

commit 29db595b4bf53dbd6cf6321b3f2791db7d73a5cc
Author: Jing Ge 
Date:   2016-02-18T11:15:35Z

Update SetupDevelopmentEnvOnMac.md




---
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: tutorial for setting up the developm...

2016-02-18 Thread RalphSu

Github user RalphSu commented on the pull request:

https://github.com/apache/incubator-eagle/pull/94#issuecomment-185749158
  
Excellent documentation. 
+1


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

[jira] [Updated] (EAGLE-116) StormTopologyCompiler's boltCache looks not working

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-116:
---
Affects Version/s: (was: 0.3.0)

> StormTopologyCompiler's boltCache looks not working
> ---
>
> Key: EAGLE-116
> URL: https://issues.apache.org/jira/browse/EAGLE-116
> Project: Eagle
>  Issue Type: Bug
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
>
> I saw boltCache is not used anymore, need investigate and clean that if 
> necessary.
>   val boltCache = scala.collection.mutable.Map[StreamProducer[Any], 
> StormBoltWrapper]()
> def createBoltIfAbsent(graph: StreamProducerGraph, producer : 
> StreamProducer[Any]): BaseRichBolt ={
> boltCache.get(producer) match{
>   case Some(bolt) => bolt
>   case None => {
> StormBoltFactory.getBoltWrapper(graph, producer, config)
>   }
> }
>   }



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

[jira] [Updated] (EAGLE-116) StormTopologyCompiler's boltCache looks not working

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-116:
---
Fix Version/s: (was: 0.3.0)

> StormTopologyCompiler's boltCache looks not working
> ---
>
> Key: EAGLE-116
> URL: https://issues.apache.org/jira/browse/EAGLE-116
> Project: Eagle
>  Issue Type: Bug
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
>
> I saw boltCache is not used anymore, need investigate and clean that if 
> necessary.
>   val boltCache = scala.collection.mutable.Map[StreamProducer[Any], 
> StormBoltWrapper]()
> def createBoltIfAbsent(graph: StreamProducerGraph, producer : 
> StreamProducer[Any]): BaseRichBolt ={
> boltCache.get(producer) match{
>   case Some(bolt) => bolt
>   case None => {
> StormBoltFactory.getBoltWrapper(graph, producer, config)
>   }
> }
>   }



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

[jira] [Updated] (EAGLE-141) fix some unit testing exception which is thrown within annoymous class

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-141:
---
Assignee: (was: Edward Zhang)

> fix some unit testing exception which is thrown within annoymous class
> --
>
> Key: EAGLE-141
> URL: https://issues.apache.org/jira/browse/EAGLE-141
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Priority: Minor
> Fix For: 0.3.0
>
>
> Sometimes unit test fails but throw exception within a annoymous inner class, 
> so it is not caught by junit framework.
> for example https://builds.apache.org/job/incubator-eagle-main/24/console



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

[jira] [Updated] (EAGLE-141) fix some unit testing exception which is thrown within annoymous class

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-141:
---
Assignee: Edward Zhang

> fix some unit testing exception which is thrown within annoymous class
> --
>
> Key: EAGLE-141
> URL: https://issues.apache.org/jira/browse/EAGLE-141
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: 0.3.0
>
>
> Sometimes unit test fails but throw exception within a annoymous inner class, 
> so it is not caught by junit framework.
> for example https://builds.apache.org/job/incubator-eagle-main/24/console



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

[jira] [Resolved] (EAGLE-141) fix some unit testing exception which is thrown within annoymous class

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang resolved EAGLE-141.

Resolution: Fixed

> fix some unit testing exception which is thrown within annoymous class
> --
>
> Key: EAGLE-141
> URL: https://issues.apache.org/jira/browse/EAGLE-141
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: 0.3.0
>
>
> Sometimes unit test fails but throw exception within a annoymous inner class, 
> so it is not caught by junit framework.
> for example https://builds.apache.org/job/incubator-eagle-main/24/console



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

[jira] [Commented] (EAGLE-141) fix some unit testing exception which is thrown within annoymous class

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang commented on EAGLE-141:


This is fixed by murkrishn, by somehow his name can't be in assignee.

> fix some unit testing exception which is thrown within annoymous class
> --
>
> Key: EAGLE-141
> URL: https://issues.apache.org/jira/browse/EAGLE-141
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: 0.3.0
>
>
> Sometimes unit test fails but throw exception within a annoymous inner class, 
> so it is not caught by junit framework.
> for example https://builds.apache.org/job/incubator-eagle-main/24/console



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

[jira] [Updated] (EAGLE-127) add NPM as pre-requisite for mvn eagle build

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-127:
---
Fix Version/s: (was: 0.3.0)

> add NPM as pre-requisite for mvn eagle build
> 
>
> Key: EAGLE-127
> URL: https://issues.apache.org/jira/browse/EAGLE-127
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Prasad Mujumdar
>Priority: Trivial
>
> NPM should be installed before mvn build. Normally people don't realize it is 
> because of NPM if the build fails. I think we should explicitly say we need 
> install NPM before mvn build.



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

Re: Work on Eagle 0.3.0 release has started.

2016-02-18 Thread Zhang, Edward (GDI Hadoop)

Looks all jira tickets are cleared, we can go ahead for next step for
release.

Thanks
Edward

On 2/9/16, 13:43, "Dendukuri, Hemanth"  wrote:

>
>I lately realized that we should use ³fixVersion² instead of
>³affectedVersion² to tag a particular jira for release.
>Kindly follow below steps.
>
>Link : 
>https://issues.apache.org/jira/browse/EAGLE-35?jql=project%20%3D%20EAGLE%2
>0AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%2
>0resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%200.3.0%20ORDER%20
>BY%20priority%20DESC
>
>Filter :  project = EAGLE AND status in (Open, "In Progress", Reopened)
>AND resolution = Unresolved AND fixVersion = 0.3.0 ORDER BY priority DESC
>
>If you want any of your Jiras to be included/removed from the list, just
>edit the jira and add/remove ³fixVersion² to 0.3.0/EMPTY.
>
>
>From: "Dendukuri, Hemanth"
>mailto:hdenduk...@ebay.com>>
>Date: Monday, February 8, 2016 at 9:16 PM
>To: 
>"dev@eagle.incubator.apache.org"
>mailto:dev@eagle.incubator.apache.org>>
>Subject: Work on Eagle 0.3.0 release has started.
>
>Hi Eagle Community,
>
>Created a tracking jira
>EAGLE-143  for the Eagle
>³0.3.0² release and planning to release a branch tentatively on 02/26.
>
>Here are the list of Jiras that are currently tagged for release ³0.3.0².
>Click on the link or use the filter below.
>Link : 
>https://issues.apache.org/jira/browse/EAGLE-35?jql=project%20%3D%20EAGLE%2
>0AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%2
>0resolution%20%3D%20Unresolved%20AND%20affectedVersion%20%3D%200.3.0%20ORD
>ER%20BY%20priority%20DESC
>Filter : project = EAGLE AND status in (Open, "In Progress", Reopened)
>AND resolution = Unresolved AND affectedVersion = 0.3.0 ORDER BY priority
>DESC
>
>If you want any of your Jiras to be included/removed from the list, just
>edit the jira and add/remove ³affectedVersion² to 0.3.0/EMPTY.
>
>Regards
>Hemanth

[jira] [Commented] (EAGLE-127) add NPM as pre-requisite for mvn eagle build

2016-02-18 Thread Jaspaul Chahal (JIRA)


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

Jaspaul Chahal commented on EAGLE-127:
--

yes, I didn't realize it failed due to NPM, I had to go thru the documentation 
again.

> add NPM as pre-requisite for mvn eagle build
> 
>
> Key: EAGLE-127
> URL: https://issues.apache.org/jira/browse/EAGLE-127
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Prasad Mujumdar
>Priority: Trivial
>
> NPM should be installed before mvn build. Normally people don't realize it is 
> because of NPM if the build fails. I think we should explicitly say we need 
> install NPM before mvn build.



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

[jira] [Commented] (EAGLE-127) add NPM as pre-requisite for mvn eagle build

2016-02-18 Thread Jaspaul Chahal (JIRA)


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

Jaspaul Chahal commented on EAGLE-127:
--

If try to build Eagle, where we don't have git installed, it fails. Why do we 
need git for build?

> add NPM as pre-requisite for mvn eagle build
> 
>
> Key: EAGLE-127
> URL: https://issues.apache.org/jira/browse/EAGLE-127
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Prasad Mujumdar
>Priority: Trivial
>
> NPM should be installed before mvn build. Normally people don't realize it is 
> because of NPM if the build fails. I think we should explicitly say we need 
> install NPM before mvn build.



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

Eagle 0.3 with Mysql

2016-02-18 Thread Jaspaul Chahal

Hi,


I am trying to get Eagle 0.3 (cloned yesterday) working with MySql as 
storage-type. I have created the tables mentioned at 
https://cwiki.apache.org/confluence/display/EAG/JDBC+Extension and also have 
put the eagle-storage-jdbc-0.3.0.jar in lib of Eagle service. It complained 
"java.lang.NoClassDefFoundError: org/apache/torque/TorqueException", so I have 
put torque-runtime-4.0.jar to lib and this error is gone.


Now, it is complaining "Table 'eagle.ipzone_ipzone' doesn't exist" while 
executing 'SELECT ipzone_ipzone.* FROM ipzone_ipzone WHERE 
(ipzone_ipzone.timestamp>=? AND ipzone_ipzone.timestamp

Re: Work on Eagle 0.3.0 release has started.

2016-02-18 Thread Dendukuri, Hemanth

Thanks everyone for working on their jiras and updating the progress. The next 
step is to sanitize the Jira.

1) There are some resolved issues for which fixVersion is Empty. We need to 
bulk edit to set fixedVersion to 0.3.0 (I don’t have access to edit closed 
bugs, Admin can do build changes for this query)
https://issues.apache.org/jira/browse/EAGLE-28?jql=project%20%3D%20EAGLE%20AND%20status%20not%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20is%20EMPTY%20ORDER%20BY%20priority%20DESC
 

2) I had a quick look at open Jiras and listed out few which need a 
reconsideration to be included in this release.
https://issues.apache.org/jira/browse/EAGLE-162 (incomplete class path fails 
launching Eagle DAM HDFS in sandbox)

https://issues.apache.org/jira/browse/EAGLE-103 (add comments to readme to tell 
users: currently, eagle is tested under jdk1.7.x, may have compile error with 
jdk1.8.x)

https://issues.apache.org/jira/browse/EAGLE-157 (policy metric should be 
refreshed every minute)
https://issues.apache.org/jira/browse/EAGLE-127 (add NPM as pre-requisite for 
mvn eagle build)  
https://issues.apache.org/jira/browse/EAGLE-100 (provide tools to collect 
hadoop jmx metrics)
https://issues.apache.org/jira/browse/EAGLE-122 (Create a generic notification 
plugin for integrating alerts) 
https://issues.apache.org/jira/browse/EAGLE-81  (Notification Plugin Framework)
https://issues.apache.org/jira/browse/EAGLE-154 (hadoop-metric monitoring 
sandbox starter script)

Regards
Hemanth 




On 2/18/16, 10:50 AM, "Zhang, Edward (GDI Hadoop)"  wrote:

>Looks all jira tickets are cleared, we can go ahead for next step for
>release.
>
>Thanks
>Edward
>
>On 2/9/16, 13:43, "Dendukuri, Hemanth"  wrote:
>
>>
>>I lately realized that we should use ³fixVersion² instead of
>>³affectedVersion² to tag a particular jira for release.
>>Kindly follow below steps.
>>
>>Link : 
>>https://issues.apache.org/jira/browse/EAGLE-35?jql=project%20%3D%20EAGLE%2
>>0AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%2
>>0resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%200.3.0%20ORDER%20
>>BY%20priority%20DESC
>>
>>Filter :  project = EAGLE AND status in (Open, "In Progress", Reopened)
>>AND resolution = Unresolved AND fixVersion = 0.3.0 ORDER BY priority DESC
>>
>>If you want any of your Jiras to be included/removed from the list, just
>>edit the jira and add/remove ³fixVersion² to 0.3.0/EMPTY.
>>
>>
>>From: "Dendukuri, Hemanth"
>>mailto:hdenduk...@ebay.com>>
>>Date: Monday, February 8, 2016 at 9:16 PM
>>To: 
>>"dev@eagle.incubator.apache.org"
>>mailto:dev@eagle.incubator.apache.org>>
>>Subject: Work on Eagle 0.3.0 release has started.
>>
>>Hi Eagle Community,
>>
>>Created a tracking jira
>>EAGLE-143  for the Eagle
>>³0.3.0² release and planning to release a branch tentatively on 02/26.
>>
>>Here are the list of Jiras that are currently tagged for release ³0.3.0².
>>Click on the link or use the filter below.
>>Link : 
>>https://issues.apache.org/jira/browse/EAGLE-35?jql=project%20%3D%20EAGLE%2
>>0AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%2
>>0resolution%20%3D%20Unresolved%20AND%20affectedVersion%20%3D%200.3.0%20ORD
>>ER%20BY%20priority%20DESC
>>Filter : project = EAGLE AND status in (Open, "In Progress", Reopened)
>>AND resolution = Unresolved AND affectedVersion = 0.3.0 ORDER BY priority
>>DESC
>>
>>If you want any of your Jiras to be included/removed from the list, just
>>edit the jira and add/remove ³affectedVersion² to 0.3.0/EMPTY.
>>
>>Regards
>>Hemanth
>

RE: Policy Alerts are not generated in Eagle

2016-02-18 Thread Nagalkar, Sanjay Contractor


Hi Daniel,

I did the below test and I was able to receive the messages in consumer. 
Infact, I also tried below steps with toic ‘sandbox_hdfs_audit_log’ and was 
able to see my test messages.

Still I don’t see the HDFS policy alerts in eagle

Thanks
Sanjay

From: Daniel Zhou [mailto:daniel.z...@dataguise.com]
Sent: Tuesday, February 16, 2016 5:28 PM
To: dev@eagle.incubator.apache.org; Nagalkar, Sanjay Contractor
Subject: RE: Policy Alerts are not generated in Eagle

Hi, Nagalkar

Could you check if your Kafka works ? Use these steps:

1.   Create a topic:

bin/kafka-topics.sh --create --zookeeper localhost:2181 --replication-factor 1 
--partitions 1 --topic test

2.   Check if topic  “test” is created:

bin/kafka-topics.sh --list --zookeeper localhost:2181

3.   Open a terminal and use producer to send message:

bin/kafka-console-producer.sh --broker-list hostname:6667 --topic test

// then type some messages

4.   Open another terminal and see if consumer get the message:

bin/kafka-console-consumer.sh --zookeeper localhost:2181 --topic test 
--from-beginning

// check if messages received
If no messages received, you need to double check the setting of Kafka.

Regards,
Daniel

From: Nagalkar, Sanjay Contractor [mailto:sanjay.nagal...@ssa.gov]
Sent: Tuesday, February 16, 2016 1:58 PM
To: 'dev@eagle.incubator.apache.org' 
mailto:dev@eagle.incubator.apache.org>>
Subject: FW: Policy Alerts are not generated in Eagle

Hello,

just wondering if there is any update on this issue I reported earlier .

Below is the detailed information about the  encountered issue and the 
configuration made in  our eagle setup:

We are planning to implement some tool for  sensitive data  monitoring /audit 
and for this purpose , I am exploring Eagle to see if it fits our requirements. 
My goal is play with eagle in Horton works sandbox environment and once 
comfortable then  move to production.

I have followed the Eagle user guide  and  had setup Horton works sandbox   and 
 eagle service as instructed in the User Docs. (I did not use the Ambari 
plug-in for eagle as I had some issue with it so I am starting eagle services 
manually from command line).


I have configured  HIVE and HDFS policies but I am not seeing any Alerts 
generated for data access by these policy.


For HDFS policy –
I have setup policy for /tmp/private file access but here I am receiving error 
while writing to KAFKA topic.

I am getting "connection Refused" error.

I have a Kafka topic 'Sandbox_hdfs_audit_log' and hdfs action events are not 
logged into this topic. when I view kafka.out , I see

ERROR Exception emitting metrics - 
org.apache.hadoop.metrics2.sink.timelineUnableToConnectException:java.net.ConnectException.


I have verified that the Kafka broker is up and configured ( Pls. see below log 
screenshots )



For HIVE policy -
 I have setup Hive policy for PHONE_NUMBER field setup. When I use hive from 
Horton works Sandbox and  execute the HIVE queries against XADEMO schema to 
select PHONE_NUMBER field, Eagle is not generating any alerts for accessing 
PHONE_NUMBER field .

Pls. click below link to see  document outlining steps for HIVE query and eagle 
policy.

https://community.hortonworks.com/storage/attachments/1964-dtempsanbox-hive-eagle-issue.pdf


Please let me know if you  need more information on this.

Your help with this is very much appreciated.

Thanks
Sanjay Nagalkar
Ph: 410-371-3299




On Wed, Feb 10, 2016 at 12:55 PM, Nagalkar, Sanjay Contractor 
mailto:sanjay.nagal...@ssa.gov>> wrote:



Hello



I am having issues generating policy alerts for Apache Eagle.



I have configured Hive and HDFS  policies as per the instructions in the Eagle 
DOCS but I am not seeing any alerts for my Hive and HDFS policy.



I am executing HIVE queries against XADEMO schema to pull PHONE_NUMBER field 
via HDP sandbox and I was expecting to see some alerts for  this data access in 
eagle. However,  I have no policy alerts .



Similar situation with HDFS file access. No alerts for /tmp/private file access.



Please let me know if there is  something that I am missing.



Thanks

Sanjay Nagalkar

RE: Policy Alerts are not generated in Eagle

2016-02-18 Thread Daniel Zhou

Hi Sanjay,

Seems your KAFKA works.
So when you run bin/kafka-console-consumer.sh --zookeeper localhost:2181 
--topic sandbox_hdfs_audit_log --from-beginning
Can you see the HDFS messages? (not your test messages)

If not, I suggest you to open Storm UI “localhost:8744” and click the topology 
summary,  find  the exception/error, and paste them in the email.
And also, double check  step3 in this: 
http://eagle.incubator.apache.org/docs/import-hdfs-auditLog.html

Regards,
Daniel





From: Nagalkar, Sanjay Contractor [mailto:sanjay.nagal...@ssa.gov]
Sent: Thursday, February 18, 2016 2:02 PM
To: Daniel Zhou ; dev@eagle.incubator.apache.org
Subject: RE: Policy Alerts are not generated in Eagle


Hi Daniel,

I did the below test and I was able to receive the messages in consumer. 
Infact, I also tried below steps with toic ‘sandbox_hdfs_audit_log’ and was 
able to see my test messages.

Still I don’t see the HDFS policy alerts in eagle

Thanks
Sanjay

From: Daniel Zhou [mailto:daniel.z...@dataguise.com]
Sent: Tuesday, February 16, 2016 5:28 PM
To: dev@eagle.incubator.apache.org; 
Nagalkar, Sanjay Contractor
Subject: RE: Policy Alerts are not generated in Eagle

Hi, Nagalkar

Could you check if your Kafka works ? Use these steps:

1.   Create a topic:

bin/kafka-topics.sh --create --zookeeper localhost:2181 --replication-factor 1 
--partitions 1 --topic test

2.   Check if topic  “test” is created:

bin/kafka-topics.sh --list --zookeeper localhost:2181

3.   Open a terminal and use producer to send message:

bin/kafka-console-producer.sh --broker-list hostname:6667 --topic test

// then type some messages

4.   Open another terminal and see if consumer get the message:

bin/kafka-console-consumer.sh --zookeeper localhost:2181 --topic test 
--from-beginning

// check if messages received
If no messages received, you need to double check the setting of Kafka.

Regards,
Daniel

From: Nagalkar, Sanjay Contractor [mailto:sanjay.nagal...@ssa.gov]
Sent: Tuesday, February 16, 2016 1:58 PM
To: 'dev@eagle.incubator.apache.org' 
mailto:dev@eagle.incubator.apache.org>>
Subject: FW: Policy Alerts are not generated in Eagle

Hello,

just wondering if there is any update on this issue I reported earlier .

Below is the detailed information about the  encountered issue and the 
configuration made in  our eagle setup:

We are planning to implement some tool for  sensitive data  monitoring /audit 
and for this purpose , I am exploring Eagle to see if it fits our requirements. 
My goal is play with eagle in Horton works sandbox environment and once 
comfortable then  move to production.

I have followed the Eagle user guide  and  had setup Horton works sandbox   and 
 eagle service as instructed in the User Docs. (I did not use the Ambari 
plug-in for eagle as I had some issue with it so I am starting eagle services 
manually from command line).


I have configured  HIVE and HDFS policies but I am not seeing any Alerts 
generated for data access by these policy.


For HDFS policy –
I have setup policy for /tmp/private file access but here I am receiving error 
while writing to KAFKA topic.

I am getting "connection Refused" error.

I have a Kafka topic 'Sandbox_hdfs_audit_log' and hdfs action events are not 
logged into this topic. when I view kafka.out , I see

ERROR Exception emitting metrics - 
org.apache.hadoop.metrics2.sink.timelineUnableToConnectException:java.net.ConnectException.


I have verified that the Kafka broker is up and configured ( Pls. see below log 
screenshots )



For HIVE policy -
 I have setup Hive policy for PHONE_NUMBER field setup. When I use hive from 
Horton works Sandbox and  execute the HIVE queries against XADEMO schema to 
select PHONE_NUMBER field, Eagle is not generating any alerts for accessing 
PHONE_NUMBER field .

Pls. click below link to see  document outlining steps for HIVE query and eagle 
policy.

https://community.hortonworks.com/storage/attachments/1964-dtempsanbox-hive-eagle-issue.pdf


Please let me know if you  need more information on this.

Your help with this is very much appreciated.

Thanks
Sanjay Nagalkar
Ph: 410-371-3299




On Wed, Feb 10, 2016 at 12:55 PM, Nagalkar, Sanjay Contractor 
mailto:sanjay.nagal...@ssa.gov>> wrote:



Hello



I am having issues generating policy alerts for Apache Eagle.



I have configured Hive and HDFS  policies as per the instructions in the Eagle 
DOCS but I am not seeing any alerts for my Hive and HDFS policy.



I am executing HIVE queries against XADEMO schema to pull PHONE_NUMBER field 
via HDP sandbox and I was expecting to see some alerts for  this data access in 
eagle. However,  I have no policy alerts .



Similar situation with HDFS file access. No alerts for /tmp/private file access.



Please let me know if there is  something that I am missing.



Thanks

Sanjay Nagalkar

[GitHub] incubator-eagle pull request: tutorial for setting up the developm...

2016-02-18 Thread yonzhang

Github user yonzhang commented on the pull request:

https://github.com/apache/incubator-eagle/pull/94#issuecomment-185984322
  
This is good. 
Could we improve in next version to set up IDE to run Eagle? I see Apache 
Kylin has nice "development" wiki page. http://kylin.apache.org/development/, 
we should put that into Eagle site http://eagle.incubator.apache.org


---
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-158 Remove org.apache.eagle.da...

2016-02-18 Thread yonzhang

Github user yonzhang commented on the pull request:

https://github.com/apache/incubator-eagle/pull/93#issuecomment-185984482
  
good to go! 
We should always keep code clean and no legacy code as much as possible.


---
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-158) Disable org.apache.eagle.datastream.EagleTuple

2016-02-18 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-158:
--

Github user yonzhang commented on the pull request:

https://github.com/apache/incubator-eagle/pull/93#issuecomment-185984482
  
good to go! 
We should always keep code clean and no legacy code as much as possible.


> Disable org.apache.eagle.datastream.EagleTuple
> --
>
> Key: EAGLE-158
> URL: https://issues.apache.org/jira/browse/EAGLE-158
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> - Remove org.apache.eagle.datastream.EagleTuple 
> - Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN



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

[jira] [Assigned] (EAGLE-100) provide tools to collect hadoop jmx metrics

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang reassigned EAGLE-100:
--

Assignee: Edward Zhang

> provide tools to collect hadoop jmx metrics
> ---
>
> Key: EAGLE-100
> URL: https://issues.apache.org/jira/browse/EAGLE-100
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Assignee: Edward Zhang
>Priority: Critical
>
> Provide scripts to collect Hadoop jmx metrics and evently sent these metrics 
> to stdout or Kafka.
> A user can easily run these scrips by crontab 



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

[jira] [Updated] (EAGLE-100) provide tools to collect hadoop jmx metrics

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-100:
---
Assignee: Hao Chen  (was: Edward Zhang)

> provide tools to collect hadoop jmx metrics
> ---
>
> Key: EAGLE-100
> URL: https://issues.apache.org/jira/browse/EAGLE-100
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Assignee: Hao Chen
>Priority: Critical
>
> Provide scripts to collect Hadoop jmx metrics and evently sent these metrics 
> to stdout or Kafka.
> A user can easily run these scrips by crontab 



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

[jira] [Commented] (EAGLE-100) provide tools to collect hadoop jmx metrics

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang commented on EAGLE-100:


[~haoch]Is this fixed, if yes, please close this ticket

> provide tools to collect hadoop jmx metrics
> ---
>
> Key: EAGLE-100
> URL: https://issues.apache.org/jira/browse/EAGLE-100
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Assignee: Hao Chen
>Priority: Critical
> Fix For: 0.3.0
>
>
> Provide scripts to collect Hadoop jmx metrics and evently sent these metrics 
> to stdout or Kafka.
> A user can easily run these scrips by crontab 



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

[jira] [Updated] (EAGLE-100) provide tools to collect hadoop jmx metrics

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-100:
---
Fix Version/s: 0.3.0

> provide tools to collect hadoop jmx metrics
> ---
>
> Key: EAGLE-100
> URL: https://issues.apache.org/jira/browse/EAGLE-100
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Assignee: Hao Chen
>Priority: Critical
> Fix For: 0.3.0
>
>
> Provide scripts to collect Hadoop jmx metrics and evently sent these metrics 
> to stdout or Kafka.
> A user can easily run these scrips by crontab 



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

[jira] [Updated] (EAGLE-122) Create a generic notification plugin for integrating alerts

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-122:
---
Fix Version/s: 0.3.0

> Create a generic notification plugin for integrating alerts
> ---
>
> Key: EAGLE-122
> URL: https://issues.apache.org/jira/browse/EAGLE-122
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Aroop Maliakkal
>Assignee: Edward Zhang
> Fix For: 0.3.0
>
>
> If a user wants to use Eagle framework to send alerts to third parties, Eagle 
> should expose a generic notification plugin with well documented 
> contract/grammer so that user can forward the alerts generated by other 
> frameworks to Eagle and use Eagle for forwarding it to respective 
> destinations.



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

[jira] [Updated] (EAGLE-100) provide tools to collect hadoop jmx metrics

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-100:
---
Affects Version/s: 0.3.0

> provide tools to collect hadoop jmx metrics
> ---
>
> Key: EAGLE-100
> URL: https://issues.apache.org/jira/browse/EAGLE-100
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Zhao, Qingwen
>Assignee: Hao Chen
>Priority: Critical
> Fix For: 0.3.0
>
>
> Provide scripts to collect Hadoop jmx metrics and evently sent these metrics 
> to stdout or Kafka.
> A user can easily run these scrips by crontab 



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

[jira] [Updated] (EAGLE-122) Create a generic notification plugin for integrating alerts

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-122:
---
Affects Version/s: 0.3.0

> Create a generic notification plugin for integrating alerts
> ---
>
> Key: EAGLE-122
> URL: https://issues.apache.org/jira/browse/EAGLE-122
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Aroop Maliakkal
>Assignee: Edward Zhang
> Fix For: 0.3.0
>
>
> If a user wants to use Eagle framework to send alerts to third parties, Eagle 
> should expose a generic notification plugin with well documented 
> contract/grammer so that user can forward the alerts generated by other 
> frameworks to Eagle and use Eagle for forwarding it to respective 
> destinations.



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

[jira] [Assigned] (EAGLE-122) Create a generic notification plugin for integrating alerts

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang reassigned EAGLE-122:
--

Assignee: Edward Zhang

> Create a generic notification plugin for integrating alerts
> ---
>
> Key: EAGLE-122
> URL: https://issues.apache.org/jira/browse/EAGLE-122
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Aroop Maliakkal
>Assignee: Edward Zhang
> Fix For: 0.3.0
>
>
> If a user wants to use Eagle framework to send alerts to third parties, Eagle 
> should expose a generic notification plugin with well documented 
> contract/grammer so that user can forward the alerts generated by other 
> frameworks to Eagle and use Eagle for forwarding it to respective 
> destinations.



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

[jira] [Updated] (EAGLE-81) Notification Plugin Framework

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-81:
--
Fix Version/s: 0.3.0

> Notification Plugin Framework
> -
>
> Key: EAGLE-81
> URL: https://issues.apache.org/jira/browse/EAGLE-81
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Senthilkumar
>Assignee: Senthilkumar
> Fix For: 0.3.0
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Today notification is only allowed for email .. We need more notification 
> methods to send alert to external system . 



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

[jira] [Resolved] (EAGLE-122) Create a generic notification plugin for integrating alerts

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang resolved EAGLE-122.

Resolution: Duplicate

duplicated for https://issues.apache.org/jira/browse/EAGLE-81

> Create a generic notification plugin for integrating alerts
> ---
>
> Key: EAGLE-122
> URL: https://issues.apache.org/jira/browse/EAGLE-122
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Aroop Maliakkal
>Assignee: Edward Zhang
> Fix For: 0.3.0
>
>
> If a user wants to use Eagle framework to send alerts to third parties, Eagle 
> should expose a generic notification plugin with well documented 
> contract/grammer so that user can forward the alerts generated by other 
> frameworks to Eagle and use Eagle for forwarding it to respective 
> destinations.



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

[jira] [Closed] (EAGLE-122) Create a generic notification plugin for integrating alerts

2016-02-18 Thread Edward Zhang (JIRA)


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

Edward Zhang closed EAGLE-122.
--

> Create a generic notification plugin for integrating alerts
> ---
>
> Key: EAGLE-122
> URL: https://issues.apache.org/jira/browse/EAGLE-122
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Aroop Maliakkal
>Assignee: Edward Zhang
> Fix For: 0.3.0
>
>
> If a user wants to use Eagle framework to send alerts to third parties, Eagle 
> should expose a generic notification plugin with well documented 
> contract/grammer so that user can forward the alerts generated by other 
> frameworks to Eagle and use Eagle for forwarding it to respective 
> destinations.



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

[GitHub] incubator-eagle pull request: EAGLE-154 hadoop-metric monitoring s...

2016-02-18 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-154) hadoop-metric monitoring sandbox starter script

2016-02-18 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-154:
--

Github user asfgit closed the pull request at:

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


> hadoop-metric monitoring sandbox starter script
> ---
>
> Key: EAGLE-154
> URL: https://issues.apache.org/jira/browse/EAGLE-154
> Project: Eagle
>  Issue Type: Task
>Reporter: hemanth dendukuri
>Assignee: hemanth dendukuri
>
> Create a sandbox start script that makes sure, hadoop metric monitoring runs 
> on new sandbox. 



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

[GitHub] incubator-eagle pull request: EAGLE-158 Remove org.apache.eagle.da...

2016-02-18 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-158) Disable org.apache.eagle.datastream.EagleTuple

2016-02-18 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-158:
--

Github user asfgit closed the pull request at:

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


> Disable org.apache.eagle.datastream.EagleTuple
> --
>
> Key: EAGLE-158
> URL: https://issues.apache.org/jira/browse/EAGLE-158
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> - Remove org.apache.eagle.datastream.EagleTuple 
> - Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN



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

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

2016-02-18 Thread Apache Jenkins Server

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

Re: Request For Wiki Access

2016-02-18 Thread Dendukuri, Hemanth

Hao, 

   Please grant me access to WIKI,I want to create release checklist wiki.

Regards
Hemanth

On 2/9/16, 10:20 AM, "Dendukuri, Hemanth"  wrote:

>Hi, 
>
> Kindly grant me(hdendukuri) access to Wiki. 
> https://cwiki.apache.org/confluence/display/EAG/Eagle 
>
>@Prasad do you have access to Eagle wiki to add release steps ? 
>
>Regards
>Hemanth 
>

Re: Request For Wiki Access

2016-02-18 Thread Chen, Hao

Hi Hemanth,

What’s your wiki account?

Thanks,
Hao



On 2/19/16, 9:20 AM, "Dendukuri, Hemanth"  wrote:

>Hao, 
>
>   Please grant me access to WIKI,I want to create release checklist wiki.
>
>Regards
>Hemanth
> 
>
>
>
>
>On 2/9/16, 10:20 AM, "Dendukuri, Hemanth"  wrote:
>
>>Hi, 
>>
>> Kindly grant me(hdendukuri) access to Wiki. 
>> https://cwiki.apache.org/confluence/display/EAG/Eagle 
>>
>>@Prasad do you have access to Eagle wiki to add release steps ? 
>>
>>Regards
>>Hemanth 
>>

Re: Request For Wiki Access

2016-02-18 Thread Chen, Hao

Created, please have a try.



On 2/19/16, 11:13 AM, "Chen, Hao"  wrote:

>Hi Hemanth,
>
>What’s your wiki account?
>
>Thanks,
>Hao
>
>
>
>On 2/19/16, 9:20 AM, "Dendukuri, Hemanth"  wrote:
>
>>Hao, 
>>
>>   Please grant me access to WIKI,I want to create release checklist wiki.
>>
>>Regards
>>Hemanth
>> 
>>
>>
>>
>>
>>On 2/9/16, 10:20 AM, "Dendukuri, Hemanth"  wrote:
>>
>>>Hi, 
>>>
>>> Kindly grant me(hdendukuri) access to Wiki. 
>>> https://cwiki.apache.org/confluence/display/EAG/Eagle 
>>>
>>>@Prasad do you have access to Eagle wiki to add release steps ? 
>>>
>>>Regards
>>>Hemanth 
>>>

[jira] [Updated] (EAGLE-158) Disable org.apache.eagle.datastream.EagleTuple

2016-02-18 Thread Hao Chen (JIRA)


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

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

> Disable org.apache.eagle.datastream.EagleTuple
> --
>
> Key: EAGLE-158
> URL: https://issues.apache.org/jira/browse/EAGLE-158
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> - Remove org.apache.eagle.datastream.EagleTuple 
> - Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN



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

[jira] [Closed] (EAGLE-158) Disable org.apache.eagle.datastream.EagleTuple

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen closed EAGLE-158.
--

> Disable org.apache.eagle.datastream.EagleTuple
> --
>
> Key: EAGLE-158
> URL: https://issues.apache.org/jira/browse/EAGLE-158
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> - Remove org.apache.eagle.datastream.EagleTuple 
> - Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN



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

[jira] [Resolved] (EAGLE-158) Disable org.apache.eagle.datastream.EagleTuple

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen resolved EAGLE-158.

Resolution: Resolved

> Disable org.apache.eagle.datastream.EagleTuple
> --
>
> Key: EAGLE-158
> URL: https://issues.apache.org/jira/browse/EAGLE-158
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> - Remove org.apache.eagle.datastream.EagleTuple 
> - Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN



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

[jira] [Closed] (EAGLE-154) hadoop-metric monitoring sandbox starter script

2016-02-18 Thread hemanth dendukuri (JIRA)


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

hemanth dendukuri closed EAGLE-154.
---
   Resolution: Done
Fix Version/s: 0.3.0

> hadoop-metric monitoring sandbox starter script
> ---
>
> Key: EAGLE-154
> URL: https://issues.apache.org/jira/browse/EAGLE-154
> Project: Eagle
>  Issue Type: Task
>Reporter: hemanth dendukuri
>Assignee: hemanth dendukuri
> Fix For: 0.3.0
>
>
> Create a sandbox start script that makes sure, hadoop metric monitoring runs 
> on new sandbox. 



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

[jira] [Updated] (EAGLE-158) Disable org.apache.eagle.datastream.EagleTuple

2016-02-18 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-158:
---
Affects Version/s: 0.3.0

> Disable org.apache.eagle.datastream.EagleTuple
> --
>
> Key: EAGLE-158
> URL: https://issues.apache.org/jira/browse/EAGLE-158
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> - Remove org.apache.eagle.datastream.EagleTuple 
> - Replace all  org.apache.eagle.datastream.TupleN with scala.TupleN



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

Re: Request For Wiki Access

2016-02-18 Thread Dendukuri, Hemanth

I am able to Edit and Create wiki in Eagle space. thanks. 

On 2/18/16, 7:15 PM, "Chen, Hao"  wrote:

>Created, please have a try.
>
>
>
>On 2/19/16, 11:13 AM, "Chen, Hao"  wrote:
>
>>Hi Hemanth,
>>
>>What’s your wiki account?
>>
>>Thanks,
>>Hao
>>
>>
>>
>>On 2/19/16, 9:20 AM, "Dendukuri, Hemanth"  wrote:
>>
>>>Hao, 
>>>
>>>   Please grant me access to WIKI,I want to create release checklist 
>>> wiki.
>>>
>>>Regards
>>>Hemanth
>>> 
>>>
>>>
>>>
>>>
>>>On 2/9/16, 10:20 AM, "Dendukuri, Hemanth"  wrote:
>>>
Hi, 

 Kindly grant me(hdendukuri) access to Wiki. 
 https://cwiki.apache.org/confluence/display/EAG/Eagle 

@Prasad do you have access to Eagle wiki to add release steps ? 

Regards
Hemanth

Re: HDFS topology not working.

2016-02-18 Thread Dendukuri, Hemanth

Hao, 

  I am still able to reproduce this issue.

Regards
Hemanth  




On 2/4/16, 10:42 AM, "Dendukuri, Hemanth"  wrote:

>Hao, 
>
>  I am just using "mvn clean install” command to build the and script 
> "examples/eagle-sandbox-starter.sh" to deploy. Please find content of file 
> “str.siddhiext”, below. 
>
>
>  charAt=org.wso2.siddhi.extension.string.CharAtFunctionExtension
>coalesce=org.wso2.siddhi.extension.string.CoalesceFunctionExtension
>concat=org.wso2.siddhi.extension.string.ConcatFunctionExtension
>length=org.wso2.siddhi.extension.string.LengthFunctionExtension
>lower=org.wso2.siddhi.extension.string.LowerFunctionExtension
>regexp=org.wso2.siddhi.extension.string.RegexpFunctionExtension
>repeat=org.wso2.siddhi.extension.string.RepeatFunctionExtension
>replaceAll=org.wso2.siddhi.extension.string.ReplaceAllFunctionExtension
>replaceFirst=org.wso2.siddhi.extension.string.ReplaceFirstFunctionExtension
>reverse=org.wso2.siddhi.extension.string.ReverseFunctionExtension
>strcmp=org.wso2.siddhi.extension.string.StrcmpFunctionExtension
>substr=org.wso2.siddhi.extension.string.SubstrFunctionExtension
>trim=org.wso2.siddhi.extension.string.TrimFunctionExtension
>upper=org.wso2.siddhi.extension.string.UpperFunctionExtension
>hex=org.wso2.siddhi.extension.string.HexFunctionExtension
>unhex=org.wso2.siddhi.extension.string.UnhexFunctionExtension
>equalsIgnoreCase=org.apache.eagle.policy.siddhi.extension.EqualsIgnoreCaseExtension
>containsIgnoreCase=org.apache.eagle.policy.siddhi.extension.ContainsIgnoreCaseExtension
>regexpIgnoreCase=org.apache.eagle.policy.siddhi.extension.RegexpIgnoreCaseFunctionExtension
>
>  
> 
>Regards
>Hemanth
>
>
>
>
>On 2/3/16, 5:41 PM, "Hao Chen"  wrote:
>
>>Hemanth,
>>
>>How do you build the package? Could you extract the siddhiext file in your
>>topology.jar and paste in this thread?
>>
>>Regards,
>>Hao
>>
>>On Thu, Feb 4, 2016 at 9:38 AM, Hao Chen  wrote:
>>
>>> It has nothing to do with policy definition, it should be because the
>>> str.siddhiext file is not correctly packaged.
>>>
>>> Regards,
>>> Hao
>>>
>>> On Thu, Feb 4, 2016 at 9:22 AM, Dendukuri, Hemanth 
>>> wrote:
>>>
 I have only one HDFS policy, which is the default one

 from hdfsAuditLogEventStream[(cmd=='open') and (src=='/tmp/private')]
 select * insert into outputStream


 Regards
 Hemanth




 On 2/3/16, 5:16 PM, "Liangfei.Su"  wrote:

 >Errors from the siddhi parser. Can you also the post the policy
 definition?
 >
 >On Thu, Feb 4, 2016 at 9:13 AM, Dendukuri, Hemanth 
 >wrote:
 >
 >> Hi,
 >>
 >>
 >> I see below exception in the log.
 >>
 >>
 >>
 >> org.wso2.siddhi.query.api.exception.ExecutionPlanValidationException:
 >> contains is neither a function extension nor an aggregated attribute
 >> extension, when creating query copyFromLocal in execution plan
 >> "ab205b61-cc34-4e7a-87fc-f234b38a1909"
 >>
 >> at
 >>
 org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:127)
 >> ~[stormjar.jar:na]
 >>
 >> at
 >>
 org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:51)
 >> ~[stormjar.jar:na]
 >>
 >> at
 >>
 org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:59)
 >> ~[stormjar.jar:na]
 >>
 >> at
 >>
 org.apache.eagle.security.auditlog.HdfsUserCommandReassembler.init(HdfsUserCommandReassembler.java:130)
 >> ~[stormjar.jar:na]
 >>
 >> at
 >>
 org.apache.eagle.datastream.storm.JavaStormBoltWrapper.prepare(JavaStormBoltWrapper.scala:36)
 >> ~[stormjar.jar:na]
 >>
 >> at
 >>
 backtype.storm.daemon.executor$fn__5017$fn__5030.invoke(executor.clj:732)
 >> ~[storm-core-0.9.3.2.2.4.2-2.jar:0.9.3.2.2.4.2-2]
 >>
 >> at backtype.storm.util$async_loop$fn__452.invoke(util.clj:463)
 >> ~[storm-core-0.9.3.2.2.4.2-2.jar:0.9.3.2.2.4.2-2]
 >>
 >> 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_79]
 >>
 >> Caused by:
 org.wso2.siddhi.core.exception.ExecutionPlanCreationException:
 >> contains is neither a function extension nor an aggregated attribute
 >> extension, when creating query copyFromLocal
 >>
 >> at
 >>
 org.wso2.siddhi.core.util.parser.QueryParser.parse(QueryParser.java:109)
 >> ~[stormjar.jar:na]
 >>
 >> at
 >>
 org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:117)
 >> ~[stormjar.jar:na]
 >>
 >> ... 8 common frames omitted
 >>
 >> Caused by:
 org.wso2.siddhi.core.exception.ExecutionPlanCreationException:
 >> contains is neither a function extension nor an aggregated attribute
 >> extension
 >>
 >> at
 >>
 org.wso2.siddhi.core.util.parser.ExpressionParser.pa

[jira] [Updated] (EAGLE-162) incomplete class path fails launching Eagle DAM HDFS in sandbox (Ambari Eagle Service)

2016-02-18 Thread hemanth dendukuri (JIRA)


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

hemanth dendukuri updated EAGLE-162:

Summary: incomplete class path fails launching Eagle DAM HDFS in sandbox 
(Ambari Eagle Service)  (was: incomplete class path fails launching Eagle DAM 
HDFS in sandbox)

> incomplete class path fails launching Eagle DAM HDFS in sandbox (Ambari Eagle 
> Service)
> --
>
> Key: EAGLE-162
> URL: https://issues.apache.org/jira/browse/EAGLE-162
> Project: Eagle
>  Issue Type: Bug
>Reporter: Michael Wu
>Assignee: Hao Chen
>
> When I tried to start Eagle DAM HDFS in sandbox, it failed and threw an error 
> with message: "Could not find or load main class 
> eagle.security.auditlog.HdfsAuditLogProcessorMain".
> According to stacktrace of the error, I refer to 
> incubator-eagle/eagle-external/eagle-ambari/lib/EAGLE/package/scripts/actions.py
>  and found, there are several lines with the incomplete class path configured 
> for main_class variable, they are: line 67, 92, and 117. Please help fix them 
> accordingly.
> Paste error stacktrace here:
> 2016-02-18 05:45:36,221 - Error while executing command 'start':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 214, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/EAGLE/0.0.1/package/scripts/eagle_hdfs_topology.py",
>  line 78, in start
> eagle_hdfs_topology_exec(action = 'start')
>   File 
> "/var/lib/ambari-agent/cache/common-services/EAGLE/0.0.1/package/scripts/actions.py",
>  line 110, in eagle_hdfs_topology_exec
> Execute(cmd, user=params.eagle_user)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 148, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 152, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 118, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 274, in action_run
> raise ex
> Fail: Execution of '/usr/hdp/current/eagle/bin/eagle-topology.sh --main 
> eagle.security.auditlog.HdfsAuditLogProcessorMain --topology 
> sandbox-hdfsAuditLog-topology --config 
> /usr/hdp/current/eagle/conf/sandbox-hdfsAuditLog-application.conf start' 
> returned 1. Starting eagle topology ...
> jarName=/usr/hdp/current/eagle/bin/../lib/topology/eagle-topology-0.3.0-assembly.jar
>  mainClass=eagle.security.auditlog.HdfsAuditLogProcessorMain 
> configFile=/usr/hdp/current/eagle/conf/sandbox-hdfsAuditLog-application.conf
> Running: java -client -Dstorm.options=nimbus.host=localhost 
> -Dstorm.home=/usr/hdp/2.2.4.2-2/storm -Dstorm.log.dir=/var/log/storm 
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib
>  -Dstorm.conf.file= -cp 
> /usr/hdp/2.2.4.2-2/storm/lib/jetty-http-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/hiccup-0.3.6.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-configuration-1.10.jar:/usr/hdp/2.2.4.2-2/storm/lib/minlog-1.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/json-simple-1.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-io-2.4.jar:/usr/hdp/2.2.4.2-2/storm/lib/ring-servlet-1.3.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/java.classpath-0.2.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-logging-1.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/clj-time-0.4.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/commons-fileupload-1.2.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/ring-core-1.1.5.jar:/usr/hdp/2.2.4.2-2/storm/lib/crypto-equality-1.0.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/core.incubator-0.1.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-servlets-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/ns-tracker-0.2.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/joda-time-2.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-security-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/ranger-storm-plugin-0.4.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/objenesis-1.2.jar:/usr/hdp/2.2.4.2-2/storm/lib/jetty-io-7.6.13.v20130916.jar:/usr/hdp/2.2.4.2-2/storm/lib/jersey-bundle-1.17.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/zookeeper.jar:/usr/hdp/2.2.4.2-2/storm/lib/javax.servlet-2.5.0.v201103041518.jar:/usr/hdp/2.2.4.2-2/storm/lib/tools.cli-0.2.4.jar:/usr/hdp/2.2.4.2-2/storm/lib/servlet-api-2.5.jar:/usr/hdp/2.2.4.2-2/storm/lib/hadoop-common-2.6.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/ranger-plugins-cred-0.4.0.2.2.4.2-2.jar:/usr/hdp/2.2.4.2-2/storm/lib/clout-1.0.1.jar:/usr/hdp/2.2.4.2-2/storm/lib/jgrapht-core-0.9.0.jar:/usr/hdp/2.2.4.2-2/storm/lib/logback-classic-1.0.6.jar:/usr/hdp/2.2.4.2-2/storm/lib/eclipselink-2.5.2-M1.jar:/usr/hdp/2.2

67 matches

Mail list logo