You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2020/01/30 03:25:57 UTC

[GitHub] [nifi] YolandaMDavis commented on issue #4020: NIFI-7054: Add RecordSinkServiceLookup for dynamic sink routing

YolandaMDavis commented on issue #4020: NIFI-7054: Add RecordSinkServiceLookup for dynamic sink routing
URL: https://github.com/apache/nifi/pull/4020#issuecomment-580066802
 
 
   @mattyb149 I was able to test this by using a custom scripted processor which consumed records and sent them to the lookup service, using flow file attributes to store info for record.sink.name in each file.  This worked well, however in looking at QueryNiFiReportingTask it doesn't seem as if it could leverage this as easily (because there is a discrete set of attributes that are sent to the sink from that task). I'm wondering if that can be enhanced in the context of this work as well to ensure that a record.sink.name can some how be propagated from that task?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services