[GitHub] incubator-eagle pull request #506: Eagle-612 Use LOCAL when app provider is ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 issue #506: Eagle-612 Use LOCAL when app provider is from cl...

[qingwen220]

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/506
  
LGTM


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

[GitHub] incubator-eagle pull request #506: Eagle-612 Use LOCAL when app provider is ...

[zombieJ]

GitHub user zombieJ opened a pull request:

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

Eagle-612 Use LOCAL when app provider is from class file and use Cluster 
when from jar file

When jarFile is jar file and use CLUSTER by default. (end with *.jar)
When jarFile is class and use LOCAL by default. (end with *.class)

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

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

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

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


commit 411625d32eb74348851e34df27520475242a14ef
Author: zombieJ 
Date:   2016-10-14T03:58:16Z

merge update for support Control Sequences

commit 7c514e20ed219c217079992833eab488447c0b23
Author: zombieJ 
Date:   2016-10-14T05:44:50Z

support auto adjust app mode




---
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-581) Generate a build number when building the project.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-581:
--

GitHub user pkuwm opened a pull request:

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

[EAGLE-581] Generate buildnumber when building the project.



Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [ ] Make sure the PR title is formatted like:
   `[EAGLE-] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [ ] Replace `` in the title with the actual Jira issue
   number, if there is one.
 - [ ] If this contribution is large, please file an Apache
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).

---



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

$ git pull https://github.com/pkuwm/incubator-eagle EAGLE-581

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

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


commit 5f922a77f19aa647049f792a0a6c070b86df6457
Author: pkuwm 
Date:   2016-10-14T04:31:17Z

[EAGLE-581] Generate buildnumber when building the project.




> Generate a build number when building the project.
> --
>
> Key: EAGLE-581
> URL: https://issues.apache.org/jira/browse/EAGLE-581
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Huizhi Lu
>Assignee: Huizhi Lu
> Fix For: v0.5.0
>
>
> Use case:
> we need to know what version(latest commit revision) of source code we are 
> using for the current build so that it will be convenient for us to clarify 
> different builds. So when you might make 100 builds of version 
> 0.5.0-SNAPSHOT, you can differentiate between them all.
> Solution:
> Use buildnumber-maven-plugin
> 1. Add Maven plugin buildnumber-maven-plugin to pom.xml file
> 2. Add manifest entries to META-INF/MANIFEST.MF
> Build-Branch: EAGLE-581
> Build-Commit: f6fad2ebe8a384a6d17e40c609041ff77f6a692c
> Build-Time: 2016-10-02 09:05:31 AM, UTC
> 3. Placehold VERSION.
> The build info is stored in RELEASE File in the root directory. RELEASE is 
> like:
> project.version: 0.5.0-incubating-SNAPSHOT
> build.branch: EAGLE-581
> build.commit: f6fad2ebe8a384a6d17e40c609041ff77f6a692c
> build.time: 2016-10-02 01:39:40 AM, PDT



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

[GitHub] incubator-eagle pull request #505: [EAGLE-581] Generate buildnumber when bui...

[pkuwm]

GitHub user pkuwm opened a pull request:

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

[EAGLE-581] Generate buildnumber when building the project.



Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [ ] Make sure the PR title is formatted like:
   `[EAGLE-] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [ ] Replace `` in the title with the actual Jira issue
   number, if there is one.
 - [ ] If this contribution is large, please file an Apache
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).

---



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

$ git pull https://github.com/pkuwm/incubator-eagle EAGLE-581

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

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


commit 5f922a77f19aa647049f792a0a6c070b86df6457
Author: pkuwm 
Date:   2016-10-14T04:31:17Z

[EAGLE-581] Generate buildnumber when building the project.




---
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 #468: [EAGLE-582] add simple Basic Authenticati...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-582) register simple Basic Authentication to server application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-582:
--

Github user asfgit closed the pull request at:

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


> register simple Basic Authentication to server application
> --
>
> Key: EAGLE-582
> URL: https://issues.apache.org/jira/browse/EAGLE-582
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> simple basic authentication with just some expected username-password pairs 
> configured for the application.
> This is one of the sub-tasks of ticket EAGLE-433, to successfully register a 
> simple Basic Authentication authenticator to the server application.
> With this check-in, when the server is up, any access to rest api method that 
> has a @Auth annotation on it's User field will require correct credentials.



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

[jira] [Commented] (EAGLE-582) register simple Basic Authentication to server application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-582:
--

Github user anyway1021 commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/468#discussion_r83355134
  
--- Diff: 
eagle-server/src/main/java/org/apache/eagle/server/authentication/authenticator/LdapBasicAuthenticator.java
 ---
