You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2015/11/18 21:19:11 UTC

[jira] [Commented] (NIFI-1189) SplitJSON validation check fails in a weird way

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

Aldrin Piri commented on NIFI-1189:
-----------------------------------

That error is certainly no good.

Your usage is a little off for the processor.  As a note, I think you are looking for just EvaluateJsonPath to get an associated element from the overall object.  SplitJson is meant for List/Array elements to be broken into sub elements.

> SplitJSON validation check fails in a weird way
> -----------------------------------------------
>
>                 Key: NIFI-1189
>                 URL: https://issues.apache.org/jira/browse/NIFI-1189
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Joseph Percivall
>            Priority: Minor
>
> I am attempting to use SplitJSON to extract the controller status elements received by "Get"ing http://localhost:8080/nifi-api/controller/status. The JSONPath needed for this should be "$.controllerStatus." and has been tested correct using this site [1] and data [2].
> When I attempt to set that as the JSONPath expression the processor is marked invalid with this explanation:
> " is invalid because Failed to run validation due to java.lang.StringOutOfBoundsException: String index out of range: 19 
> [1] https://jsonpath.curiousconcept.com/
> [2] {"revision":{"clientId":"6584c7eb-b84b-4d0a-85e3-2f41e92a02bc"},"controllerStatus":{"activeThreadCount":0,"queued":"0 / 0 bytes","hasPendingAccounts":false,"runningCount":0,"stoppedCount":5,"invalidCount":1,"disabledCount":0,"activeRemotePortCount":0,"inactiveRemotePortCount":0,"bulletins":[],"controllerServiceBulletins":[],"reportingTaskBulletins":[]}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)