exceptionfactory commented on PR #11583: URL: https://github.com/apache/nifi/pull/11583#issuecomment-5381661676
Thanks for the reply! The use case makes sense, but I'm not sure if it fits as a generalized capability for the project. As the additional details highlights, there are differences in Base64 alphabets, depending on the encoding style. Although this could be handled through additional configuration properties, this introduces another level of complexity. The detection strategy is notable, highlighting the challenges of attempting to infer Base64 status based on partial content or entire content. Apache Tika supports a variety of content detection strategies, although it does not appear to have anything out of the box for Base64 detection. Base64 detection can also be tuned if the content follows a standard pattern, which may be more reliable and efficient that general strategies. For all of these reasons, it seems like this would be better left as a custom Processor as opposed to included with the project for now. Another option is publishing it directly as a NAR to Maven Central, which could provide opportunity for additional use and feedback. -- 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]
