exceptionfactory commented on PR #10031: URL: https://github.com/apache/nifi/pull/10031#issuecomment-3308261365
> @exceptionfactory I support adding the extensibility for multi-document, record-oriented implementations, but I'm not sure what the best approach is yet. > > The name `Document` might not be the most suitable, as the processors can also handle binary data, which is more of a "Key-Value Store"-like function rather than a "Document Database" function. At the moment, however, I don't have a better name. > > I'm not sure what the "standard approach" is in NiFi for handling different types of inputs in a processor. For example, some processors (like PublishMQTT) can process both FlowFile content and a Record Reader, while other solutions implement these two functions in separate processors (e.g., the old ConsumeKafka and ConsumeKafkaRecord). > > Which one do you think is the correct way? Thanks for the reply. On further consideration, the current naming can work. As you noted, one strategy is to introduce new Processors with the `Record` suffix, and another approach is to introduce record-oriented handling as a strategy property. -- 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]
