You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2026/06/02 15:13:00 UTC

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

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

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

> StandardResourceReferenceFactory cannot disambiguate between a file path and a single line Java comment
> -------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-15982
>                 URL: https://issues.apache.org/jira/browse/NIFI-15982
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: NiFi API
>            Reporter: Daniel Stieglitz
>            Assignee: Daniel Stieglitz
>            Priority: Major
>             Fix For: nifi-api-2.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Text which begins with two forward slashes 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-15975 where a JSLT transform with a leading single line Java comment e.g.
> {code:java}
> // This is a single line comment in JSLT
> {
>        "id": .userId,
>        "name": .firstName
> }
> {code}
> is misinterpreted as a file instead of text. The assumption made in this ticket is that two forward slashes although is a valid Linux path, is not common hence it should not be interpreted as a file path.
>  



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