Michael Moser wrote > NIFI-1077 [1] has discussed this a bit in the past, when > ConvertCharacterSet was improved to support expression language. A JIRA > ticket is needed to spur action on these requests. > > An interesting case to help this would be to improve the IdentifyMimeType > processor to detect character encodings on text data. Apache Tika can do > it with an EncodingDetector [2], so why not take advantage since it's > already part of IdentifyMimeType? I think this would be cool so I wrote > NIFI-1874 [3]. > > [1] - https://issues.apache.org/jira/browse/NIFI-1077 > [2] - > https://tika.apache.org/1.12/api/org/apache/tika/detect/EncodingDetector.html > [3] - https://issues.apache.org/jira/browse/NIFI-1874
Funny enough, my company's backlog says that we would need to have a character set detection processor. However, I just got assigned a bunch of tasks for our next sprint. I'd love to have either my colleague or I take up JIRA 1874, but we'll have to wait until the sprint after -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Purpose-of-Disallowing-Attribute-Expression-tp10221p10234.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
