[GitHub] eagle issue #905: HBase Naming that unify `Hbase` and `HBase` into `HBase`
Github user asdf2014 commented on the issue: https://github.com/apache/eagle/pull/905 @jhsenjaliya Already done. --- 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-998) Add eagle csd
[ https://issues.apache.org/jira/browse/EAGLE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972061#comment-15972061 ] ASF GitHub Bot commented on EAGLE-998: -- Github user chitin commented on a diff in the pull request: https://github.com/apache/eagle/pull/908#discussion_r111864052 --- Diff: eagle-external/eagle-cdh/src/aux/eagle-server.sh --- @@ -0,0 +1,135 @@ +#!/bin/bash --- End diff -- Thank you very much for your review. I have used it in my company for a long time. > Add eagle csd > - > > Key: EAGLE-998 > URL: https://issues.apache.org/jira/browse/EAGLE-998 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng >Priority: Minor > Fix For: v0.6.0 > > > Add eagle-cdh in eagle-external, users who use cdh can integrate eagle to > cloudera manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-981) GC overhead limit exceeded
[ https://issues.apache.org/jira/browse/EAGLE-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971926#comment-15971926 ] ASF GitHub Bot commented on EAGLE-981: -- Github user asdf2014 commented on the issue: https://github.com/apache/eagle/pull/896 @jhsenjaliya Okey. > GC overhead limit exceeded > -- > > Key: EAGLE-981 > URL: https://issues.apache.org/jira/browse/EAGLE-981 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Travis >Reporter: Benedict Jin > Labels: CI > Fix For: v0.4.1 > > Attachments: gc_overhead.png > > Original Estimate: 24h > Remaining Estimate: 24h > > Travis throw `GC overhead limit exceeded` exception because the default `JVM` > option of maven limit the resource of Travis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #896: [EAGLE-981] GC overhead limit exceeded
Github user asdf2014 closed the pull request at: https://github.com/apache/eagle/pull/896 --- 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 #916: [MINOR] adding myself in developer list as a first commit
Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/916 This was merged with master, will rebase branch-0.5 or cherry pick this later. --- 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 #916: [MINOR] adding myself in developer list as a first ...
Github user jhsenjaliya closed the pull request at: https://github.com/apache/eagle/pull/916 --- 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 #897: [EAGLE-982] The log length has exceeded the limit o...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/897 --- 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 #897: [EAGLE-982] The log length has exceeded the limit of 4 MB ...
Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/897 @asdf2014 please squash the commits again and I should merge this. --- 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-998) Add eagle csd
[ https://issues.apache.org/jira/browse/EAGLE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971579#comment-15971579 ] ASF GitHub Bot commented on EAGLE-998: -- Github user jhsenjaliya commented on a diff in the pull request: https://github.com/apache/eagle/pull/908#discussion_r111810600 --- Diff: eagle-external/eagle-cdh/src/aux/eagle-server.sh --- @@ -0,0 +1,135 @@ +#!/bin/bash --- End diff -- while packaging this module, can you pick up eagle.conf and copy it as eagle.properties via maven-assembly-plugin since the file content dont change ? btw, i dont see eagle.properties file in this PR. is it in different format than eagle.conf? > Add eagle csd > - > > Key: EAGLE-998 > URL: https://issues.apache.org/jira/browse/EAGLE-998 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng >Priority: Minor > Fix For: v0.6.0 > > > Add eagle-cdh in eagle-external, users who use cdh can integrate eagle to > cloudera manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #908: [EAGLE-998]Add eagle csd
Github user jhsenjaliya commented on a diff in the pull request: https://github.com/apache/eagle/pull/908#discussion_r111810600 --- Diff: eagle-external/eagle-cdh/src/aux/eagle-server.sh --- @@ -0,0 +1,135 @@ +#!/bin/bash --- End diff -- while packaging this module, can you pick up eagle.conf and copy it as eagle.properties via maven-assembly-plugin since the file content dont change ? btw, i dont see eagle.properties file in this PR. is it in different format than eagle.conf? --- 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-1007) Fix memory leak in ExecutionRuntimeManager
[ https://issues.apache.org/jira/browse/EAGLE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971024#comment-15971024 ] ASF GitHub Bot commented on EAGLE-1007: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/917 > Fix memory leak in ExecutionRuntimeManager > -- > > Key: EAGLE-1007 > URL: https://issues.apache.org/jira/browse/EAGLE-1007 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > Fix memory leak in ExecutionRuntimeManager > As equal method is not overrided in {{AbstractEnvironment}}, below return > statement has never been executed. > {code} > if (executionRuntimeCache.containsKey(environment)) { > return executionRuntimeCache.get(environment); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-982) The log length has exceeded the limit of 4 MB in Travis
[ https://issues.apache.org/jira/browse/EAGLE-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971005#comment-15971005 ] ASF GitHub Bot commented on EAGLE-982: -- Github user asdf2014 commented on the issue: https://github.com/apache/eagle/pull/897 Those changes about `.travis.yml` file shouldn't effect `Jenkins`. It seems like the `maven-surefire-plugin` throw a `ExecutionException` to make this build process failed. ```bash [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project eagle-app-streamproxy: ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was /bin/sh -c cd /home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-core/eagle-app/eagle-app-streamproxy && /usr/local/asfpackages/java/jdk1.8.0_121/jre/bin/java -XX:-UseGCOverheadLimit -jar /home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-core/eagle-app/eagle-app-streamproxy/target/surefire/surefirebooter8929133803599728653.jar /home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-core/eagle-app/eagle-app-streamproxy/target/surefire/surefire4241285850518905830tmp /home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-core/eagle-app/eagle-app-streamproxy/target/surefire/surefire_2332892144259826349419tmp ``` > The log length has exceeded the limit of 4 MB in Travis > --- > > Key: EAGLE-982 > URL: https://issues.apache.org/jira/browse/EAGLE-982 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Travis >Reporter: Benedict Jin > Labels: CI > Fix For: v0.4.1 > > Attachments: travis_log.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Maven throw too many warnings for checking `Code Style` in `Travis`. Should > we disable it for a while until we fix those `Code Style` issues? > ``` > The log length has exceeded the limit of 4 MB (this usually means that the > test suite is raising the same exception over and over). > The job has been terminated > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #897: [EAGLE-982] The log length has exceeded the limit of 4 MB ...
Github user asdf2014 commented on the issue: https://github.com/apache/eagle/pull/897 Those changes about `.travis.yml` file shouldn't effect `Jenkins`. It seems like the `maven-surefire-plugin` throw a `ExecutionException` to make this build process failed. ```bash [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project eagle-app-streamproxy: ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was /bin/sh -c cd /home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-core/eagle-app/eagle-app-streamproxy && /usr/local/asfpackages/java/jdk1.8.0_121/jre/bin/java -XX:-UseGCOverheadLimit -jar /home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-core/eagle-app/eagle-app-streamproxy/target/surefire/surefirebooter8929133803599728653.jar /home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-core/eagle-app/eagle-app-streamproxy/target/surefire/surefire4241285850518905830tmp /home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-core/eagle-app/eagle-app-streamproxy/target/surefire/surefire_2332892144259826349419tmp ``` --- 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-1007) Fix memory leak in ExecutionRuntimeManager
[ https://issues.apache.org/jira/browse/EAGLE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970935#comment-15970935 ] ASF GitHub Bot commented on EAGLE-1007: --- GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/917 EAGLE-1007: Fix memory leak in ExecutionRuntimeManager https://issues.apache.org/jira/browse/EAGLE-1007 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/eagle EAGLE-1007 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/917.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 #917 commit 20d7a1555f269c1e1728cd843e1369ae453deaa0 Author: Zhao, QingwenDate: 2017-04-12T06:46:53Z refine app config commit 9a2871a7d2424e790a41833ad5b3eb541452b61c Author: Zhao, Qingwen Date: 2017-04-17T09:38:43Z Merge branch 'master' of https://github.com/qingwen220/incubator-eagle commit cc8c366f771cef7d510d49483bd08a29a399864a Author: Zhao, Qingwen Date: 2017-04-17T10:16:12Z fix a bug in ExecutionRuntimeManager > Fix memory leak in ExecutionRuntimeManager > -- > > Key: EAGLE-1007 > URL: https://issues.apache.org/jira/browse/EAGLE-1007 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > Fix memory leak in ExecutionRuntimeManager > As equal method is not overrided in {{AbstractEnvironment}}, below return > statement has never been executed. > {code} > if (executionRuntimeCache.containsKey(environment)) { > return executionRuntimeCache.get(environment); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #897: [EAGLE-982] The log length has exceeded the limit of 4 MB ...
Github user asdf2014 commented on the issue: https://github.com/apache/eagle/pull/897 @jhsenjaliya Already done. --- 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 #908: [EAGLE-998]Add eagle csd
Github user chitin commented on a diff in the pull request: https://github.com/apache/eagle/pull/908#discussion_r111723827 --- Diff: eagle-external/eagle-cdh/src/aux/eagle-server.sh --- @@ -0,0 +1,135 @@ +#!/bin/bash --- End diff -- Thanks for your review. As I mentioned in /scripts/control.sh,"Use eagle.properties instead of eagle.conf, configFormat only support hadoop_xml,properties,gflags", CSD can't generate file end with ".conf", I can't find out better method to replace. --- 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-998) Add eagle csd
[ https://issues.apache.org/jira/browse/EAGLE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970902#comment-15970902 ] ASF GitHub Bot commented on EAGLE-998: -- Github user chitin commented on a diff in the pull request: https://github.com/apache/eagle/pull/908#discussion_r111723827 --- Diff: eagle-external/eagle-cdh/src/aux/eagle-server.sh --- @@ -0,0 +1,135 @@ +#!/bin/bash --- End diff -- Thanks for your review. As I mentioned in /scripts/control.sh,"Use eagle.properties instead of eagle.conf, configFormat only support hadoop_xml,properties,gflags", CSD can't generate file end with ".conf", I can't find out better method to replace. > Add eagle csd > - > > Key: EAGLE-998 > URL: https://issues.apache.org/jira/browse/EAGLE-998 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng >Priority: Minor > Fix For: v0.6.0 > > > Add eagle-cdh in eagle-external, users who use cdh can integrate eagle to > cloudera manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #897: [EAGLE-982] The log length has exceeded the limit of 4 MB ...
Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/897 @asdf2014 , can u please squash the commits ? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (EAGLE-992) HBase Naming that unify `Hbase` and `HBase` into `HBase`
[ https://issues.apache.org/jira/browse/EAGLE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-992: - Fix Version/s: (was: Future) v0.5.0 > HBase Naming that unify `Hbase` and `HBase` into `HBase` > > > Key: EAGLE-992 > URL: https://issues.apache.org/jira/browse/EAGLE-992 > Project: Eagle > Issue Type: Bug > Components: App::System Metric Monitor >Affects Versions: v0.4.0 >Reporter: Benedict Jin > Labels: patch > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > HBase Naming that unify `Hbase` and `HBase` into `HBase` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-998) Add eagle csd
[ https://issues.apache.org/jira/browse/EAGLE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970865#comment-15970865 ] ASF GitHub Bot commented on EAGLE-998: -- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/908 was just going through some PRs, so put some comments...pls take a look. > Add eagle csd > - > > Key: EAGLE-998 > URL: https://issues.apache.org/jira/browse/EAGLE-998 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng >Priority: Minor > Fix For: v0.6.0 > > > Add eagle-cdh in eagle-external, users who use cdh can integrate eagle to > cloudera manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #908: [EAGLE-998]Add eagle csd
Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/908 was just going through some PRs, so put some comments...pls take a look. --- 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-998) Add eagle csd
[ https://issues.apache.org/jira/browse/EAGLE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970863#comment-15970863 ] ASF GitHub Bot commented on EAGLE-998: -- Github user jhsenjaliya commented on a diff in the pull request: https://github.com/apache/eagle/pull/908#discussion_r111720746 --- Diff: eagle-external/eagle-cdh/src/aux/eagle-server.sh --- @@ -0,0 +1,135 @@ +#!/bin/bash --- End diff -- same with server.yml > Add eagle csd > - > > Key: EAGLE-998 > URL: https://issues.apache.org/jira/browse/EAGLE-998 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng >Priority: Minor > Fix For: v0.6.0 > > > Add eagle-cdh in eagle-external, users who use cdh can integrate eagle to > cloudera manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #908: [EAGLE-998]Add eagle csd
Github user jhsenjaliya commented on a diff in the pull request: https://github.com/apache/eagle/pull/908#discussion_r111720746 --- Diff: eagle-external/eagle-cdh/src/aux/eagle-server.sh --- @@ -0,0 +1,135 @@ +#!/bin/bash --- End diff -- same with server.yml --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (EAGLE-972) Eagle 0.5 release tasks checklist
[ https://issues.apache.org/jira/browse/EAGLE-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-972: - Summary: Eagle 0.5 release tasks checklist (was: Eagle 0.5 Release Tasks) > Eagle 0.5 release tasks checklist > - > > Key: EAGLE-972 > URL: https://issues.apache.org/jira/browse/EAGLE-972 > Project: Eagle > Issue Type: Task >Affects Versions: v0.5.0 >Reporter: Jayesh > Labels: release > Fix For: v0.5.0 > > > This ticket should include all the required tasks that needs to be complete > in order to release 0.5 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-972) Eagle 0.5 Release Tasks
[ https://issues.apache.org/jira/browse/EAGLE-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-972: - Summary: Eagle 0.5 Release Tasks (was: Create 0.5 Release) > Eagle 0.5 Release Tasks > --- > > Key: EAGLE-972 > URL: https://issues.apache.org/jira/browse/EAGLE-972 > Project: Eagle > Issue Type: Task >Affects Versions: v0.5.0 >Reporter: Jayesh > Labels: release > Fix For: v0.5.0 > > > This ticket should include all the required tasks that needs to be complete > in order to release 0.5 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-740) Fix eagle-query checkstyle warnings
[ https://issues.apache.org/jira/browse/EAGLE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970837#comment-15970837 ] ASF GitHub Bot commented on EAGLE-740: -- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/647 @haoch , do you need any help on reviewing this? @koone, Can you please rebase this PR ? Thanks > Fix eagle-query checkstyle warnings > --- > > Key: EAGLE-740 > URL: https://issues.apache.org/jira/browse/EAGLE-740 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: luokun >Assignee: luokun > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Fix checkstyle problems on eagle-query -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #647: [EAGLE-740]Fix eagle-query checkstyle warnings
Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/647 @haoch , do you need any help on reviewing this? @koone, Can you please rebase this PR ? Thanks --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (EAGLE-1004) Test branch-0.5 with apps on Dev/Staging environment
[ https://issues.apache.org/jira/browse/EAGLE-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-1004: -- Summary: Test branch-0.5 with apps on Dev/Staging environment (was: Test Eagle 0.5 on Dev/Staging environment) > Test branch-0.5 with apps on Dev/Staging environment > > > Key: EAGLE-1004 > URL: https://issues.apache.org/jira/browse/EAGLE-1004 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-1005) cut branch 0.5
Jayesh created EAGLE-1005: - Summary: cut branch 0.5 Key: EAGLE-1005 URL: https://issues.apache.org/jira/browse/EAGLE-1005 Project: Eagle Issue Type: Sub-task Reporter: Jayesh Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (EAGLE-1005) cut branch 0.5
[ https://issues.apache.org/jira/browse/EAGLE-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-1005. --- Resolution: Fixed branch-0.5 is created > cut branch 0.5 > -- > > Key: EAGLE-1005 > URL: https://issues.apache.org/jira/browse/EAGLE-1005 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh >Priority: Minor > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (EAGLE-1005) cut branch 0.5
[ https://issues.apache.org/jira/browse/EAGLE-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh reassigned EAGLE-1005: - Assignee: Jayesh > cut branch 0.5 > -- > > Key: EAGLE-1005 > URL: https://issues.apache.org/jira/browse/EAGLE-1005 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh >Assignee: Jayesh >Priority: Minor > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-942) Fetch running apps info with Yarn client
[ https://issues.apache.org/jira/browse/EAGLE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970831#comment-15970831 ] Jayesh commented on EAGLE-942: -- [~cltlfcjin], are you targeting this change for 0.5 ? do you think you will have this PR sometime this month? I think this would be very nice to have, to keep Apache Eagle efficient. Also it would be nice if you can remove those classes that was duplicated due to lack of yarn client. Thanks ! > Fetch running apps info with Yarn client > > > Key: EAGLE-942 > URL: https://issues.apache.org/jira/browse/EAGLE-942 > Project: Eagle > Issue Type: Improvement > Components: App::Job Performance Monitor >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Lantao Jin > Fix For: v0.5.0 > > > Since Hadoop upgrades to 2.7, /apps API returns much more data than before, > which burdens of the resource manager heavily. > The requirements: > * support multiple Hadoop version, at least 2.4 & 2.7 > * avoid the heavy burden on resource manager for per request -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-984) Potential null dereference in SimpleWindowCounter#poll()
[ https://issues.apache.org/jira/browse/EAGLE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970828#comment-15970828 ] Jayesh commented on EAGLE-984: -- [~ted_yu] would you be interested in providing fix for this ? > Potential null dereference in SimpleWindowCounter#poll() > > > Key: EAGLE-984 > URL: https://issues.apache.org/jira/browse/EAGLE-984 > Project: Eagle > Issue Type: Bug >Reporter: Ted Yu >Priority: Minor > Fix For: v0.5.0 > > > Here is related code: > {code} > public Tuple2poll() { > long oldestTimestamp = timeQueue.poll(); > Tuple2 pair = new Tuple2<>(oldestTimestamp, > counter.get(oldestTimestamp)); > {code} > We should check the return value from timeQueue.poll() before casting to long. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-984) Potential null dereference in SimpleWindowCounter#poll()
[ https://issues.apache.org/jira/browse/EAGLE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-984: - Fix Version/s: v0.5.0 > Potential null dereference in SimpleWindowCounter#poll() > > > Key: EAGLE-984 > URL: https://issues.apache.org/jira/browse/EAGLE-984 > Project: Eagle > Issue Type: Bug >Reporter: Ted Yu >Priority: Minor > Fix For: v0.5.0 > > > Here is related code: > {code} > public Tuple2poll() { > long oldestTimestamp = timeQueue.poll(); > Tuple2 pair = new Tuple2<>(oldestTimestamp, > counter.get(oldestTimestamp)); > {code} > We should check the return value from timeQueue.poll() before casting to long. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-958) ElasticSearch Alert Publisher
[ https://issues.apache.org/jira/browse/EAGLE-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970824#comment-15970824 ] Jayesh commented on EAGLE-958: -- [~haoch] are you planning to put this feature in 0.5 ?, can u please set v0.6.0 if not. I also have suggestion to convert this into generic feature to use ELK as cold storage ( since we will have that requirement on myside in near future), I have created this EP, Please let me know your thoughts: https://cwiki.apache.org/confluence/display/EAG/EP-19+Optional+Elastic+Search+integration+for+longer+retention > ElasticSearch Alert Publisher > - > > Key: EAGLE-958 > URL: https://issues.apache.org/jira/browse/EAGLE-958 > Project: Eagle > Issue Type: New Feature > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > ElasticSearch Alert Publisher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-581) Generate a build number when building the project.
[ https://issues.apache.org/jira/browse/EAGLE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970767#comment-15970767 ] ASF GitHub Bot commented on EAGLE-581: -- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/505 duplicate of #639 @pkuwm , can u please close this PR, Thanks > 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.15#6346)
[jira] [Updated] (EAGLE-969) duplicate email module
[ https://issues.apache.org/jira/browse/EAGLE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-969: - Fix Version/s: (was: v0.5.0) v0.6.0 > duplicate email module > -- > > Key: EAGLE-969 > URL: https://issues.apache.org/jira/browse/EAGLE-969 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Jayesh >Assignee: Jayesh > Fix For: v0.6.0 > > > I see duplicate email module {{org.apache.eagle.common.mail}} and > {{org.apache.eagle.alert.engine.publisher.email}} both has similar email > functionality related classes, not sure what is the reason, but it should be > merged, because it can create confusion letter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (EAGLE-988) Can't sort by Duration in Job Details Page
[ https://issues.apache.org/jira/browse/EAGLE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-988. -- Resolution: Fixed > Can't sort by Duration in Job Details Page > -- > > Key: EAGLE-988 > URL: https://issues.apache.org/jira/browse/EAGLE-988 > Project: Eagle > Issue Type: Bug > Components: App::Job Performance Monitor >Affects Versions: v0.5.0 >Reporter: Chang chen >Assignee: Jilin, Jiang > Fix For: v0.5.0 > > Attachments: 7864577558@chatroom_1491013604898_31.png > > > Steps to reproduce > # enter job detail list page > # click head of duration column -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #916: [MINOR] adding myself in developer list as a first ...
GitHub user jhsenjaliya opened a pull request: https://github.com/apache/eagle/pull/916 [MINOR] adding myself in developer list as a first commit You can merge this pull request into a Git repository by running: $ git pull https://github.com/jhsenjaliya/eagle add-me-in-developer-list Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/916.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 #916 commit 9a4e8e4f0b271f8b1ca502a49394d8d85bcf8821 Author: JayDate: 2017-04-17T03:58:53Z adding myself in developer list as a first commit --- 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-1004) Test Eagle 0.5 on Dev/Staging environment
Jayesh created EAGLE-1004: - Summary: Test Eagle 0.5 on Dev/Staging environment Key: EAGLE-1004 URL: https://issues.apache.org/jira/browse/EAGLE-1004 Project: Eagle Issue Type: Sub-task Reporter: Jayesh -- This message was sent by Atlassian JIRA (v6.3.15#6346)