[GitHub] incubator-eagle pull request: EAGLE-195 policy metric display with...

2016-03-10 Thread zombieJ
GitHub user zombieJ opened a pull request: https://github.com/apache/incubator-eagle/pull/121 EAGLE-195 policy metric display with interval of 5 min or customized interval Provide daily & hourly & Every 5 minutes interval for policy metric display You can merge this pull request in

[jira] [Commented] (EAGLE-195) policy metric display with interval of 5 min or customized interval

2016-03-10 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190565#comment-15190565 ] ASF GitHub Bot commented on EAGLE-195: -- GitHub user zombieJ opened a pull request:

[jira] [Commented] (EAGLE-181) HDFS topology alerts multiple time.

2016-03-10 Thread Huizhi Lu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190559#comment-15190559 ] Huizhi Lu commented on EAGLE-181: - Not yet :) Two more weeks. > HDFS topology alerts mu

[DISCUSS] Adding new mailing list to contain JIRA and Github updates

2016-03-10 Thread Henry Saputra
Hi All, With Apache Eagle podling getting more active every day, it seemed like JIRA updates and Github mirror updates start to become clutter to the dev list. I think it is time to introduce new list, typically called issues@ as the reservoir for the updates. We will still need to make JIRA cre

[jira] [Updated] (EAGLE-197) figure out way to enable debug in storm cluster for Eagle topology

2016-03-10 Thread Hao Chen (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-197: --- Affects Version/s: v0.3.0 > figure out way to enable debug in storm cluster for Eagle topology > --

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

2016-03-10 Thread 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: --- Affects Version/s: v0.3.0 > integrate new Siddhi version so that thread should not die when event > evaluation

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

2016-03-10 Thread Hao Chen (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190503#comment-15190503 ] Hao Chen commented on EAGLE-198: Bad data will trigger this bug: https://github.com/wso2/si

[jira] [Commented] (EAGLE-190) JBDC Metadata Storage Extension

2016-03-10 Thread Hao Chen (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190485#comment-15190485 ] Hao Chen commented on EAGLE-190: No need to register additional complex jdbc type double[]

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

2016-03-10 Thread Edward Zhang (JIRA)
Edward Zhang created EAGLE-198: -- Summary: 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 Projec

MapR audit log , userid

2016-03-10 Thread Daniel Zhou
Hi guys, Now I'm able to generate "HDFSAuditLogObject" based on MAPR's hdfs audit log message, but met a problem of the "userID" part. Like I mentioned before, mapR's audit log message contains ids( eg: "2050.36.131336" is the file id of "/tmp/file.w" , "5098" is the id of user "daniel") but n

[jira] [Commented] (EAGLE-197) figure out way to enable debug in storm cluster for Eagle topology

2016-03-10 Thread Edward Zhang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189830#comment-15189830 ] Edward Zhang commented on EAGLE-197: Some logback configuration java -server -Xmx6g -X

[jira] [Created] (EAGLE-197) figure out way to enable debug in storm cluster for Eagle topology

2016-03-10 Thread Edward Zhang (JIRA)
Edward Zhang created EAGLE-197: -- Summary: figure out way to enable debug in storm cluster for Eagle topology Key: EAGLE-197 URL: https://issues.apache.org/jira/browse/EAGLE-197 Project: Eagle I

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

2016-03-10 Thread Edward Zhang (JIRA)
Edward Zhang created EAGLE-196: -- Summary: 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:

[jira] [Commented] (EAGLE-181) HDFS topology alerts multiple time.

2016-03-10 Thread Hao Chen (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189637#comment-15189637 ] Hao Chen commented on EAGLE-181: Can I start to assign tickets to you now? > HDFS topology

[jira] [Commented] (EAGLE-181) HDFS topology alerts multiple time.

2016-03-10 Thread Huizhi Lu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189627#comment-15189627 ] Huizhi Lu commented on EAGLE-181: - I am following it! Hey, Guys! > HDFS topology alerts mu

[jira] [Commented] (EAGLE-190) JBDC Metadata Storage Extension

2016-03-10 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188926#comment-15188926 ] ASF GitHub Bot commented on EAGLE-190: -- Github user haoch commented on the pull reques

[GitHub] incubator-eagle pull request: EAGLE-190 JBDC Metadata Storage Exte...

2016-03-10 Thread haoch
Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/118#issuecomment-194742526 Need to rename all "user" fields into "username" because "user" is invalid for Derby. --- If your project is set up for it, you can reply to this email and have