Once the split is made for each you can now create separate branches (data flows) add additional processors that needed to prepare each type for insertion. Next you similarly split the flow for other types TXT, AVRO, etc, and then one for unmatched type.
This would create a "csv" route which you would then direct downstream the flow you created. To improve your flow you would add RouteOnAttribute to check the file name ends in CSV. Another new common example would be to get the files from Amazon S3.Īfter the top of the flow where files arrive inbound, it is common to create a single flow with a single branch for a specific use case. Another example is using getFile/ListFile/etc at the top of a flow to read a directory. For example you an create an API with HandleHttpRequest/HandleHttpResponse to accept a post of a file. This is a common use case for nifi to create a data flow that is a single entry point for data files of different expected types up to an including all types.
0 kommentar(er)
