You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Tamás Bunth (Jira)" <ji...@apache.org> on 2020/07/16 13:42:00 UTC
[jira] [Commented] (NIFI-7643) Unpackcontent writing absolute path
property does not make sense
[ https://issues.apache.org/jira/browse/NIFI-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159222#comment-17159222 ]
Tamás Bunth commented on NIFI-7643:
-----------------------------------
Setting version to Nifi 2.0 because of API change.
> Unpackcontent writing absolute path property does not make sense
> ----------------------------------------------------------------
>
> Key: NIFI-7643
> URL: https://issues.apache.org/jira/browse/NIFI-7643
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Tamás Bunth
> Priority: Minor
> Fix For: 2.0.0
>
>
> Steps to reproduce:
> # Create a tar or zip file with some arbitrary content in its root. The bug occurs only when using these two formats.
> # Create a flow: GetFile -> UnpackContent -> LogAttribute.
> # Set GetFile to fetch the compressed test file from the file system. Set UnpackContent to use the appropriate format.
> Unpackcontent writes an attribute "file.absolutePath" which is currently the relative path of the unpacked content concatenated with the current working directory (where Nifi has been run).
> E.g. if I unpacked a file with relative path "egg/ham.txt" and I run Nifi from "/usr/bin", "file.absolutePath" would be "/usr/bin/egg/ham.txt".
> In my opinion, "absolute path" does not make much sense in this context. I suggest removing it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)