You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Aakash Chauhan (Jira)" <ji...@apache.org> on 2022/04/27 19:57:00 UTC

[jira] [Assigned] (NIFI-8971) For NiFi 2.0, remove support for legacy attributes

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

Aakash Chauhan reassigned NIFI-8971:
------------------------------------

    Assignee: Aakash Chauhan

> For NiFi 2.0, remove support for legacy attributes
> --------------------------------------------------
>
>                 Key: NIFI-8971
>                 URL: https://issues.apache.org/jira/browse/NIFI-8971
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Andrew Atwood
>            Assignee: Aakash Chauhan
>            Priority: Minor
>              Labels: beginner
>             Fix For: 2.0.0
>
>
> I believe the following attributes are considered legacy and only maintained for backwards compatibility. As part of removing technical debt in 2.0 release, support for them should be removed.
>  * nf.file.name
>  * nf.file.path
>  * content-encoding
>  * content-type
> I found handling for them in MergeContent, UnpackContent, and ListenHTTPServlet. There is also handling for them in PostHTTP, but that processor is deprecated and planned to be removed in 2.0 release.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)