exceptionfactory commented on PR #7122: URL: https://github.com/apache/nifi/pull/7122#issuecomment-1600758257
> Thanks a ton @exceptionfactory for reviewing the PR and implementing the fixes. I think we are good with all changes as suggested. But I had a question though on QueryAzureDataExplorer. Since it mandatorily requires a flow file to query into ADX, can this processor become a starting point of a flow where we query into ADX using input query and write the output to a file or some other output processor? You're welcome, and thanks for the follow-up @tanmaya-panda1. Regarding the required input FlowFile, you are right that the updated approach changes the behavior to require some other starting point Processor, such as GenerateFlowFile, as an input to QueryAzureDataExplorer. This behavior could be restored, but I wanted to clarify the intended use case first. Other "source" Processors, such as the List Processors, use state tracking to provide a query approach that only brings in new information. Without that tracking in this Processor, it would be necessary to right a query with a relative boundary, or using NiFi Expression Language to compute the current time, for example. The same result could be achieved using `GenerateFlowFile` in front of this Processor, but I understand that it introduces an additional step in the data flow. If you can provide some additional details on how you expected to use this Processor as a standalone source, that would be helpful in determining the best path forward. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
