[ 
https://issues.apache.org/jira/browse/AMBARI-24214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527018#comment-16527018
 ] 

Hudson commented on AMBARI-24214:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9550 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9550/])
AMBARI-24214. Log Search: config api validator in Configuration Editor (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e07b99f999154fb9ccdeae3e2875fcd79fbe04dc])
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerFilterGrok.java


> Log Search: config api validator in Configuration Editor throws 
> "IllegalArgumentException"
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-24214
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24214
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch
>    Affects Versions: 2.7.0
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>            Priority: Major
>              Labels: pull-request-available, quickfix
>             Fix For: 2.7.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 1. Login to logsearch portal
> 2. Navigate to Configuration Editor
> 3. Select a valid component in the Validator drop down, and Type in some 
> sample test data in the Sample Data text area, click Test. This should 
> validate the sample data and show valid response to the user, but throws a 
> illegalArgumentException.
> {code:java}
> java.lang.IllegalArgumentException: Error validating shipper config:
> [ConstraintViolationImpl{interpolatedMessage='may not be null', 
> propertyPath=filter[3].multilinePattern, rootBeanClass=class 
> org.apache.ambari.logsearch.model.common.LSServerInputConfig, 
> messageTemplate='{javax.validation.constraints.NotNull.message}'}]
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to