Team,
I'd like to propose we remove the FlowFilePrioritizer [1] from the set
of first class extension points we support.
The background:
FlowFilePrioritizer implementations are used to compare flow files as
they are enqueued on a given connection in the flow. This in turn
means when flow files
I'm definitely a +1. In my experience, the way that most people think about
prioritizing data is
to either assign an absolute priority to a FlowFile and use the
PriorityAttributePrioritizer or to
use the FirstInFirstOut Prioritizer. Any number of processors can be used to
extract the the
'priori
+1. This seems like something we should provide options for (as we do),
but doesn't really need to be made / kept accessible for extension.
Brandon
On Fri, May 6, 2016 at 11:45 AM Mark Payne wrote:
> I'm definitely a +1. In my experience, the way that most people think
> about prioritizing dat
+1. I think the benefits of this move far outweigh the potential but unrealized
value of extensible prioritizers.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On May 6, 2016, at 9:49 AM, Brandon DeVries wrote
+1 as long as the existing 4 prioritizers remain as options. I have seen
people use all of them. I have also seen someone hack together what was
effectively a SmallestFileFirstPrioritizer and a
LargestFileFirstPrioritizer by using RouteOnAttribute on different
${fileSize} values. The use case wa
+1 for this. It also occurred to me that these are currently not shown in
the generated docs and only in the user guide.
Mike,
As far as sorting by size, do you think there is merit beyond the
PriorityAttributePrioritizer for this case? An update attribute "copying"
fileSize to "priority" shoul
I do think there is (a little) merit to a separate sort by file size, but
only because adding UpdateAttribute feels like a work around. Having it as
a native prioritizer should give people the impression that we thought
about it and consider it a valid use case.
-- Mike
On Mon, May 9, 2016 at 1
