[
https://issues.apache.org/jira/browse/NIFI-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582147#comment-14582147
]
Aldrin Piri commented on NIFI-487:
----------------------------------
The problem seemed to stem from control characters. As seen in the tweet and
the associated test, the issue in question was 0x7F (Delete)
> JsonPath processors can mark valid JSON as invalid
> --------------------------------------------------
>
> Key: NIFI-487
> URL: https://issues.apache.org/jira/browse/NIFI-487
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
> Fix For: 0.2.0
>
> Attachments:
> 0001-NIFI-487-Changing-the-default-JSON-provider-from-Sma.patch, tweet.json
>
>
> By default, all processors extending AbstractJsonPathProcessor can mark valid
> JSON as invalid by default configuration from the JsonPath library being used
> due to a bug in the backing JsonPath library used for evaluating JSON.
> By default, the processor is configured with the JSONParser.MODE_RFC4627.
> However, for the attached file, despite being valid according to the spec, is
> marked as invalid, when encountering the & in the string (US & Canada).
> One way around the library issue, would be allowing the specification of
> parse mode. Evaluating the same file for MODE_PERMISSIVE, allowed the file
> to be properly processed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
