[jira] [Commented] (EAGLE-902) Add JDBC data storage dependency into eagle server module
[ https://issues.apache.org/jira/browse/EAGLE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877724#comment-15877724 ] ASF GitHub Bot commented on EAGLE-902: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/834 > Add JDBC data storage dependency into eagle server module > -- > > Key: EAGLE-902 > URL: https://issues.apache.org/jira/browse/EAGLE-902 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: DanielZhou > > add the dependency into eagle server module -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (EAGLE-902) Add JDBC data storage dependency into eagle server module
[ https://issues.apache.org/jira/browse/EAGLE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on EAGLE-902 started by Hao Chen. -- > Add JDBC data storage dependency into eagle server module > -- > > Key: EAGLE-902 > URL: https://issues.apache.org/jira/browse/EAGLE-902 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Hao Chen > > add the dependency into eagle server module -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #834: EAGLE-902 Add JDBC data storage dependency into eag...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/834 --- 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] eagle issue #834: EAGLE-902 Add JDBC data storage dependency into eagle serv...
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/834 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-881) Url of scala-tools repository is no longer valid
[ https://issues.apache.org/jira/browse/EAGLE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877720#comment-15877720 ] ASF GitHub Bot commented on EAGLE-881: -- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/795 @DadanielZ is this PR still valid? > Url of scala-tools repository is no longer valid > > > Key: EAGLE-881 > URL: https://issues.apache.org/jira/browse/EAGLE-881 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: DanielZhou > > After clear ~/.m2/repository, Maven build failed with error messages: > Failed to execute goal > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) > on project eagle-security-hive: Error resolving project artifact: Could not > transfer artifact org.pentaho:pentaho-aggdesigner-algorithm:pom:5.1.5-jhyde > from/to scala-tools.org (http://scala-tools.org/repo-releases): Received > fatal alert: protocol_version for project > org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde -> [Help 1] > Reason: > The URL of scala-tools repository provided in "eagle-parent" pom file is no > longer valid: http://scala-tools.org/repo-releases > It will redirects to some unknown blog and won't find related resources. > Solution: > Remove the repositories declaration of "Scala-Tools Maven2 Repository" from > "eagle-parent" pom file, so that maven can download them from default maven > repo. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #795: [EAGLE-881] Url of scala-tools repository is no longer val...
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/795 @DadanielZ is this PR still valid? --- 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-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[ https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877718#comment-15877718 ] ASF GitHub Bot commented on EAGLE-888: -- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/796 @DadanielZ is this PR still valid? > Application submitted to Storm is always shown as “HBaseAuditLogApp” > - > > Key: EAGLE-888 > URL: https://issues.apache.org/jira/browse/EAGLE-888 > Project: Eagle > Issue Type: Bug > Components: Core::App Engine >Affects Versions: v0.5.0 >Reporter: DanielZhou >Assignee: DanielZhou > > *Issue*: > Steps to reproduce: > - Started application from Eagle UI (eg: alert engine) > - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"* > *Reason*: > In the constructor function of class *"ApplicationAction"*: > {quote} > this.effectiveConfig = ConfigFactory.parseMap(executionConfig) > .withFallback(serverConfig) > > .withFallback(ConfigFactory.parseMap(metadata.getContext())) > {quote} > According to the java doc of > [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-] > : > {quote} > Returns a new value computed by merging this value with another, with keys in > this value "winning" over the other one. > {quote} > As a result, "serverConfig" will win over > "ConfigFactory.parseMap(metadata.getContext())" which means the default > "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")" > will win over the meta data of the user's topology. > *Fix*: > Change the order of "withFallBack" to: > {quote} > this.effectiveConfig = ConfigFactory.parseMap(executionConfig) > > .withFallback(ConfigFactory.parseMap(metadata.getContext())) > .withFallback(serverConfig) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-916) UI alert detail pass timerange
[ https://issues.apache.org/jira/browse/EAGLE-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877717#comment-15877717 ] ASF GitHub Bot commented on EAGLE-916: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/824 > UI alert detail pass timerange > -- > > Key: EAGLE-916 > URL: https://issues.apache.org/jira/browse/EAGLE-916 > Project: Eagle > Issue Type: Improvement >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > UI alert detail pass timerange -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #824: EAGLE-916 alert support time stamp
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/824 --- 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-921) Integrate role-based Authentication in API and UI
Hao Chen created EAGLE-921: -- Summary: Integrate role-based Authentication in API and UI Key: EAGLE-921 URL: https://issues.apache.org/jira/browse/EAGLE-921 Project: Eagle Issue Type: New Feature Components: Core::Eagle Server Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Integrate role-based Authentication in API and UI -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-918) Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
[ https://issues.apache.org/jira/browse/EAGLE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877677#comment-15877677 ] ASF GitHub Bot commented on EAGLE-918: -- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/831 @r7raul1984 I have finished this PR, please help continue to review. If no more problem, I will merge it after approved. > Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth > > > Key: EAGLE-918 > URL: https://issues.apache.org/jira/browse/EAGLE-918 > Project: Eagle > Issue Type: New Feature > Components: Core::Eagle Server >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > * Improve eagle auth framework to support annotations under Jersey 1.9 and > Dropwizard 0.7.1 > {code} > @PermitAll > @DenyAll > @RolesAllowed > @Auth > {code} > * Add Authentication API > {code} > GET /auth/principal > GET /auth/validate > GET /auth/login > {code} > * Add password encryption and EncrytTool > {code} > java ServerMain encrypt [text to encrypt] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #831: [EAGLE-918] Improve eagle auth to support @PermitAll/DenyA...
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/831 @r7raul1984 I have finished this PR, please help continue to review. If no more problem, I will merge it after approved. --- 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] eagle pull request #831: [EAGLE-918] Improve eagle auth to support @PermitAl...
Github user haoch commented on a diff in the pull request: https://github.com/apache/eagle/pull/831#discussion_r102397848 --- Diff: eagle-server/src/main/java/org/apache/eagle/server/authentication/config/UserAccount.java --- @@ -0,0 +1,61 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +package org.apache.eagle.server.authentication.config; + +import org.apache.eagle.common.authentication.UserPrincipal; + +import java.util.List; + +public class UserAccount { +private String username; +private String password; +private List roles; + +public UserAccount(String username, String password) { +this.username = username; +this.password = password; +} + +public String getUsername() { +return username; +} + +public void setUsername(String username) { +this.username = username; +} + +public String getPassword() { +return password; +} + +public void setPassword(String password) { +this.password = password; --- End diff -- Resolved with password encryption. --- 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] eagle issue #812: [EAGLE-906] org.apache.storm 1.x with API changes
Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/812 i havent explicitly tested it, but from their [docs](http://storm.apache.org/releases/1.0.2/storm-kafka.html), it looks compatible with kafka 0.8.1.1 which is used in the example given on that page. --- 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] eagle pull request #825: [EAGLE-900] Only show left navigation item (HDFS, H...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/825 --- 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-918) Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
[ https://issues.apache.org/jira/browse/EAGLE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877495#comment-15877495 ] ASF GitHub Bot commented on EAGLE-918: -- Github user haoch commented on a diff in the pull request: https://github.com/apache/eagle/pull/831#discussion_r102385723 --- Diff: eagle-server/src/main/java/org/apache/eagle/server/authentication/config/UserAccount.java --- @@ -0,0 +1,61 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +package org.apache.eagle.server.authentication.config; + +import org.apache.eagle.common.authentication.UserPrincipal; + +import java.util.List; + +public class UserAccount { +private String username; +private String password; +private List roles; + +public UserAccount(String username, String password) { +this.username = username; +this.password = password; +} + +public String getUsername() { +return username; +} + +public void setUsername(String username) { +this.username = username; +} + +public String getPassword() { +return password; +} + +public void setPassword(String password) { +this.password = password; --- End diff -- Good point. > Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth > > > Key: EAGLE-918 > URL: https://issues.apache.org/jira/browse/EAGLE-918 > Project: Eagle > Issue Type: New Feature > Components: Core::Eagle Server >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > * Improve eagle auth framework to support annotations under Jersey 1.9 and > Dropwizard 0.7.1 > {code} > @PermitAll > @DenyAll > @RolesAllowed > @Auth > {code} > * Add Authentication API > {code} > GET /auth/principal > GET /auth/validate > GET /auth/login > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-902) Add JDBC data storage dependency into eagle server module
[ https://issues.apache.org/jira/browse/EAGLE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877478#comment-15877478 ] ASF GitHub Bot commented on EAGLE-902: -- Github user DadanielZ closed the pull request at: https://github.com/apache/eagle/pull/815 > Add JDBC data storage dependency into eagle server module > -- > > Key: EAGLE-902 > URL: https://issues.apache.org/jira/browse/EAGLE-902 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: DanielZhou > > add the dependency into eagle server module -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #815: EAGLE-902 Add JDBC data storage dependency into eagle serv...
Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/815 Closing this pr, will open a new one --- 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-902) Add JDBC data storage dependency into eagle server module
[ https://issues.apache.org/jira/browse/EAGLE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877477#comment-15877477 ] ASF GitHub Bot commented on EAGLE-902: -- Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/815 Closing this pr, will open a new one > Add JDBC data storage dependency into eagle server module > -- > > Key: EAGLE-902 > URL: https://issues.apache.org/jira/browse/EAGLE-902 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: DanielZhou > > add the dependency into eagle server module -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-919) Fix mr history null pointer exception when counters are null
[ https://issues.apache.org/jira/browse/EAGLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877394#comment-15877394 ] ASF GitHub Bot commented on EAGLE-919: -- GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/833 EAGLE-919: Fix null pointer exception in JobSuggestionListener https://issues.apache.org/jira/browse/EAGLE-919 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-919 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/833.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 #833 commit 32dfd910269bc2d3c907472d056963cf4f3ef033 Author: Zhao, QingwenDate: 2017-02-22T03:23:34Z fix null pointer exception commit 2eaf5a6c99a6bcdda702760c8da533f88b756403 Author: Zhao, Qingwen Date: 2017-02-22T03:27:18Z enable jobSuggestion listener > Fix mr history null pointer exception when counters are null > > > Key: EAGLE-919 > URL: https://issues.apache.org/jira/browse/EAGLE-919 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > Fix null pointer exception in mr history job parser when counters are null -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #833: EAGLE-919: Fix null pointer exception in JobSuggest...
GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/833 EAGLE-919: Fix null pointer exception in JobSuggestionListener https://issues.apache.org/jira/browse/EAGLE-919 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-919 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/833.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 #833 commit 32dfd910269bc2d3c907472d056963cf4f3ef033 Author: Zhao, QingwenDate: 2017-02-22T03:23:34Z fix null pointer exception commit 2eaf5a6c99a6bcdda702760c8da533f88b756403 Author: Zhao, Qingwen Date: 2017-02-22T03:27:18Z enable jobSuggestion listener --- 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-144) Support activity monitoring for Knox
[ https://issues.apache.org/jira/browse/EAGLE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877389#comment-15877389 ] Jayesh commented on EAGLE-144: -- [~senthilec566], are you actively working on this? we use knox in production and looking to build this app. Please let me know, if you want to collaborate. Thanks > Support activity monitoring for Knox > > > Key: EAGLE-144 > URL: https://issues.apache.org/jira/browse/EAGLE-144 > Project: Eagle > Issue Type: New Feature >Reporter: Senthilkumar >Assignee: Senthilkumar > > The Knox Gateway provides a single access point for all REST interactions > with Hadoop clusters. It will be valuable to monitor the access events > happening in knox gateway and see if there is an anomaly and generate an > alert. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-919) Fix mr history null pointer exception when counters are null
Zhao, Qingwen created EAGLE-919: --- Summary: Fix mr history null pointer exception when counters are null Key: EAGLE-919 URL: https://issues.apache.org/jira/browse/EAGLE-919 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix null pointer exception in mr history job parser when counters are null -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #832: [MINOR] fix job error mapping flush bug
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/832 --- 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] eagle pull request #832: [MINOR] fix job error mapping flush bug
GitHub user wujinhu opened a pull request: https://github.com/apache/eagle/pull/832 [MINOR] fix job error mapping flush bug You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/eagle EAGLE-845 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/832.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 #832 --- 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-918) Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
[ https://issues.apache.org/jira/browse/EAGLE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877065#comment-15877065 ] ASF GitHub Bot commented on EAGLE-918: -- Github user r7raul1984 commented on a diff in the pull request: https://github.com/apache/eagle/pull/831#discussion_r102352634 --- Diff: eagle-server/src/main/java/org/apache/eagle/server/authentication/config/UserAccount.java --- @@ -0,0 +1,61 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +package org.apache.eagle.server.authentication.config; + +import org.apache.eagle.common.authentication.UserPrincipal; + +import java.util.List; + +public class UserAccount { +private String username; +private String password; +private List roles; + +public UserAccount(String username, String password) { +this.username = username; +this.password = password; +} + +public String getUsername() { +return username; +} + +public void setUsername(String username) { +this.username = username; +} + +public String getPassword() { +return password; +} + +public void setPassword(String password) { +this.password = password; --- End diff -- In order to make it more safe,I think that we should encrypt the password . > Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth > > > Key: EAGLE-918 > URL: https://issues.apache.org/jira/browse/EAGLE-918 > Project: Eagle > Issue Type: New Feature > Components: Core::Eagle Server >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > * Improve eagle auth framework to support annotations under Jersey 1.9 and > Dropwizard 0.7.1 > {code} > @PermitAll > @DenyAll > @RolesAllowed > @Auth > {code} > * Add Authentication API > {code} > GET /auth/principal > GET /auth/validate > GET /auth/login > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #831: [EAGLE-918] Improve eagle auth to support @PermitAl...
Github user r7raul1984 commented on a diff in the pull request: https://github.com/apache/eagle/pull/831#discussion_r102352634 --- Diff: eagle-server/src/main/java/org/apache/eagle/server/authentication/config/UserAccount.java --- @@ -0,0 +1,61 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +package org.apache.eagle.server.authentication.config; + +import org.apache.eagle.common.authentication.UserPrincipal; + +import java.util.List; + +public class UserAccount { +private String username; +private String password; +private List roles; + +public UserAccount(String username, String password) { +this.username = username; +this.password = password; +} + +public String getUsername() { +return username; +} + +public void setUsername(String username) { +this.username = username; +} + +public String getPassword() { +return password; +} + +public void setPassword(String password) { +this.password = password; --- End diff -- In order to make it more safeï¼I think that we should encrypt the password . --- 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-911) Have mongo metadata dbname configurable
[ https://issues.apache.org/jira/browse/EAGLE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877038#comment-15877038 ] ASF GitHub Bot commented on EAGLE-911: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/819 > Have mongo metadata dbname configurable > --- > > Key: EAGLE-911 > URL: https://issues.apache.org/jira/browse/EAGLE-911 > Project: Eagle > Issue Type: Improvement > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.6.0 > > > MongoMetadataDao doesnt respect the configuration of db name. This make > multiple alert-service no table to reuse a mongo instance which is > specifically useful in prod testing case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-870) NoClassDefFoundError while running storm topology for alert and MRrunning
[ https://issues.apache.org/jira/browse/EAGLE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876261#comment-15876261 ] ASF GitHub Bot commented on EAGLE-870: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/811 > NoClassDefFoundError while running storm topology for alert and MRrunning > - > > Key: EAGLE-870 > URL: https://issues.apache.org/jira/browse/EAGLE-870 > Project: Eagle > Issue Type: Bug >Reporter: Jayesh >Assignee: Jayesh >Priority: Critical > > alert module is throwing this error in storm topology about not finding the > class > {code} > java.lang.NoClassDefFoundError: com/sun/jersey/api/client/GenericType at > org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.init(ZKMetadataChangeNotifyService.java:70) > {code} > GenericType class here mentioned is part of jetty-client from > com.sun.jersey.jetty which is not included in > eagle-topology-0.5.0-SNAPSHOT-assembly.jar > due to this error, alert topology wont be able to execute. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #811: [EAGLE-870] adding required packages into storm-jar
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/811 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] eagle issue #812: [EAGLE-906] org.apache.storm 1.x with API changes
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/812 Have you tested about consuming `kafka:0.8.1` with `storm-kafka:1.0.2` ? --- 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-900) Only show left navigation item (HDFS, HBase) when we install the JMX application
[ https://issues.apache.org/jira/browse/EAGLE-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876252#comment-15876252 ] ASF GitHub Bot commented on EAGLE-900: -- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/825 LGTM > Only show left navigation item (HDFS, HBase) when we install the JMX > application > > > Key: EAGLE-900 > URL: https://issues.apache.org/jira/browse/EAGLE-900 > Project: Eagle > Issue Type: Improvement > Components: App::Hadoop JMX Monitor >Reporter: jianzhong.chen >Assignee: JiJun Tang > > Currently, we can see the HBase navigation item even if my cluster has not > installed the HBase JMX application. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #825: [EAGLE-900] Only show left navigation item (HDFS, HBase) w...
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/825 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] eagle issue #831: [EAGLE-918] Improve eagle auth to support @PermitAll/DenyA...
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/831 @zombieJ please move on to refactor eagle login page after this PR 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. ---
[jira] [Work started] (EAGLE-918) Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
[ https://issues.apache.org/jira/browse/EAGLE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on EAGLE-918 started by Hao Chen. -- > Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth > > > Key: EAGLE-918 > URL: https://issues.apache.org/jira/browse/EAGLE-918 > Project: Eagle > Issue Type: New Feature > Components: Core::Eagle Server >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > * Improve eagle auth framework to support annotations under Jersey 1.9 and > Dropwizard 0.7.1 > {code} > @PermitAll > @DenyAll > @RolesAllowed > @Auth > {code} > * Add Authentication API > {code} > GET /auth/principal > GET /auth/validate > GET /auth/login > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-918) Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
[ https://issues.apache.org/jira/browse/EAGLE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876193#comment-15876193 ] ASF GitHub Bot commented on EAGLE-918: -- GitHub user haoch opened a pull request: https://github.com/apache/eagle/pull/831 [EAGLE-918] Improve eagle auth to support @PermitAll/DenyAll/RolesAllowed/Auth and API * Improve eagle auth framework to support annotations under Jersey 1.9 and Dropwizard 0.7.1 ~~~ @PermitAll @DenyAll @RolesAllowed @Auth ~~~ * Add Authentication API ~~~ GET /auth/principal GET /auth/validate GET /auth/login ~~~ You can merge this pull request into a Git repository by running: $ git pull https://github.com/haoch/eagle EnableAuthAPI Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/831.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 #831 commit 5dc42d1ce5d9be74cfa0683bbef57ddcc3e8f1bb Author: Hao ChenDate: 2017-02-20T11:27:38Z Add User.Role commit 753d4bf87f52056ffc1717498bf829bb52517671 Author: Hao Chen Date: 2017-02-21T09:49:01Z Support @RolesAllowed @DenyAll @PermitAll security annoations commit 3e16a20199d9c6af670d30b00dd065835e76a542 Author: Hao Chen Date: 2017-02-21T11:41:54Z Remove VISITOR role commit 30c06cbc8381366e3c1847091f7ad52944b7a705 Author: Hao Chen Date: 2017-02-21T11:42:23Z Clean useless code commit 844a05180deaff666472d74e50ba4cdd2269ebf0 Author: Hao Chen Date: 2017-02-21T15:50:15Z Improve Unit test coverage commit 78d39c58e0956cbebb7e7f20d4469a7c2bd9eb78 Author: Hao Chen Date: 2017-02-21T15:53:13Z Rename package authentication to security > Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth > > > Key: EAGLE-918 > URL: https://issues.apache.org/jira/browse/EAGLE-918 > Project: Eagle > Issue Type: New Feature > Components: Core::Eagle Server >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Improve eagle auth framework to support annotations under Jersey 1.9 and > Dropwizard 0.7.1 > @PermitAll > @DenyAll > @RolesAllowed > @Auth -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #831: [EAGLE-918] Improve eagle auth to support @PermitAl...
GitHub user haoch opened a pull request: https://github.com/apache/eagle/pull/831 [EAGLE-918] Improve eagle auth to support @PermitAll/DenyAll/RolesAllowed/Auth and API * Improve eagle auth framework to support annotations under Jersey 1.9 and Dropwizard 0.7.1 ~~~ @PermitAll @DenyAll @RolesAllowed @Auth ~~~ * Add Authentication API ~~~ GET /auth/principal GET /auth/validate GET /auth/login ~~~ You can merge this pull request into a Git repository by running: $ git pull https://github.com/haoch/eagle EnableAuthAPI Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/831.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 #831 commit 5dc42d1ce5d9be74cfa0683bbef57ddcc3e8f1bb Author: Hao ChenDate: 2017-02-20T11:27:38Z Add User.Role commit 753d4bf87f52056ffc1717498bf829bb52517671 Author: Hao Chen Date: 2017-02-21T09:49:01Z Support @RolesAllowed @DenyAll @PermitAll security annoations commit 3e16a20199d9c6af670d30b00dd065835e76a542 Author: Hao Chen Date: 2017-02-21T11:41:54Z Remove VISITOR role commit 30c06cbc8381366e3c1847091f7ad52944b7a705 Author: Hao Chen Date: 2017-02-21T11:42:23Z Clean useless code commit 844a05180deaff666472d74e50ba4cdd2269ebf0 Author: Hao Chen Date: 2017-02-21T15:50:15Z Improve Unit test coverage commit 78d39c58e0956cbebb7e7f20d4469a7c2bd9eb78 Author: Hao Chen Date: 2017-02-21T15:53:13Z Rename package authentication to security --- 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-918) Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
Hao Chen created EAGLE-918: -- Summary: Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth Key: EAGLE-918 URL: https://issues.apache.org/jira/browse/EAGLE-918 Project: Eagle Issue Type: New Feature Components: Core::Eagle Server Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Improve eagle auth framework to support annotations under Jersey 1.9 and Dropwizard 0.7.1 @PermitAll @DenyAll @RolesAllowed @Auth -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #830: [MINOR] fix mr history null pointer bug
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/830 --- 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] eagle pull request #829: [MINOR] add Job error category and error message ma...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/829 --- 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-917) add Job error category and error message mapping
[ https://issues.apache.org/jira/browse/EAGLE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875627#comment-15875627 ] ASF GitHub Bot commented on EAGLE-917: -- GitHub user wujinhu opened a pull request: https://github.com/apache/eagle/pull/828 [EAGLE-917] add Job error category and error message mapping You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/eagle EAGLE-917 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/828.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 #828 commit 84ef5b70ea3b5de307738c546f433ad8793ba5b4 Author: wujinhuDate: 2017-02-21T06:51:14Z add Job error category and error message mapping commit f9afafe7810d49e5338a9f8de76315c801f6fe24 Author: wujinhu Date: 2017-02-21T07:08:40Z add Job error category and error message mapping commit fbee685dc1394629f71a4bc785864a7d5b127332 Author: wujinhu Date: 2017-02-21T07:34:09Z add Job error category and error message mapping commit e68842c24c10e93229e64af918296e4825b420bd Author: wujinhu Date: 2017-02-21T08:57:07Z add Job error category and error message mapping > add Job error category and error message mapping > > > Key: EAGLE-917 > URL: https://issues.apache.org/jira/browse/EAGLE-917 > Project: Eagle > Issue Type: Improvement >Reporter: wujinhu >Assignee: wujinhu > > In order to query error category and error message quickly, we need to add > this mapping to eagle storage although task attempt already has this > information -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-917) add Job error category and error message mapping
[ https://issues.apache.org/jira/browse/EAGLE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875628#comment-15875628 ] ASF GitHub Bot commented on EAGLE-917: -- Github user wujinhu closed the pull request at: https://github.com/apache/eagle/pull/828 > add Job error category and error message mapping > > > Key: EAGLE-917 > URL: https://issues.apache.org/jira/browse/EAGLE-917 > Project: Eagle > Issue Type: Improvement >Reporter: wujinhu >Assignee: wujinhu > > In order to query error category and error message quickly, we need to add > this mapping to eagle storage although task attempt already has this > information -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #828: [EAGLE-917] add Job error category and error messag...
Github user wujinhu closed the pull request at: https://github.com/apache/eagle/pull/828 --- 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] eagle pull request #828: [EAGLE-917] add Job error category and error messag...
GitHub user wujinhu opened a pull request: https://github.com/apache/eagle/pull/828 [EAGLE-917] add Job error category and error message mapping You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/eagle EAGLE-917 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/828.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 #828 commit 84ef5b70ea3b5de307738c546f433ad8793ba5b4 Author: wujinhuDate: 2017-02-21T06:51:14Z add Job error category and error message mapping commit f9afafe7810d49e5338a9f8de76315c801f6fe24 Author: wujinhu Date: 2017-02-21T07:08:40Z add Job error category and error message mapping commit fbee685dc1394629f71a4bc785864a7d5b127332 Author: wujinhu Date: 2017-02-21T07:34:09Z add Job error category and error message mapping commit e68842c24c10e93229e64af918296e4825b420bd Author: wujinhu Date: 2017-02-21T08:57:07Z add Job error category and error message mapping --- 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-908) Hdfs JMX Monitoring Dashboard
[ https://issues.apache.org/jira/browse/EAGLE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875562#comment-15875562 ] ASF GitHub Bot commented on EAGLE-908: -- Github user chitin closed the pull request at: https://github.com/apache/eagle/pull/813 > Hdfs JMX Monitoring Dashboard > - > > Key: EAGLE-908 > URL: https://issues.apache.org/jira/browse/EAGLE-908 > Project: Eagle > Issue Type: New Feature > Components: App::Hadoop JMX Monitor, Core::UI Engine >Reporter: Lingang Deng >Assignee: JiJun Tang > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #813: [EAGLE-908] Hdfs JMX Monitoring Dashboard
Github user chitin commented on the issue: https://github.com/apache/eagle/pull/813 Close the pr, contribute to the jira base on [825](https://github.com/apache/eagle/pull/825) --- 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] eagle pull request #813: [EAGLE-908] Hdfs JMX Monitoring Dashboard
Github user chitin closed the pull request at: https://github.com/apache/eagle/pull/813 --- 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-840) Task Failing Nodes List and bad node detection
[ https://issues.apache.org/jira/browse/EAGLE-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-840. - Resolution: Resolved > Task Failing Nodes List and bad node detection > -- > > Key: EAGLE-840 > URL: https://issues.apache.org/jira/browse/EAGLE-840 > Project: Eagle > Issue Type: Improvement > Components: App::Job Performance Monitor >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > add Task Failing Nodes List and bad node detection -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (EAGLE-917) add Job error category and error message mapping
[ https://issues.apache.org/jira/browse/EAGLE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-917. - Resolution: Resolved > add Job error category and error message mapping > > > Key: EAGLE-917 > URL: https://issues.apache.org/jira/browse/EAGLE-917 > Project: Eagle > Issue Type: Improvement >Reporter: wujinhu >Assignee: wujinhu > > In order to query error category and error message quickly, we need to add > this mapping to eagle storage although task attempt already has this > information -- This message was sent by Atlassian JIRA (v6.3.15#6346)