Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Is there a way to avoid the RouteOnAttribute.Route parameter that NiFi puts after RouteOnAttribute processor?

avatar

I have a workflow that routes on attribute depending on a type, but it sets a RouteOnAttribute.Route param on a flow that has all of the filters, I don't want that, how can I prevent the processor to do this? Thanks

1 ACCEPTED SOLUTION

avatar
Master Mentor
@estefania rabadan

There is no processor configuration option to turn off what attributes a processor writes on to a FlowFile it processes. However, you can use the UpdateAttribute processor to remove attributes from FlowFiles.

Thanks,

Matt

View solution in original post

2 REPLIES 2

avatar
Master Mentor
@estefania rabadan

There is no processor configuration option to turn off what attributes a processor writes on to a FlowFile it processes. However, you can use the UpdateAttribute processor to remove attributes from FlowFiles.

Thanks,

Matt

avatar

thanks for the quick reply matt, i'll use that solution!