[jira] [Commented] (EAGLE-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[
https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857436#comment-15857436
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ commented on the issue:
https://github.com/apache/eagle/pull/796
@wujinhu here is what I observed:
1. In site "sandbox", I have "alert engine" started. In storm UI, topology
is running as "HBaseAuditMonitor"
2.When run in Debug mode in Intellij, "server config" has "siteId =
testSite", "appId = HBaseAuditLog", and config context has "siteId = sandbox"
and "appId = ALERT_UNIT_TOPOLOGY_APP_SANDBOX".
Because server config has higher priority, these context info are
overridden.
By the way, could you explain a little bit on "There are a lot of
application.conf files in eagle. I think this is the root cause"?
Thanks and regards,
Da
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Application Framework
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle issue #796: [EAGLE-888] Application submitted to Storm is always shown...
Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/796 @wujinhu here is what I observed: 1. In site "sandbox", I have "alert engine" started. In storm UI, topology is running as "HBaseAuditMonitor" 2.When run in Debug mode in Intellij, "server config" has "siteId = testSite", "appId = HBaseAuditLog", and config context has "siteId = sandbox" and "appId = ALERT_UNIT_TOPOLOGY_APP_SANDBOX". Because server config has higher priority, these context info are overridden. By the way, could you explain a little bit on "There are a lot of application.conf files in eagle. I think this is the root cause"? Thanks and regards, Da --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[
https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857407#comment-15857407
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user wujinhu commented on the issue:
https://github.com/apache/eagle/pull/796
@DadanielZ
There are a lot of application.conf files in eagle. I think this is the
root cause.
Besides, I think server config has higher priority than generated
config(context)
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Application Framework
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle issue #796: [EAGLE-888] Application submitted to Storm is always shown...
Github user wujinhu commented on the issue: https://github.com/apache/eagle/pull/796 @DadanielZ There are a lot of application.conf files in eagle. I think this is the root cause. Besides, I think server config has higher priority than generated config(context) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-881) Url of scala-tools repository is no longer valid
[ https://issues.apache.org/jira/browse/EAGLE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857345#comment-15857345 ] ASF GitHub Bot commented on EAGLE-881: -- Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/795 @haoch this is for branch-0.4, which should be using jdk 1.7 to build. > Url of scala-tools repository is no longer valid > > > Key: EAGLE-881 > URL: https://issues.apache.org/jira/browse/EAGLE-881 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: DanielZhou > > After clear ~/.m2/repository, Maven build failed with error messages: > Failed to execute goal > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) > on project eagle-security-hive: Error resolving project artifact: Could not > transfer artifact org.pentaho:pentaho-aggdesigner-algorithm:pom:5.1.5-jhyde > from/to scala-tools.org (http://scala-tools.org/repo-releases): Received > fatal alert: protocol_version for project > org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde -> [Help 1] > Reason: > The URL of scala-tools repository provided in "eagle-parent" pom file is no > longer valid: http://scala-tools.org/repo-releases > It will redirects to some unknown blog and won't find related resources. > Solution: > Remove the repositories declaration of "Scala-Tools Maven2 Repository" from > "eagle-parent" pom file, so that maven can download them from default maven > repo. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #795: [EAGLE-881] Url of scala-tools repository is no longer val...
Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/795 @haoch this is for branch-0.4, which should be using jdk 1.7 to 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. ---
[jira] [Commented] (EAGLE-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[
https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857342#comment-15857342
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ commented on the issue:
https://github.com/apache/eagle/pull/796
@wujinhu yes, I find this when I start eagle from Intellij on mac.
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Application Framework
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle issue #796: [EAGLE-888] Application submitted to Storm is always shown...
Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/796 @wujinhu yes, I find this when I start eagle from Intellij on mac. --- 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 #796: [EAGLE-888] Application submitted to Storm is always shown...
Github user wujinhu commented on the issue: https://github.com/apache/eagle/pull/796 @DadanielZ Do you find this problem in your dev env? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[
https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857326#comment-15857326
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user wujinhu commented on the issue:
https://github.com/apache/eagle/pull/796
@DadanielZ Do you find this problem in your dev env?
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Application Framework
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-881) Url of scala-tools repository is no longer valid
[ https://issues.apache.org/jira/browse/EAGLE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857322#comment-15857322 ] ASF GitHub Bot commented on EAGLE-881: -- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/795 @DadanielZ eagle currently requires `jdk-1.8` to compile, why the build failed? > Url of scala-tools repository is no longer valid > > > Key: EAGLE-881 > URL: https://issues.apache.org/jira/browse/EAGLE-881 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: DanielZhou > > After clear ~/.m2/repository, Maven build failed with error messages: > Failed to execute goal > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) > on project eagle-security-hive: Error resolving project artifact: Could not > transfer artifact org.pentaho:pentaho-aggdesigner-algorithm:pom:5.1.5-jhyde > from/to scala-tools.org (http://scala-tools.org/repo-releases): Received > fatal alert: protocol_version for project > org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde -> [Help 1] > Reason: > The URL of scala-tools repository provided in "eagle-parent" pom file is no > longer valid: http://scala-tools.org/repo-releases > It will redirects to some unknown blog and won't find related resources. > Solution: > Remove the repositories declaration of "Scala-Tools Maven2 Repository" from > "eagle-parent" pom file, so that maven can download them from default maven > repo. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #795: [EAGLE-881] Url of scala-tools repository is no longer val...
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/795 @DadanielZ eagle currently requires `jdk-1.8` to compile, why the build failed? --- 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-872) Transform counter metric to rate metric
[ https://issues.apache.org/jira/browse/EAGLE-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857275#comment-15857275 ] ASF GitHub Bot commented on EAGLE-872: -- Github user r7raul1984 commented on the issue: https://github.com/apache/eagle/pull/783 @haoch If metric name endswith "count" , it will be converted to rate. > Transform counter metric to rate metric > --- > > Key: EAGLE-872 > URL: https://issues.apache.org/jira/browse/EAGLE-872 > Project: Eagle > Issue Type: Improvement >Reporter: JiJun Tang >Assignee: JiJun Tang > > Some metric like hbase hadoop.hbase.regionserver.server.totalrequestcount is > counter type(the value is always increasing).We will save the rate of change > of the value over a step period. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #783: [EAGLE-872] Transform counter metric to rate metric
Github user r7raul1984 commented on the issue: https://github.com/apache/eagle/pull/783 @haoch If metric name endswith "count" , it will be converted to rate. --- 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-872) Transform counter metric to rate metric
[ https://issues.apache.org/jira/browse/EAGLE-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857266#comment-15857266 ] ASF GitHub Bot commented on EAGLE-872: -- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/783 @r7raul1984 would you convert *all* counter metric to rate? > Transform counter metric to rate metric > --- > > Key: EAGLE-872 > URL: https://issues.apache.org/jira/browse/EAGLE-872 > Project: Eagle > Issue Type: Improvement >Reporter: JiJun Tang >Assignee: JiJun Tang > > Some metric like hbase hadoop.hbase.regionserver.server.totalrequestcount is > counter type(the value is always increasing).We will save the rate of change > of the value over a step period. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #783: [EAGLE-872] Transform counter metric to rate metric
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/783 @r7raul1984 would you convert *all* counter metric to rate? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[
https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857262#comment-15857262
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user haoch commented on the issue:
https://github.com/apache/eagle/pull/796
@wujinhu please help review the PR about app/server config changes
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Application Framework
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle issue #796: [EAGLE-888] Application submitted to Storm is always shown...
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/796 @wujinhu please help review the PR about app/server config changes --- 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-882) Stream leaf RunningQueueAPIEntity into Kafka for queue monitoring
[ https://issues.apache.org/jira/browse/EAGLE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen resolved EAGLE-882. - Resolution: Resolved Fix Version/s: v0.5.0 > Stream leaf RunningQueueAPIEntity into Kafka for queue monitoring > - > > Key: EAGLE-882 > URL: https://issues.apache.org/jira/browse/EAGLE-882 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > Stream RunningQueueAPIEntity into Kafka for queue monitoring. > Sample policy: when leaf queue's resource usage hit any limit(max limit or > user limit) over 10 mins, then trigger the alert. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[
https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857200#comment-15857200
]
ASF GitHub Bot commented on EAGLE-888:
--
GitHub user DadanielZ opened a pull request:
https://github.com/apache/eagle/pull/796
[EAGLE-888] Application submitted to Storm is always shown as
“HBaseAuditLogApp”
Reordered the "withFallBack" function to get user's topology configuration
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DadanielZ/eagle EAGLE-888
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/eagle/pull/796.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 #796
commit 0cc2167e2f807fcd59e220916b4e0cdcc76e2563
Author: DadanielZ
Date: 2017-02-08T01:35:34Z
EAGLE-888 Application submitted to Storm is always shown as
“HBaseAuditLogApp”
Reordered the "withFallBack" function to get user's topology configuration
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Application Framework
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle pull request #796: [EAGLE-888] Application submitted to Storm is alway...
GitHub user DadanielZ opened a pull request: https://github.com/apache/eagle/pull/796 [EAGLE-888] Application submitted to Storm is always shown as âHBaseAuditLogAppâ Reordered the "withFallBack" function to get user's topology configuration You can merge this pull request into a Git repository by running: $ git pull https://github.com/DadanielZ/eagle EAGLE-888 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/796.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 #796 commit 0cc2167e2f807fcd59e220916b4e0cdcc76e2563 Author: DadanielZ Date: 2017-02-08T01:35:34Z EAGLE-888 Application submitted to Storm is always shown as âHBaseAuditLogAppâ Reordered the "withFallBack" function to get user's topology 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-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
DanielZhou created EAGLE-888:
Summary: Application submitted to Storm is always shown as
“HBaseAuditLogApp”
Key: EAGLE-888
URL: https://issues.apache.org/jira/browse/EAGLE-888
Project: Eagle
Issue Type: Bug
Components: Application Framework
Affects Versions: v0.5.0
Reporter: DanielZhou
Assignee: DanielZhou
*Issue*:
Steps to reproduce:
- Started application from Eagle UI (eg: alert engine)
- Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
*Reason*:
In the constructor function of class *"ApplicationAction"*:
{quote}
this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
.withFallback(serverConfig)
.withFallback(ConfigFactory.parseMap(metadata.getContext()))
{quote}
According to the java doc of
[withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
:
{quote}
Returns a new value computed by merging this value with another, with keys in
this value "winning" over the other one.
{quote}
As a result, "serverConfig" will win over
"ConfigFactory.parseMap(metadata.getContext())" which means the default
"ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
will win over the meta data of the user's topology.
*Fix*:
Change the order of "withFallBack" to:
{quote}
this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
.withFallback(ConfigFactory.parseMap(metadata.getContext()))
.withFallback(serverConfig)
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-881) Url of scala-tools repository is no longer valid
[ https://issues.apache.org/jira/browse/EAGLE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856352#comment-15856352 ] ASF GitHub Bot commented on EAGLE-881: -- Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/795 Build failed because Jenkins is using jdk1.8 but not jdk1.7: [ERROR] error: error while loading CharSequence, class file '/usr/local/asfpackages/java/jdk1.8.0_102/jre/lib/rt.jar(java/lang/CharSequence.class)' is broken [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 10) [ERROR] error: error while loading AnnotatedElement, class file '/usr/local/asfpackages/java/jdk1.8.0_102/jre/lib/rt.jar(java/lang/reflect/AnnotatedElement.class)' is broken [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 76) [ERROR] error: error while loading ConcurrentMap, class file '/usr/local/asfpackages/java/jdk1.8.0_102/jre/lib/rt.jar(java/util/concurrent/ConcurrentMap.class)' is broken > Url of scala-tools repository is no longer valid > > > Key: EAGLE-881 > URL: https://issues.apache.org/jira/browse/EAGLE-881 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: DanielZhou > > After clear ~/.m2/repository, Maven build failed with error messages: > Failed to execute goal > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) > on project eagle-security-hive: Error resolving project artifact: Could not > transfer artifact org.pentaho:pentaho-aggdesigner-algorithm:pom:5.1.5-jhyde > from/to scala-tools.org (http://scala-tools.org/repo-releases): Received > fatal alert: protocol_version for project > org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde -> [Help 1] > Reason: > The URL of scala-tools repository provided in "eagle-parent" pom file is no > longer valid: http://scala-tools.org/repo-releases > It will redirects to some unknown blog and won't find related resources. > Solution: > Remove the repositories declaration of "Scala-Tools Maven2 Repository" from > "eagle-parent" pom file, so that maven can download them from default maven > repo. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #795: [EAGLE-881] Url of scala-tools repository is no longer val...
Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/795 Build failed because Jenkins is using jdk1.8 but not jdk1.7: [ERROR] error: error while loading CharSequence, class file '/usr/local/asfpackages/java/jdk1.8.0_102/jre/lib/rt.jar(java/lang/CharSequence.class)' is broken [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 10) [ERROR] error: error while loading AnnotatedElement, class file '/usr/local/asfpackages/java/jdk1.8.0_102/jre/lib/rt.jar(java/lang/reflect/AnnotatedElement.class)' is broken [INFO] (class java.lang.RuntimeException/bad constant pool tag 18 at byte 76) [ERROR] error: error while loading ConcurrentMap, class file '/usr/local/asfpackages/java/jdk1.8.0_102/jre/lib/rt.jar(java/util/concurrent/ConcurrentMap.class)' is broken --- 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-867) Show real time current server time aside global timepicker
[ https://issues.apache.org/jira/browse/EAGLE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jilin, Jiang resolved EAGLE-867. Resolution: Fixed > Show real time current server time aside global timepicker > -- > > Key: EAGLE-867 > URL: https://issues.apache.org/jira/browse/EAGLE-867 > Project: Eagle > Issue Type: Sub-task > Components: Hadoop JMX Monitor >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Jilin, Jiang > Fix For: v0.5.0 > > > Show current server time aside global timepicker -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #794: Eagle-884 JPM support queue trend view
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/794 --- 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 #794: Eagle-884 JPM support queue trend view
Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/794 look good to me --- 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. ---
