[
https://issues.apache.org/jira/browse/NIFI-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Bunth updated NIFI-7643:
------------------------------
Description:
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.
was:
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.
> 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: Major
>
> 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)