@@ -0,0 +1,40 @@
+/*
+ * 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.authenticator;
+
+import com.google.common.base.Optional;
+import io.dropwizard.auth.AuthenticationException;
+import io.dropwizard.auth.basic.BasicCredentials;
+import org.apache.eagle.common.authentication.User;
+import 
org.apache.eagle.server.authentication.config.AuthenticationSettings;
+
+public class LdapBasicAuthenticator extends 
AbstractSwitchableAuthenticator {
+private AuthenticationSettings config = null;
+
+public LdapBasicAuthenticator(AuthenticationSettings settings) {
+super(settings, User.class);
+}
+
+public Optional authenticate(BasicCredentials credentials) 
throws AuthenticationException {
+// TODO need to implement ldap authentication logic
+boolean pass = true;
+if (pass) {
--- End diff --

it's no more than a fake placeholder, will be removed by real logic soon


> register simple Basic Authentication to server application
> --
>
> Key: EAGLE-582
> URL: https://issues.apache.org/jira/browse/EAGLE-582
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> simple basic authentication with just some expected username-password pairs 
> configured for the application.
> This is one of the sub-tasks of ticket EAGLE-433, to successfully register a 
> simple Basic Authentication authenticator to the server application.
> With this check-in, when the server is up, any access to rest api method that 
> has a @Auth annotation on it's User field will require correct credentials.



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

[GitHub] incubator-eagle pull request #468: [EAGLE-582] add simple Basic Authenticati...

[anyway1021]

Github user anyway1021 commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/468#discussion_r83355134
  
--- Diff: 
eagle-server/src/main/java/org/apache/eagle/server/authentication/authenticator/LdapBasicAuthenticator.java
 ---
@@ -0,0 +1,40 @@
+/*
+ * 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.authenticator;
+
+import com.google.common.base.Optional;
+import io.dropwizard.auth.AuthenticationException;
+import io.dropwizard.auth.basic.BasicCredentials;
+import org.apache.eagle.common.authentication.User;
+import 
org.apache.eagle.server.authentication.config.AuthenticationSettings;
+
+public class LdapBasicAuthenticator extends 
AbstractSwitchableAuthenticator {
+private AuthenticationSettings config = null;
+
+public LdapBasicAuthenticator(AuthenticationSettings settings) {
+super(settings, User.class);
+}
+
+public Optional authenticate(BasicCredentials credentials) 
throws AuthenticationException {
+// TODO need to implement ldap authentication logic
+boolean pass = true;
+if (pass) {
--- End diff --

it's no more than a fake placeholder, will be removed by real logic soon


---
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-618) migration eagle-jpm-aggregation to application framework

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-618:
--

Github user asfgit closed the pull request at:

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


> migration eagle-jpm-aggregation to application framework 
> -
>
> Key: EAGLE-618
> URL: https://issues.apache.org/jira/browse/EAGLE-618
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> We need migrate this application so that user can install it via ui.
> What need to do is add provider xml and spi to eagle-topology-assembly



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

[GitHub] incubator-eagle pull request #504: [EAGLE-618] migration eagle-jpm-aggregati...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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] [Resolved] (EAGLE-617) Scrollbar is missing when install Map Reduce History Job Monitoring

[Jilin, Jiang (JIRA)]

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

Jilin, Jiang resolved EAGLE-617.

Resolution: Fixed

> Scrollbar is missing when install Map Reduce History Job Monitoring
> ---
>
> Key: EAGLE-617
> URL: https://issues.apache.org/jira/browse/EAGLE-617
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> When I install Map Reduce History Job Monitoring and add new field 
> configures, Scrollbar is missing. My screen resolution is 2880 * 1800



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

[jira] [Commented] (EAGLE-617) Scrollbar is missing when install Map Reduce History Job Monitoring

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-617:
--

Github user asfgit closed the pull request at:

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


> Scrollbar is missing when install Map Reduce History Job Monitoring
> ---
>
> Key: EAGLE-617
> URL: https://issues.apache.org/jira/browse/EAGLE-617
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> When I install Map Reduce History Job Monitoring and add new field 
> configures, Scrollbar is missing. My screen resolution is 2880 * 1800



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

[GitHub] incubator-eagle pull request #503: EAGLE-617 Scrollbar is missing when insta...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #504: [EAGLE-618] migration eagle-jpm-aggregati...

[wujinhu]

GitHub user wujinhu opened a pull request:

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

[EAGLE-618] migration eagle-jpm-aggregation to application framework



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-618

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

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


commit 6e863d0c6a7dd94a42a1300256cf6842016b4414
Author: wujinhu 
Date:   2016-10-14T03:19:50Z

migration eagle-jpm-aggregation to application framework




---
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-618) migration eagle-jpm-aggregation to application framework

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-618:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-618] migration eagle-jpm-aggregation to application framework



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

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-618

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

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


commit 6e863d0c6a7dd94a42a1300256cf6842016b4414
Author: wujinhu 
Date:   2016-10-14T03:19:50Z

migration eagle-jpm-aggregation to application framework




> migration eagle-jpm-aggregation to application framework 
> -
>
> Key: EAGLE-618
> URL: https://issues.apache.org/jira/browse/EAGLE-618
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> We need migrate this application so that user can install it via ui.
> What need to do is add provider xml and spi to eagle-topology-assembly



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

Re: Can I build Eagle with Java 1.8?

[Huizhi Lu]

Hi Kieth,

Sorry for the version typo... I meant 0.4.x and 0.3.x.

-Huizhi

On Thu, Oct 13, 2016 at 1:05 PM, Huizhi Lu  wrote:

> Hi Kieth,
>
> Eagle 4.0.x and 3.x don't support Java 1.8.
>
> The master branch supports Java 1.8. But it has not yet been released.
>
> Please use Eagle-4.x and Java 1.7
>
>
> Best,
> Huizhi
>
> On Thu, Oct 13, 2016 at 1:00 PM, Keith Wiley  wrote:
>
>> I see that the requirements indicate Java 1.7.  My OS 10.11 Mac seems to
>> have Java 1.8 and the build is failing for reasons that appear correlated
>> with that discrepancy.  Is there some way to build Eagle with Java 1.8 or
>> do I have to install Java 1.7 before I can use Eagle?
>>
>> I also tried building Eagle inside the HortonWorks sandbox docker, which
>> appears to have Java 1.7, but it runs out of Java heap space.
>>
>> Thanks.
>>
>> 
>> Keith Wiley
>> Integers
>> kei...@integris.io
>>
>>
>>
>>
>

[jira] [Commented] (EAGLE-617) Scrollbar is missing when install Map Reduce History Job Monitoring

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-617:
--

Github user wujinhu commented on the issue:

https://github.com/apache/incubator-eagle/pull/503
  
LGTM


> Scrollbar is missing when install Map Reduce History Job Monitoring
> ---
>
> Key: EAGLE-617
> URL: https://issues.apache.org/jira/browse/EAGLE-617
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> When I install Map Reduce History Job Monitoring and add new field 
> configures, Scrollbar is missing. My screen resolution is 2880 * 1800



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

[GitHub] incubator-eagle pull request #468: [EAGLE-582] add simple Basic Authenticati...

[haoch]

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/468#discussion_r83352374
  
--- Diff: 
eagle-server/src/main/java/org/apache/eagle/server/authentication/authenticator/LdapBasicAuthenticator.java
 ---
@@ -0,0 +1,40 @@
+/*
+ * 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.authenticator;
+
+import com.google.common.base.Optional;
+import io.dropwizard.auth.AuthenticationException;
+import io.dropwizard.auth.basic.BasicCredentials;
+import org.apache.eagle.common.authentication.User;
+import 
org.apache.eagle.server.authentication.config.AuthenticationSettings;
+
+public class LdapBasicAuthenticator extends 
AbstractSwitchableAuthenticator {
+private AuthenticationSettings config = null;
+
+public LdapBasicAuthenticator(AuthenticationSettings settings) {
+super(settings, User.class);
+}
+
+public Optional authenticate(BasicCredentials credentials) 
throws AuthenticationException {
+// TODO need to implement ldap authentication logic
+boolean pass = true;
+if (pass) {
--- End diff --

pass is always true?


---
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 issue #503: EAGLE-617 Scrollbar is missing when install Map ...

[wujinhu]

Github user wujinhu commented on the issue:

https://github.com/apache/incubator-eagle/pull/503
  
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-582) register simple Basic Authentication to server application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-582:
--

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/468#discussion_r83352374
  
--- Diff: 
eagle-server/src/main/java/org/apache/eagle/server/authentication/authenticator/LdapBasicAuthenticator.java
 ---
@@ -0,0 +1,40 @@
+/*
+ * 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.authenticator;
+
+import com.google.common.base.Optional;
+import io.dropwizard.auth.AuthenticationException;
+import io.dropwizard.auth.basic.BasicCredentials;
+import org.apache.eagle.common.authentication.User;
+import 
org.apache.eagle.server.authentication.config.AuthenticationSettings;
+
+public class LdapBasicAuthenticator extends 
AbstractSwitchableAuthenticator {
+private AuthenticationSettings config = null;
+
+public LdapBasicAuthenticator(AuthenticationSettings settings) {
+super(settings, User.class);
+}
+
+public Optional authenticate(BasicCredentials credentials) 
throws AuthenticationException {
+// TODO need to implement ldap authentication logic
+boolean pass = true;
+if (pass) {
--- End diff --

pass is always true?


> register simple Basic Authentication to server application
> --
>
> Key: EAGLE-582
> URL: https://issues.apache.org/jira/browse/EAGLE-582
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> simple basic authentication with just some expected username-password pairs 
> configured for the application.
> This is one of the sub-tasks of ticket EAGLE-433, to successfully register a 
> simple Basic Authentication authenticator to the server application.
> With this check-in, when the server is up, any access to rest api method that 
> has a @Auth annotation on it's User field will require correct credentials.



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

[GitHub] incubator-eagle pull request #503: EAGLE-617 Scrollbar is missing when insta...

[zombieJ]

GitHub user zombieJ opened a pull request:

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

EAGLE-617 Scrollbar is missing when install Map Reduce History Job 
Monitoring

add check logic in uiSrv. When dialog close, will check current existed 
dialog for body 'modal-open'

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

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

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

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


commit 7ab80eb9b9476cc7e0727a4a0652db2d29dc3313
Author: zombieJ 
Date:   2016-10-14T02:55:31Z

add dialog check after dialog close




---
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-618) migration eagle-jpm-aggregation to application framework

[wujinhu (JIRA)]

wujinhu created EAGLE-618:
-

 Summary: migration eagle-jpm-aggregation to application framework 
 Key: EAGLE-618
 URL: https://issues.apache.org/jira/browse/EAGLE-618
 Project: Eagle
  Issue Type: Improvement
Reporter: wujinhu
Assignee: wujinhu


We need migrate this application so that user can install it via ui.
What need to do is add provider xml and spi to eagle-topology-assembly



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

[GitHub] incubator-eagle pull request #502: [Minor]: Update unitApp configuration

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 issue #502: [Minor]: Update unitApp configuration

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/502
  
LGTM


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

[GitHub] incubator-eagle pull request #497: [Minor] Simply reorg maven repositories

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: [DISCUSS] restart Eagle graduate discussion

[Da Zhou]

Vote +1.
 "Eagle Maturity Assessment" looks good to me. Great process has been made
since last discussion:

- Lots of new features have been introduced, now Apache Eagle has become
more powerful and user-friendly.(eg,  Application Management through Eagle
UI.)
- Also many fixes have been checked in, which makes Eagle more stable and
robust.
- Community is getting more active, we can tell this based on daily
discussion happened in the emails.
- Apache Eagle is getting more attention by different corporations and
organizations,  their cooperation has been reported online (eg, Yahoo News)

Regards,
Da

On Wed, Oct 12, 2016 at 8:12 PM, Edward Zhang 
wrote:

> Hi Eagle Community,
>
> It's been more than 2 months and a lot have been improved since we last
> time discussed Eagle graduation. Here I want to suggest we restart
> discussion of Eagle graduation. Please share your comments.
>
> Some documents and data are as follows:
> 1. Maturity assessment,
> https://cwiki.apache.org/confluence/display/EAG/Eagle+
> Podling+Maturity+Assessment
> 2. https://cwiki.apache.org/confluence/display/EAG/Documentation
> 3. Four new committers were added since incubation
> 4. Two releases are made
> 5. >600 Jira tickets,
> https://issues.apache.org/jira/browse/EAGLE-614?jql=project%20%3D%20EAGLE
> 6. ~500 pull requests.
> https://github.com/apache/incubator-eagle/pulls?utf8=%E2%9C%93=is%3Apr
>
> Thanks
> Edward
>
>
> On Sat, Oct 1, 2016 at 7:34 AM, Ge, Jing  wrote:
>
> > Hi Jijun,
> >
> > Thanks for your nice feedback and excellent contribution. We appreciate
> it.
> >
> > Best regards
> > Jing
> >
> > On 9/30/16, 8:43 PM, "Tang Jijun(上海_技术部_数据平台_唐觊隽)" 
> > wrote:
> >
> > Great work! Great advances have been made for Apache Eagle.
> > I think Apache Eagle will became a great project for community with
> > these improvement.
> >
> > Best Wishes
> >
> > 唐觊隽
> > Jr. Engineer , Architecture - Fundation, Tech Dept
> > Floor 4, 295 ZUCHONGZHI RD, Zhangjiang, Shanghai (201203)
> >
> > -邮件原件-
> > 发件人: Ge, Jing [mailto:ji...@ebay.com]
> > 发送时间: 2016年9月30日 19:50
> > 收件人: dev@eagle.incubator.apache.org; Tang Jijun(上海_技术部_数据平台_唐觊隽)
> > 主题: Re: [DISCUSS] Is Eagle ready to graduate?
> >
> > Hi Jijun,
> >
> > Thanks for pointing out where we can improve ourselves. We have been
> > working on that since we got your email. Now:
> >
> > 1. We have CI server which will make sure the code will be stable and
> > build will be successful.
> > 2. We have more than 430 Unit tests.
> > 3. We have published fundamental documentation to let user and
> > developer understand Eagle and will continue working on them a.
> Development
> > Guide https://cwiki.apache.org/confluence/display/EAG/Development+Guide
> > b. Product features introduction https://cwiki.apache.org/
> > confluence/display/EAG/Development+Guide
> > c. More information w.r.t. roadmap or technical design, etc. can be
> > found at https://cwiki.apache.org/confluence/display/EAG/Eagle
> >
> > Speaking of documentation, many thanks for your contribution to the
> > Alert Engine on Spark Streaming https://cwiki.apache.org/
> > confluence/display/EAG/Alert+Engine+on+Spark+Streaming. We really
> > appreciate it.
> >
> > Your concerns should be solved. please let us know your thoughts.
> >
> > Best regards
> > Jing
> >
> > On 9/1/16, 1:17 PM, "Michael Wu"  wrote:
> >
> > Security page at http://eagle.incubator.apache.
> org/sup/index.html
> > is
> > updated with new content, please review if it conforms to what we
> > expected.
> >
> > On Thu, Aug 25, 2016 at 10:28 AM, Michael Wu  >
> > wrote:
> >
> > > Hi mentors,
> > >
> > > I will update security page content taking the mentioned
> aspects.
> > >
> > > Except for the security part, is there any other gaps that you
> > feel eagle
> > > has to fill before graduation? Please feel free to point issues
> > out and we
> > > will do our best to get aligned to what graduation requires.
> > Thanks.
> > >
> > > Michael
> > >
> > > On Wed, Aug 24, 2016 at 9:53 AM, Julian Hyde  >
> > wrote:
> > >
> > >> I did a quick survey, and it seems that most projects do not
> > have a
> > >> security team[1], which means that vulnerabilities should be
> > reported to
> > >> secur...@apache.org. Of the projects that do, Kafka seems a
> > good model
> > >> to follow; its security page is simple and clear[2].
> > >>
> > >> Julian
> > >>
> > >> [1] http://www.apache.org/security/projects.html <
> > >> http://www.apache.org/security/projects.html>
> > >>
> > >> [2] http://kafka.apache.org/project-security.html <
> > >> 

Re: Can I build Eagle with Java 1.8?

[Huizhi Lu]

Hi Kieth,

Eagle 4.0.x and 3.x don't support Java 1.8.

The master branch supports Java 1.8. But it has not yet been released.

Please use Eagle-4.x and Java 1.7


Best,
Huizhi

On Thu, Oct 13, 2016 at 1:00 PM, Keith Wiley  wrote:

> I see that the requirements indicate Java 1.7.  My OS 10.11 Mac seems to
> have Java 1.8 and the build is failing for reasons that appear correlated
> with that discrepancy.  Is there some way to build Eagle with Java 1.8 or
> do I have to install Java 1.7 before I can use Eagle?
>
> I also tried building Eagle inside the HortonWorks sandbox docker, which
> appears to have Java 1.7, but it runs out of Java heap space.
>
> Thanks.
>
> 
> Keith Wiley
> Integers
> kei...@integris.io
>
>
>
>

Can I build Eagle with Java 1.8?

[Keith Wiley]

I see that the requirements indicate Java 1.7.  My OS 10.11 Mac seems to have 
Java 1.8 and the build is failing for reasons that appear correlated with that 
discrepancy.  Is there some way to build Eagle with Java 1.8 or do I have to 
install Java 1.7 before I can use Eagle?

I also tried building Eagle inside the HortonWorks sandbox docker, which 
appears to have Java 1.7, but it runs out of Java heap space.

Thanks.


Keith Wiley
Integers
kei...@integris.io

[jira] [Commented] (EAGLE-582) register simple Basic Authentication to server application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-582:
--

Github user anyway1021 closed the pull request at:

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


> register simple Basic Authentication to server application
> --
>
> Key: EAGLE-582
> URL: https://issues.apache.org/jira/browse/EAGLE-582
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> simple basic authentication with just some expected username-password pairs 
> configured for the application.
> This is one of the sub-tasks of ticket EAGLE-433, to successfully register a 
> simple Basic Authentication authenticator to the server application.
> With this check-in, when the server is up, any access to rest api method that 
> has a @Auth annotation on it's User field will require correct credentials.



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

[jira] [Commented] (EAGLE-582) register simple Basic Authentication to server application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-582:
--

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/468
  
for re-trigger the reviewer ci build


> register simple Basic Authentication to server application
> --
>
> Key: EAGLE-582
> URL: https://issues.apache.org/jira/browse/EAGLE-582
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> simple basic authentication with just some expected username-password pairs 
> configured for the application.
> This is one of the sub-tasks of ticket EAGLE-433, to successfully register a 
> simple Basic Authentication authenticator to the server application.
> With this check-in, when the server is up, any access to rest api method that 
> has a @Auth annotation on it's User field will require correct credentials.



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

[jira] [Commented] (EAGLE-582) register simple Basic Authentication to server application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-582:
--

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/468
  
re-trigger ci build


> register simple Basic Authentication to server application
> --
>
> Key: EAGLE-582
> URL: https://issues.apache.org/jira/browse/EAGLE-582
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> simple basic authentication with just some expected username-password pairs 
> configured for the application.
> This is one of the sub-tasks of ticket EAGLE-433, to successfully register a 
> simple Basic Authentication authenticator to the server application.
> With this check-in, when the server is up, any access to rest api method that 
> has a @Auth annotation on it's User field will require correct credentials.



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

[jira] [Commented] (EAGLE-582) register simple Basic Authentication to server application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-582:
--

GitHub user anyway1021 reopened a pull request:

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

[EAGLE-582] add simple Basic Authentication registration to server appl…

This is one of the sub-tasks of ticket EAGLE-433, to successfully register 
a simple Basic Authentication authenticator to the server application.

With this check-in, when the server is up, any access to rest api method 
that has a @Auth annotation on it's User field will require correct credentials.

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

$ git pull https://github.com/anyway1021/incubator-eagle EAGLE-582

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

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


commit df9e2b4d9cb2a10fda03b7fe9eb790026d95de30
Author: anyway1021 
Date:   2016-10-01T08:18:48Z

EAGLE-582 add simple Basic Authentication registration to server application

commit 95b5feb68214bf3d18ae6224681d069ebcc564ef
Author: anyway1021 
Date:   2016-10-01T08:40:56Z

modify config key from auth.basic to auth.simple

commit e899d55de7aa8e1c87cbfec26aebe32530cc24f9
Author: anyway1021 
Date:   2016-10-10T03:48:18Z

remove specific info for ldap

commit 40078531f2ccc96defa78ffddc34563e2b1e7c57
Author: anyway1021 
Date:   2016-10-10T03:58:40Z

remove useless commented code

commit 3774c436cfbefddcd27be2a305ab025aa6f0cda5
Author: anyway1021 
Date:   2016-10-11T02:34:32Z

move authentication settings from application.conf to configuration.yml, 
and modify impacted classes

commit 4fbc41dbba39ed3d684334dcddabd79f39cf8f5f
Author: anyway1021 
Date:   2016-10-11T02:44:25Z

remove glassfish-jersey-server dependency for it's useless

commit d4c68b7b64bf36171ee40cc7223a29cde0c33406
Author: anyway1021 
Date:   2016-10-13T07:07:08Z

move User.java from eagle-server to eagle-common project so that other sub 
projects could depend on it

commit cf4bc3f07741b79e10395be77efa651114403541
Author: anyway1021 
Date:   2016-10-13T07:13:21Z

add switching functionality to enable/disable only in configuration.yml, 
without modifying code

commit db62a327fc85c5b57114d90e5d8b48ed0610cefe
Author: anyway1021 
Date:   2016-10-13T08:03:22Z

obey checkstyle instructions

commit a863058c3d2064d4aa39439cad340e65348adce7
Author: anyway1021 
Date:   2016-10-13T08:29:10Z

add new content to eagle-server/src/test/resources/configuration.yml for 
unit test




> register simple Basic Authentication to server application
> --
>
> Key: EAGLE-582
> URL: https://issues.apache.org/jira/browse/EAGLE-582
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> simple basic authentication with just some expected username-password pairs 
> configured for the application.
> This is one of the sub-tasks of ticket EAGLE-433, to successfully register a 
> simple Basic Authentication authenticator to the server application.
> With this check-in, when the server is up, any access to rest api method that 
> has a @Auth annotation on it's User field will require correct credentials.



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

[GitHub] incubator-eagle issue #468: [EAGLE-582] add simple Basic Authentication regi...

[anyway1021]

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/468
  
re-trigger ci build


---
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 issue #502: [Minor]: Update unitApp configuration

[wujinhu]

Github user wujinhu commented on the issue:

https://github.com/apache/incubator-eagle/pull/502
  
LGTM


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

[GitHub] incubator-eagle pull request #502: [Minor]: Update unitApp configuration

[qingwen220]

GitHub user qingwen220 opened a pull request:

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

[Minor]: Update unitApp configuration

1. remove 'topology.name' in AlertUnitTopologyAppProvider.xml
2. remove topology assembly in jpm 

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

$ git pull https://github.com/qingwen220/incubator-eagle unitApp

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

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


commit 9e6eef39fc0deabe35fbbaede2c01bf163ad8578
Author: Zhao, Qingwen 
Date:   2016-10-13T11:57:58Z

update unitApp configuration




---
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-617) Scrollbar is missing when install Map Reduce History Job Monitoring

[wujinhu (JIRA)]

wujinhu created EAGLE-617:
-

 Summary: Scrollbar is missing when install Map Reduce History Job 
Monitoring
 Key: EAGLE-617
 URL: https://issues.apache.org/jira/browse/EAGLE-617
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: Jilin, Jiang
 Fix For: v0.5.0


When I install Map Reduce History Job Monitoring and add new field configures, 
Scrollbar is missing. My screen resolution is 2880 * 1800



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

[jira] [Commented] (EAGLE-616) AlertEngine: Reduce the connection from alert-service to ZK

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-616:
--

Github user mizeng commented on the issue:

https://github.com/apache/incubator-eagle/pull/501
  
@RalphSu could you plz help to review?


> AlertEngine: Reduce the connection from alert-service to ZK
> ---
>
> Key: EAGLE-616
> URL: https://issues.apache.org/jira/browse/EAGLE-616
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> In QA, it used to show too much connection from alert-service to zookeeper.
> We only use zk for exclusive lock and spec version notify, should not have so 
> much connection.



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

[jira] [Commented] (EAGLE-616) AlertEngine: Reduce the connection from alert-service to ZK

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-616:
--

GitHub user mizeng opened a pull request:

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

[EAGLE-616] AlertEngine: Reduce the connection from alert-service to ZK

In QA, it used to show too much connection from alert-service to zookeeper.
We only use zk for exclusive lock and spec version notify, should not have 
so much connection.

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

$ git pull https://github.com/mizeng/incubator-eagle EAGLE-616

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

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


commit 30f881d3cb24d167d521d6477e6b728b38c923dd
Author: mizeng 
Date:   2016-10-13T09:28:06Z

[EAGLE-616] AlertEngine: Reduce the connection from alert-service to ZK




> AlertEngine: Reduce the connection from alert-service to ZK
> ---
>
> Key: EAGLE-616
> URL: https://issues.apache.org/jira/browse/EAGLE-616
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> In QA, it used to show too much connection from alert-service to zookeeper.
> We only use zk for exclusive lock and spec version notify, should not have so 
> much connection.



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

[GitHub] incubator-eagle issue #501: [EAGLE-616] AlertEngine: Reduce the connection f...

[mizeng]

Github user mizeng commented on the issue:

https://github.com/apache/incubator-eagle/pull/501
  
@RalphSu could you plz help to review?


---
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-616) AlertEngine: Reduce the connection from alert-service to ZK

[Zeng, Bryant (JIRA)]

Zeng, Bryant created EAGLE-616:
--

 Summary: AlertEngine: Reduce the connection from alert-service to 
ZK
 Key: EAGLE-616
 URL: https://issues.apache.org/jira/browse/EAGLE-616
 Project: Eagle
  Issue Type: Bug
Reporter: Zeng, Bryant
Assignee: Zeng, Bryant


In QA, it used to show too much connection from alert-service to zookeeper.
We only use zk for exclusive lock and spec version notify, should not have so 
much connection.




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

[jira] [Commented] (EAGLE-594) Remove raw alert from kafka publisher

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-594:
--

Github user asfgit closed the pull request at:

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


> Remove raw alert from kafka publisher
> -
>
> Key: EAGLE-594
> URL: https://issues.apache.org/jira/browse/EAGLE-594
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Garrett Li
>Assignee: Garrett Li
>Priority: Minor
>
> We are leveraging configured deduplicator to dedup the duplicated alerts 
> before publish to kafka, email, slack, etc. However, sometimes we may still 
> want to keep the raw alerts in kafka. Here we have defined 
> rawAlertNamespaceLabel and rawAlertNamespaceValue custom fields to emit the 
> raw alerts into kafka. 
> However, these configured namespace concept is ebay/sherlock specific, we 
> should remove it from eagle and use it ebay/sherlock extended kafka publisher.



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

[GitHub] incubator-eagle pull request #478: EAGLE-594: Remove raw alert from kafka pu...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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] [Resolved] (EAGLE-604) Support view/editing application configuration after installed

[Jilin, Jiang (JIRA)]

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

Jilin, Jiang resolved EAGLE-604.

Resolution: Fixed

> Support view/editing application configuration after installed
> --
>
> Key: EAGLE-604
> URL: https://issues.apache.org/jira/browse/EAGLE-604
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Jilin, Jiang
>  Labels: app-manager, eagle-ui
> Fix For: v0.5.0
>
>
> Support editing application configuration after installed



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

[GitHub] incubator-eagle pull request #500: Eagle-604 Support view/editing applicatio...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 issue #500: Eagle-604 Support view/editing application confi...

[qingwen220]

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/500
  
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] [Closed] (EAGLE-614) NPE in DynamicPolicyLoader

[Zeng, Bryant (JIRA)]

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

Zeng, Bryant closed EAGLE-614.
--
Resolution: Fixed

> NPE in DynamicPolicyLoader
> --
>
> Key: EAGLE-614
> URL: https://issues.apache.org/jira/browse/EAGLE-614
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Find exception as below:
> INFO  [2016-10-13 01:15:02,965] 
> org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: policies 
> loader start.
> INFO  [2016-10-13 01:15:02,966] 
> org.apache.eagle.alert.service.MetadataServiceClientImpl: query URL 
> http://localhost:8080/rest/metadata/policies
> ERROR [2016-10-13 01:15:02,972] 
> org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: error loading 
> policy, but continue to run
> ! java.lang.NullPointerException: null
> ! at 
> org.apache.eagle.alert.engine.coordinator.PolicyDefinition.equals(PolicyDefinition.java:150)
>  ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded.jar
> :0.5.0-incubating-SNAPSHOT]
> ! at 
> org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader.run(DynamicPolicyLoader.java:69)
>  ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded.
> jar:0.5.0-incubating-SNAPSHOT]
> ! at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_102]
> ! at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_102]
> ! at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_102]
> ! at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_102]
> ! at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_102]
> ! at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_102]
> ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_102]
> we have compare null with other object which should be avoided.



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

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

[Apache Jenkins Server]

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

[jira] [Commented] (EAGLE-614) NPE in DynamicPolicyLoader

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-614:
--

Github user asfgit closed the pull request at:

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


> NPE in DynamicPolicyLoader
> --
>
> Key: EAGLE-614
> URL: https://issues.apache.org/jira/browse/EAGLE-614
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Find exception as below:
> INFO  [2016-10-13 01:15:02,965] 
> org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: policies 
> loader start.
> INFO  [2016-10-13 01:15:02,966] 
> org.apache.eagle.alert.service.MetadataServiceClientImpl: query URL 
> http://localhost:8080/rest/metadata/policies
> ERROR [2016-10-13 01:15:02,972] 
> org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: error loading 
> policy, but continue to run
> ! java.lang.NullPointerException: null
> ! at 
> org.apache.eagle.alert.engine.coordinator.PolicyDefinition.equals(PolicyDefinition.java:150)
>  ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded.jar
> :0.5.0-incubating-SNAPSHOT]
> ! at 
> org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader.run(DynamicPolicyLoader.java:69)
>  ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded.
> jar:0.5.0-incubating-SNAPSHOT]
> ! at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_102]
> ! at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_102]
> ! at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_102]
> ! at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_102]
> ! at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_102]
> ! at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_102]
> ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_102]
> we have compare null with other object which should be avoided.



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

[GitHub] incubator-eagle pull request #498: EAGLE-614: NPE in DynamicPolicyLoader

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #486: EAGLE-602: Exception that Spec Version [x...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-602) Exception that Spec Version [xxx] of AlertBolt is newer than Stream Event Version [null]!

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-602:
--

Github user asfgit closed the pull request at:

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


> Exception that Spec Version [xxx] of AlertBolt is newer than Stream Event 
> Version [null]!
> -
>
> Key: EAGLE-602
> URL: https://issues.apache.org/jira/browse/EAGLE-602
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> Just find exception as below:
> 2016-10-06 22:51:41 org.apache.eagle.alert.engine.runner.AlertBolt [WARN] 
> Spec Version [spec_version_1475817732537] of AlertBolt is newer than Stream 
> Event Version [null]!
> Seems there's an error when get meta version from stream event or 
> initialising failed when stream event version is null.



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

[jira] [Commented] (EAGLE-582) register simple Basic Authentication to server application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-582:
--

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/468
  
@haoch 
@all

Would like to merge but because some new classes are added to support 
switching authentication without modifying code, I think it may be better to 
ask you to review again.

The reason of doing this is:
1. dropwizard 0.7.1 only supports @Auth annotation to mark authentication 
on additional User argument of REST resource methods, means if we'd like a REST 
path be authenticated, we should add a parameter to the method, such as "public 
List list(@Auth User user)". In this way, any REST resource we don't want to 
authenticate could only be freed by removing the parameter.

2. Currently, while registering the Authenticators, by default API, we 
would register a BasicAuthProvider that doesn't support switching 
authentication on or off. People may think, we could skip registering it when 
we want to switch off the authentication, however, this approach would cause 
4xx http error for unable to map the coded "@Auth" parameters correctly.

3. Based on the above 2, I  create a SwitchableBasicAuthProvider to involve 
switching configuration, and by registering this provider on starting the 
server, people could configure a param "enabled=true|false" in 
configuration.yml, to enable|disable authentication, without having to change 
code, re-compile, or re-deploy.

Besides, to make other projects able to depend on class User, I moved it 
from eagle-server to eagle-common under package: 
org.apache.eagle.common.authentication, please consider if it's appropriate, 
thanks.

Hopefully it's not a redundant modification. 

Michael


> register simple Basic Authentication to server application
> --
>
> Key: EAGLE-582
> URL: https://issues.apache.org/jira/browse/EAGLE-582
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Michael Wu
>Assignee: Michael Wu
> Fix For: v0.5.0
>
>
> simple basic authentication with just some expected username-password pairs 
> configured for the application.
> This is one of the sub-tasks of ticket EAGLE-433, to successfully register a 
> simple Basic Authentication authenticator to the server application.
> With this check-in, when the server is up, any access to rest api method that 
> has a @Auth annotation on it's User field will require correct credentials.



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

[GitHub] incubator-eagle issue #468: [EAGLE-582] add simple Basic Authentication regi...

[anyway1021]

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/468
  
@haoch 
@all

Would like to merge but because some new classes are added to support 
switching authentication without modifying code, I think it may be better to 
ask you to review again.

The reason of doing this is:
1. dropwizard 0.7.1 only supports @Auth annotation to mark authentication 
on additional User argument of REST resource methods, means if we'd like a REST 
path be authenticated, we should add a parameter to the method, such as "public 
List list(@Auth User user)". In this way, any REST resource we don't want to 
authenticate could only be freed by removing the parameter.

2. Currently, while registering the Authenticators, by default API, we 
would register a BasicAuthProvider that doesn't support switching 
authentication on or off. People may think, we could skip registering it when 
we want to switch off the authentication, however, this approach would cause 
4xx http error for unable to map the coded "@Auth" parameters correctly.

3. Based on the above 2, I  create a SwitchableBasicAuthProvider to involve 
switching configuration, and by registering this provider on starting the 
server, people could configure a param "enabled=true|false" in 
configuration.yml, to enable|disable authentication, without having to change 
code, re-compile, or re-deploy.

Besides, to make other projects able to depend on class User, I moved it 
from eagle-server to eagle-common under package: 
org.apache.eagle.common.authentication, please consider if it's appropriate, 
thanks.

Hopefully it's not a redundant modification. 

Michael


---
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 #500: Eagle-604 Support view/editing applicatio...

[zombieJ]

GitHub user zombieJ opened a pull request:

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

Eagle-604 Support view/editing application configuration after installed

Support view/editing application configuration after installed

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

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

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

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


commit f69209abc89801171b77cd5618cc368e81dfc96d
Author: zombieJ 
Date:   2016-10-11T09:21:03Z

ui pretty

commit 47b4eae825cb29b510e0aacc07b1269c9768417a
Author: zombieJ 
Date:   2016-10-12T08:12:29Z

hide play/stop if not executable

commit 10d43784ce74a79a3caedf989c78016ede99a209
Author: zombieJ 
Date:   2016-10-12T10:02:32Z

update common parseJSON logic

commit 25d50bc2aa8e56ad3d4f8c17b7157b5d3dfb8027
Author: zombieJ 
Date:   2016-10-13T02:47:51Z

support update application

commit f7aed178d1d3960627932d4c74ad8ecd172d32b5
Author: zombieJ 
Date:   2016-10-13T03:22:29Z

tab of policy detail

commit 096596eccc17327154b2db14eb1910da24406bec
Author: zombieJ 
Date:   2016-10-13T04:35:29Z

add app detail page

commit d059ac38008c6d3d8775a925d4093c65e2f7fab6
Author: zombieJ 
Date:   2016-10-13T06:46:13Z

add dep warning

commit f9e3de10933052f2e28bd1320525ea9a25a30cea
Author: zombieJ 
Date:   2016-10-13T07:19:22Z

move streams to alert list

commit baf9bec69e0defaff973a52f260ca4fe558d4e05
Author: zombieJ 
Date:   2016-10-13T07:28:00Z

clean unused content




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