Hello, I would like to use the existing ScrollElasticsearchHttp to perform a search that returns a potentially large number of hits. The parameters of the search need to reference one or more flow file attributes.
Looking at the source code for this processor it appears that the QUERY property supports EL with flow file attributes. Furthermore, the documentation for the FAILURE relationship notes that only incoming flow files will be routed to failure. So it seems clear that this processor was designed to allow input flow files. Unfortunately though, the processor also has been annotated with INPUT_FORBIDDEN so I can’t use as is. I assume that there is a good reason for forbidding input here. Before I go and try to implement a custom processor that does what I want, I’d like to know if some hidden problem awaits me. Can someone clarify why this processor forbids input, and what problems I might expect if I try to circumvent this limitation? Thanks - Tim Sent from my iPhone
