[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=15878877#comment-15878877
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ commented on the issue:
https://github.com/apache/eagle/pull/796
Issues resolved, hence closing it.
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-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=15878878#comment-15878878
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ closed the pull request at:
https://github.com/apache/eagle/pull/796
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-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=15877718#comment-15877718
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user haoch commented on the issue:
https://github.com/apache/eagle/pull/796
@DadanielZ is this PR still valid?
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-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=15871024#comment-15871024
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ commented on the issue:
https://github.com/apache/eagle/pull/796
@qingwen220 sure, will do it.
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-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=15869053#comment-15869053
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user qingwen220 commented on the issue:
https://github.com/apache/eagle/pull/796
@DadanielZ Could you help to fix it? I have a ticket here
https://issues.apache.org/jira/browse/EAGLE-902
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-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=15863877#comment-15863877
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ commented on the issue:
https://github.com/apache/eagle/pull/796
@qingwen220 Got it.. When will we add this module and what is the target
release date for Eagle 0.5?
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-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=15863203#comment-15863203
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user qingwen220 commented on the issue:
https://github.com/apache/eagle/pull/796
Hi @DadanielZ,
We have not added this module into Eagle server. So the service loader
cannot detect it.
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-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=15861748#comment-15861748
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ commented on the issue:
https://github.com/apache/eagle/pull/796
@wujinhu thanks 👍 , this issue is solved.
But I come up with another one when tring to view the alerts from UI:
After configuring the "application-debug.conf" properly with *"jdbc"* as
the storage type, I started eagle from Intellij successfully and started
alert-engine and hdfsAuditLogApp smoothly, then I created a hdfs policy.
I saw alerts are generated and saved in my mysql database.
But when I tried to view the alerts from UI, ERROR occurs:
~~~
ERROR [2017-02-10 01:19:40,433]
org.apache.eagle.service.generic.GenericEntityServiceResource: unknown storage
type: jdbc, support: [hbase]
! org.apache.eagle.storage.exception.IllegalDataStorageTypeException:
unknown storage type: jdbc, support: [hbase]
~~~
During debugging I see `storageServiceProviders` only contains
`hBaseStorage`, but no `jdbcStorage`. Could you tell me the reason or give me a
hint on which module to look into?
Thanks and regards,
Da
Here is the configuration file I used:
~~~
# 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.
# -
# Eagle REST Web Service Configuration
# -
service {
env = "testing"
host = "localhost"
port = 9090
username = "admin"
password = "secret"
readTimeOutSeconds = 60
context = "/rest"
timezone = "UTC"
}
zookeeper {
zkQuorum = "localhost:2181"
zkSessionTimeoutMs : 15000
zkRetryTimes : 3
zkRetryInterval : 2
}
# -
# Eagle Deep Storage Configuration
# -
storage {
type = "jdbc"
jdbc {
adapter = "mysql"
username = "root"
password = root
database = eagle
connectionUrl = "jdbc:mysql://localhost:3306/eagle"
connectionProps = "encoding=UTF-8"
driverClass = "com.mysql.jdbc.Driver"
connectionMax = 8
}
}
# -
# Eagle Metadata Store Configuration
# -
metadata {
store = "org.apache.eagle.metadata.store.jdbc.JDBCMetadataStore"
jdbc {
username = root
password = root
driverClassName = com.mysql.jdbc.Driver
database = "eagle"
connection = "jdbc:mysql://localhost:3306/eagle?user=root"
}
}
# -
# Eagle Application Configuration
# -
application {
stream {
provider = org.apache.eagle.app.messaging.KafkaStreamProvider
}
storm {
nimbusHost = "localhost"
nimbusThriftPort = 6627
}
updateStatus: {
initialDelay: 10
period: 10
}
healthCheck {
initialDelay = 30
period = 60
publisher {
publisherImpl =
org.apache.eagle.app.service.impl.ApplicationHealthCheckEmailPublisher
dailySendHour = 11
mail.smtp.host = "mail.host.com"
mail.smtp.port = 25
mail.smtp.recipients = "some...@email.com"
mail.smtp.subject = "Eagle Application Health Check"
mail.smtp.template = "HealthCheckTemplate.vm"
}
}
mailService {
mailSmtpServer = "",
mailSmtpPort = 25,
mailSmtpAuth = "false"
//mailSmtpConn = "plaintext",
//mailSmtpUsername = ""
//mailSmtpPassword = ""
//mailSmtpDebug = false
}
dailyJobReport {
reportHourTime: 1
reportPeriodInHour: 12
numTopUsers : 10
jobOvertimeLimitInHour: 6
su
[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=15858832#comment-15858832
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user wujinhu commented on the issue:
https://github.com/apache/eagle/pull/796
@DadanielZ I think you can add application-debug.conf to
eagle-server/src/test/resources/ if you run Class ServerDebug. Pls have a try.
Thanks.
> 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-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=15858580#comment-15858580
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ commented on the issue:
https://github.com/apache/eagle/pull/796
@wujinhu I see, so this only happens in dev env. Since "Typesafe Config"
is loading all "applicaiton.conf" in the classPath, parameters like "siteId",
"appId",etc are preloaded in "server config".
Is there a good way to solve this issue? Or I have to update all
"application.conf" files in the maven project manually?
> 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-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=15857734#comment-15857734
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user wujinhu commented on the issue:
https://github.com/apache/eagle/pull/796
IMO, "server config" has "siteId = testSite", "appId = HBaseAuditLog" may
be wrong. It should not contains these. I mean wrong application.conf has been
loaded probably.
> 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-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)
[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)
[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)
[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-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)
[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)
