Eric, It might be overkill for you, but one thing you can consider doing if you'd like the ability to inspect flowfiles at various points in the flow for their attributes is use the SiteToSiteProvenanceReporting task to publish provenance data to another NiFi instance and load the JSON data from that into a store like Mongo or ElasticSearch. The attributes will be sent along with the provenance data, and you can query on time, processor, etc. as well.
On Fri, Mar 15, 2019 at 10:51 AM Joe Witt <[email protected]> wrote: > Eric, > > You could download the flowfile content using the provenance > click-to-content feature. You can see the attributes there too if you need > to recreate those. > > You can then ingest that file using GetFile or something on the other > system. > > There are additional built-in mechanisms that allow you to actually > serialize the flowfile itself but the process is more involved. > > We need to add a feature that lets you 'export as flowfile' and 'import > flowfile' right into a queue.. That would be ideal > > Thanks > > On Fri, Mar 15, 2019 at 10:44 AM Eric Chaves <[email protected]> wrote: > >> Hi fellows, >> >> I'd like to export a flow file from a queue running in production in >> order to import it into my local machine for development/troubleshooting? >> >> Also, is it possible to pick a single flow file in a given queue and >> process only it? >> >> Is there any way to do it? >> >> Best regards, >> >> Eric >> >
