You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Yolanda M. Davis (JIRA)" <ji...@apache.org> on 2016/07/18 23:31:20 UTC

[jira] [Updated] (NIFI-2310) Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters

     [ https://issues.apache.org/jira/browse/NIFI-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yolanda M. Davis updated NIFI-2310:
-----------------------------------
    Summary: Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters  (was: Shiftr Transform in JoltTransformProcessor Does Not Support Escaping Special Characters)

> Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters
> --------------------------------------------------------------------------------------------
>
>                 Key: NIFI-2310
>                 URL: https://issues.apache.org/jira/browse/NIFI-2310
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.0.0
>            Reporter: Yolanda M. Davis
>            Assignee: Yolanda M. Davis
>             Fix For: 1.0.0
>
>
> The following jolt spec failed to pass the validation check in JoltTransformJSON:
>     {
>       "\\@context": {
>         "name": "&1.Name",
>         "ingredient": "&1.Inputs",
>         "yield": "\\@context.Makes",
>         "*": "&1.&"
>       },
>       "name": "Name",
>       "ingredient": "Inputs",
>       "yield": "Makes",
>       "*": "&"
>     }
> The reason is the double backslash to escape '@' which should be supported to identify literal characters.
> Upgrading to Jolt version 0.0.21 should resolve this problem since it was fixed in that release.



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