[jira] [Commented] (EAGLE-296) add unit test for eagle-storm-jobrunning-spout
[ https://issues.apache.org/jira/browse/EAGLE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297664#comment-15297664 ] Edward Zhang commented on EAGLE-296: Can you please close both jira and PR? > add unit test for eagle-storm-jobrunning-spout > -- > > Key: EAGLE-296 > URL: https://issues.apache.org/jira/browse/EAGLE-296 > Project: Eagle > Issue Type: Test >Reporter: tangjunjie >Priority: Minor > > Add unit test for eagle-storm-jobrunning-spout -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-296 Test unit for JobConfParse...
Github user yonzhang commented on the pull request: https://github.com/apache/incubator-eagle/pull/195#issuecomment-221164014 fixed and merged https://github.com/apache/incubator-eagle/commit/5578cfd912d70ebc0bb52a754f145996c6e5efd8. Please allow 2 weeks for merging into master --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (EAGLE-306) add metadata for showing "Topology" tab in left-nav by default
Michael Wu created EAGLE-306: Summary: add metadata for showing "Topology" tab in left-nav by default Key: EAGLE-306 URL: https://issues.apache.org/jira/browse/EAGLE-306 Project: Eagle Issue Type: Improvement Affects Versions: v0.3.0 Reporter: Michael Wu Assignee: Zhao, Qingwen Fix For: v0.4.0 When eagle-service is started up, on admin page, in the left-nav, there is no "Topology" tab showing up by default. Users have to add it as a new "Feature" to make it. Could you please add the metadata for default settings? Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-294) If a policy metadata field is not set, null attributes can not be able to add into input stream for SiddhiCEP
[ https://issues.apache.org/jira/browse/EAGLE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297471#comment-15297471 ] ASF GitHub Bot commented on EAGLE-294: -- Github user pkuwm closed the pull request at: https://github.com/apache/incubator-eagle/pull/177 > If a policy metadata field is not set, null attributes can not be able to add > into input stream for SiddhiCEP > -- > > Key: EAGLE-294 > URL: https://issues.apache.org/jira/browse/EAGLE-294 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 >Reporter: Huizhi Lu >Assignee: Huizhi Lu >Priority: Critical > Fix For: v0.3.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > If a policy metadata field is not set, null attributes can not be able to add > into input stream for SiddhiCEP. Alerts may not be able to detect. > So we need to put null attributes into input stream. > In the sourcecode, we should get metadata map for the stream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-294) If a policy metadata field is not set, null attributes can not be able to add into input stream for SiddhiCEP
[ https://issues.apache.org/jira/browse/EAGLE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297472#comment-15297472 ] ASF GitHub Bot commented on EAGLE-294: -- Github user pkuwm commented on the pull request: https://github.com/apache/incubator-eagle/pull/177#issuecomment-221140141 PULL REQUEST #196 > If a policy metadata field is not set, null attributes can not be able to add > into input stream for SiddhiCEP > -- > > Key: EAGLE-294 > URL: https://issues.apache.org/jira/browse/EAGLE-294 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 >Reporter: Huizhi Lu >Assignee: Huizhi Lu >Priority: Critical > Fix For: v0.3.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > If a policy metadata field is not set, null attributes can not be able to add > into input stream for SiddhiCEP. Alerts may not be able to detect. > So we need to put null attributes into input stream. > In the sourcecode, we should get metadata map for the stream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-294. If a policy metadata fiel...
Github user pkuwm commented on the pull request: https://github.com/apache/incubator-eagle/pull/177#issuecomment-221140141 PULL REQUEST #196 --- 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-294. If a policy metadata fiel...
Github user pkuwm closed the pull request at: https://github.com/apache/incubator-eagle/pull/177 --- 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-294) If a policy metadata field is not set, null attributes can not be able to add into input stream for SiddhiCEP
[ https://issues.apache.org/jira/browse/EAGLE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297467#comment-15297467 ] ASF GitHub Bot commented on EAGLE-294: -- GitHub user pkuwm reopened a pull request: https://github.com/apache/incubator-eagle/pull/196 EAGLE-294. If a policy metadata field is not set, add null attributes to input stream for SiddhiCEP. For dev branch. EAGLE-294. If a policy metadata field is not set, add null attributes to input stream for SiddhiCEP. You can merge this pull request into a Git repository by running: $ git pull https://github.com/pkuwm/incubator-eagle EAGLE-294-DEV Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/196.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 #196 commit 0de67fc95edf3be62941634e038ba8ad20346a79 Author: LuDate: 2016-05-06T00:45:47Z EAGLE-294. If a policy metadata field is not set, add null attributes into input stream for SiddhiCEP. > If a policy metadata field is not set, null attributes can not be able to add > into input stream for SiddhiCEP > -- > > Key: EAGLE-294 > URL: https://issues.apache.org/jira/browse/EAGLE-294 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 >Reporter: Huizhi Lu >Assignee: Huizhi Lu >Priority: Critical > Fix For: v0.3.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > If a policy metadata field is not set, null attributes can not be able to add > into input stream for SiddhiCEP. Alerts may not be able to detect. > So we need to put null attributes into input stream. > In the sourcecode, we should get metadata map for the stream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-294. If a policy metadata fiel...
GitHub user pkuwm reopened a pull request: https://github.com/apache/incubator-eagle/pull/196 EAGLE-294. If a policy metadata field is not set, add null attributes to input stream for SiddhiCEP. For dev branch. EAGLE-294. If a policy metadata field is not set, add null attributes to input stream for SiddhiCEP. You can merge this pull request into a Git repository by running: $ git pull https://github.com/pkuwm/incubator-eagle EAGLE-294-DEV Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/196.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 #196 commit 0de67fc95edf3be62941634e038ba8ad20346a79 Author: LuDate: 2016-05-06T00:45:47Z EAGLE-294. If a policy metadata field is not set, add null attributes into input stream for SiddhiCEP. --- 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] [Closed] (EAGLE-236) Change project version to "0.4.0-SNAPSHOT" since "v0.3.0" has been released.
[ https://issues.apache.org/jira/browse/EAGLE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-236. --- Resolution: Fixed Merged. > Change project version to "0.4.0-SNAPSHOT" since "v0.3.0" has been released. > > > Key: EAGLE-236 > URL: https://issues.apache.org/jira/browse/EAGLE-236 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.3.0 >Reporter: Hao Chen >Assignee: Huizhi Lu > Fix For: v0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-297) Email with authentication can not be validated and sent out.
[ https://issues.apache.org/jira/browse/EAGLE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-297. --- Resolution: Fixed Merged. > Email with authentication can not be validated and sent out. > > > Key: EAGLE-297 > URL: https://issues.apache.org/jira/browse/EAGLE-297 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 >Reporter: Huizhi Lu >Assignee: Huizhi Lu > Original Estimate: 48h > Remaining Estimate: 48h > > Email authentication information is not passed into EagleMailClient from > AlertEmailSender. So authentication can not be validated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-294. If a policy metadata fiel...
Github user pkuwm closed the pull request at: https://github.com/apache/incubator-eagle/pull/196 --- 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-291) JDBC: Update transactions fail in PostgreSQL
[ https://issues.apache.org/jira/browse/EAGLE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297440#comment-15297440 ] ASF GitHub Bot commented on EAGLE-291: -- Github user Jashchahal closed the pull request at: https://github.com/apache/incubator-eagle/pull/193 > JDBC: Update transactions fail in PostgreSQL > > > Key: EAGLE-291 > URL: https://issues.apache.org/jira/browse/EAGLE-291 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 > Environment: Linux, PostgreSQL 9.1 as metadata store. >Reporter: Jaspaul Chahal > Fix For: v0.4.0 > > > When it tries to update some entity, throws the following exception: > org.apache.torque.TorqueException: org.postgresql.util.PSQLException: ERROR: > current transaction is aborted, commands ignored until end of transaction > block. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-291) JDBC: Update transactions fail in PostgreSQL
[ https://issues.apache.org/jira/browse/EAGLE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297439#comment-15297439 ] ASF GitHub Bot commented on EAGLE-291: -- Github user Jashchahal commented on the pull request: https://github.com/apache/incubator-eagle/pull/193#issuecomment-221135969 Closing PR > JDBC: Update transactions fail in PostgreSQL > > > Key: EAGLE-291 > URL: https://issues.apache.org/jira/browse/EAGLE-291 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 > Environment: Linux, PostgreSQL 9.1 as metadata store. >Reporter: Jaspaul Chahal > Fix For: v0.4.0 > > > When it tries to update some entity, throws the following exception: > org.apache.torque.TorqueException: org.postgresql.util.PSQLException: ERROR: > current transaction is aborted, commands ignored until end of transaction > block. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-291) JDBC: Update transactions fail in PostgreSQL
[ https://issues.apache.org/jira/browse/EAGLE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297438#comment-15297438 ] ASF GitHub Bot commented on EAGLE-291: -- Github user Jashchahal closed the pull request at: https://github.com/apache/incubator-eagle/pull/194 > JDBC: Update transactions fail in PostgreSQL > > > Key: EAGLE-291 > URL: https://issues.apache.org/jira/browse/EAGLE-291 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 > Environment: Linux, PostgreSQL 9.1 as metadata store. >Reporter: Jaspaul Chahal > Fix For: v0.4.0 > > > When it tries to update some entity, throws the following exception: > org.apache.torque.TorqueException: org.postgresql.util.PSQLException: ERROR: > current transaction is aborted, commands ignored until end of transaction > block. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-291) JDBC: Update transactions fail in PostgreSQL
[ https://issues.apache.org/jira/browse/EAGLE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297437#comment-15297437 ] ASF GitHub Bot commented on EAGLE-291: -- Github user Jashchahal commented on the pull request: https://github.com/apache/incubator-eagle/pull/194#issuecomment-221135862 Closing PR > JDBC: Update transactions fail in PostgreSQL > > > Key: EAGLE-291 > URL: https://issues.apache.org/jira/browse/EAGLE-291 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 > Environment: Linux, PostgreSQL 9.1 as metadata store. >Reporter: Jaspaul Chahal > Fix For: v0.4.0 > > > When it tries to update some entity, throws the following exception: > org.apache.torque.TorqueException: org.postgresql.util.PSQLException: ERROR: > current transaction is aborted, commands ignored until end of transaction > block. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-291 : JDBC: Update transaction...
Github user Jashchahal commented on the pull request: https://github.com/apache/incubator-eagle/pull/194#issuecomment-221135862 Closing PR --- 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-291 : JDBC: Update transaction...
Github user Jashchahal closed the pull request at: https://github.com/apache/incubator-eagle/pull/194 --- 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: add developer page
Github user yonzhang commented on the pull request: https://github.com/apache/incubator-eagle/pull/137#issuecomment-221134520 Need more thinking on document --- 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-294. If a policy metadata fiel...
Github user pkuwm closed the pull request at: https://github.com/apache/incubator-eagle/pull/178 --- 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-300 set debug-log dumping comp...
Github user yonzhang commented on the pull request: https://github.com/apache/incubator-eagle/pull/192#issuecomment-221131417 merged --- 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-296 Test unit for JobConfParse...
Github user yonzhang commented on the pull request: https://github.com/apache/incubator-eagle/pull/195#issuecomment-221126481 This looks good! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
RE: Eagle credentials
Thanks Huizhi, I will try this out and will get back to you, if have more questions. Regards, Jaspaul -Original Message- From: Huizhi Lu [mailto:ihuizhi...@gmail.com] Sent: Monday, May 23, 2016 2:16 PM To: dev@eagle.incubator.apache.org Cc: Subra RameshSubject: Re: Eagle credentials Hi Jaspaul, We support 2 types of credential verification: 1) We use javax.xml.bind.DatatypeConverter Base64 to encode encrypted authentication. This is used for testing/sandbox. And please note that authority is also used -- ROLE_USER, ROLE_ADMIN. The information is in the following file. We can set it up in the following file. It means you can change the username/password in the following configuration. You need to use Base64 to encode your password and replace the following password's value. eagle/lib/tomcat/webapps/eagle-service/WEB-INF/classes/eagleSecurity.xml Please note that this is NOT recommended. It might be hacked and password may be leaked. 2) LDAP is supported and recommended. We can enable LDAP this way: a) Edit conf/eagle-service.conf. change springActiveProfile="default" b) Edit conf/ldap.properties If you still have any questions, please feel free to contact us. Thanks. -Huizhi > On May 23, 2016, at 11:06 AM, Jaspaul Chahal wrote: > > Hello, > > This is related to Apache Eagle credentials, we know that the default > credentials are admin/secret. > But, I want to change the credentials to something else. Only place, I know, > where we specify the credentials are in "~ /eagle/bin/eagle-env.sh" file . > Even if I change the EAGLE_SERVICE_USER and EAGLE_SERVICE_PASSWD and restart > Apache Eagle service, it doesn't reflect the change. > > Can you please guide me, how can I change the credentials for Apache Eagle > service? > > > Thanks and regards, > Jaspaul Chahal
[jira] [Created] (EAGLE-304) Enable Advanced dedup configuration in policy definition
Zhao, Qingwen created EAGLE-304: --- Summary: Enable Advanced dedup configuration in policy definition Key: EAGLE-304 URL: https://issues.apache.org/jira/browse/EAGLE-304 Project: Eagle Issue Type: Bug Affects Versions: v0.3.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Priority: Critical Fix For: v0.4.0 1. This advanced de-dup configuration at UI is just a empty shell. 2. Eagle alert entity de-dup function currently only ignores these entities with same tags. -- This message was sent by Atlassian JIRA (v6.3.4#6332)