[
https://issues.apache.org/jira/browse/NIFI-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148081#comment-17148081
]
Mark Payne commented on NIFI-7579:
----------------------------------
I'm not sure that we should introduce another processor just to avoid needing
to connect a List/Fetch pair of processors. The pattern of GetXYZ is an older
pattern and most of the newer processors that are responsible for gathering
files/blobs of data and the like tend to follow the List/Fetch pattern. This
pattern has proven to provide many advantages over the Get pattern. It allows
for easy and powerful filtering of data before fetching the data. It separates
the concerns of listing and maintaining state about what's been seen from
actually gathering data. It provides a very powerful mechanism for distributing
the data and processing load across the cluster. It makes it far easier to
handle flows that are more batch-oriented, with the introduction of NIFI-7476.
I would be a -1 on adding a new processor just to avoid needing to connect an
upstream List processor. It would mean additional code that must be maintained
and would lead to confusion for users when trying to determine which Processor
they need, especially for newer users.
> Create a GetS3Object Processor
> ------------------------------
>
> Key: NIFI-7579
> URL: https://issues.apache.org/jira/browse/NIFI-7579
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: ArpStorm1
> Assignee: YoungGyu Chun
> Priority: Major
>
> Sometimes the client needs to get only specific object or a subset of objects
> from its bucket. Now, the only way to do it is using ListS3 Processor and
> after that using FetchS3Object processor. Creating a GetS3Object processor
> for such cases can be greatÂ
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
