[
https://issues.apache.org/jira/browse/NIFI-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Atwood updated NIFI-8971:
--------------------------------
Description:
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.
was:I see in MergeContent a comment about adding legacy attributes
'nf.file.name','nf.file.path', and 'content-type'. As expressed in dev mailing
list, goal for 2.0 release is removing technical debt which I think removing
support for those attributes from MergeContent counts as.
> 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: Wish
> Reporter: Andrew Atwood
> Priority: Minor
> Labels: beginner
>
> 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.3.4#803005)
