[jira] [Updated] (NIFI-16022) StandardResourceReferenceFactory cannot disambiguate between a file path and a multi-line Java comment

["David Handermann (Jira)" <ji...@apache.org>]

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

David Handermann updated NIFI-16022:
------------------------------------
    Fix Version/s: nifi-api-2.10.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> StandardResourceReferenceFactory cannot disambiguate between a file path and a multi-line Java comment
> ------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-16022
>                 URL: https://issues.apache.org/jira/browse/NIFI-16022
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: NiFi API
>            Reporter: Daniel Stieglitz
>            Assignee: Daniel Stieglitz
>            Priority: Major
>             Fix For: nifi-api-2.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Text which begins with  multi-line Java comment is misinterpreted by the StandardResourceReferenceFactory in method createResourceReference as a File when the ResourceType can be either FILE or TEXT.  A case in point is the bug discovered in NIFI-16021 where a JOLT transform with a leading multi-line Java comment e.g.
> {code:java}
> /*
>   This is a multi-line Java comment in a JOLT spec.
> */
> [
>   {
>     "operation": "shift",
>     "spec": {
>       "*": "&"
>     }
>   }
> ]{code}
> is misinterpreted as a file instead of text. The assumption made in this ticket is that although /*  is a valid Linux path, it is not common hence it should not be interpreted as a file path.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)