[
https://issues.apache.org/jira/browse/NIFI-14005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-14005:
----------------------------------
Description:
The goal of this new GetFileResource processor is to provide a way for a user
to inject a File Resource as a FlowFile with custom attributes. It means that
the processor would be able to specify a path to a file and its content would
be used as FlowFile's content. By leveraging the asset feature, it makes it
easy to load a test dataset as a FlowFile in a cloud native environment
(container based).
Alternatives that have been considered:
* GenerateFlowFile with a "Custom File/Content" property. However, a processor
being able to access the local file system needs to be associated with a
specific set of permissions and that would be a significant breaking change for
all users already using GenerateFlowFile processor where such permissions are
enforced.
* GetFile with some specific improvements. However, longer term we would
likely want to completely remove this processor and only have
ListFile/FetchFile. Beside, its configuration is overly complex for the
intended goal here.
was:
Add a property in GenerateFlowFile allowing the user to specify a local path to
an external file. If specified the content of the external file will be used as
content of the generated flow files.
This makes things easier compared to a GetFile for example. Besides, coupled
with the Asset feature, it makes it easy to load a test dataset as content for
GenerateFlowFile processor in a cloud native environment (container based).
Summary: New processor GetFileResource (was: Support Custom Content
from External File in GenerateFlowFile)
> New processor GetFileResource
> -----------------------------
>
> Key: NIFI-14005
> URL: https://issues.apache.org/jira/browse/NIFI-14005
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Minor
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The goal of this new GetFileResource processor is to provide a way for a user
> to inject a File Resource as a FlowFile with custom attributes. It means that
> the processor would be able to specify a path to a file and its content would
> be used as FlowFile's content. By leveraging the asset feature, it makes it
> easy to load a test dataset as a FlowFile in a cloud native environment
> (container based).
> Alternatives that have been considered:
> * GenerateFlowFile with a "Custom File/Content" property. However, a
> processor being able to access the local file system needs to be associated
> with a specific set of permissions and that would be a significant breaking
> change for all users already using GenerateFlowFile processor where such
> permissions are enforced.
> * GetFile with some specific improvements. However, longer term we would
> likely want to completely remove this processor and only have
> ListFile/FetchFile. Beside, its configuration is overly complex for the
> intended goal here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
