[
https://issues.apache.org/jira/browse/EAGLE-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15794674#comment-15794674
]
ASF GitHub Bot commented on EAGLE-797:
--------------------------------------
Github user haoch commented on a diff in the pull request:
https://github.com/apache/eagle/pull/762#discussion_r94381184
--- Diff: eagle-jpm/pom.xml ---
@@ -42,6 +42,7 @@
<module>eagle-jpm-web</module>
<module>eagle-jpm-service</module>
<module>eagle-jpm-aggregation</module>
+ <module>eagle-jpm-analysis</module>
--- End diff --
`analyzer`
> MRJobParser fetchjobConfig should continue when parse throw exception
> ---------------------------------------------------------------------
>
> Key: EAGLE-797
> URL: https://issues.apache.org/jira/browse/EAGLE-797
> Project: Eagle
> Issue Type: Improvement
> Reporter: JiJun Tang
> Assignee: luokun
> Priority: Minor
>
> {code:xml}
> <property>
> <name>hadoop.security.group.mapping.ldap.search.filter.user</name>
> <value>(&(objectClass=user)(sAMAccountName={0}))</value>
> <source>core-default.xml</source>
>
> <source>viewfs://xxxxx/user/xxx/.staging/job_1479206441898_30784/job.xml</source>
> </property>
> {code}
> When DocumentBuilder parse xml like above which have some unescape char like
> & will throw exception.That will cause whole fetchjobconfig fail.So I think
> should catch the exception and continue to parse .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
