Hello It is generally quite easy to enable for Property Descriptors which accept user supplied strings. And this is one that does seem like a candidate. Were you wanting it to look at a flowfile attribute to be the way of indicating the character set?
Thinking through this example the challenges that come to mind are: - What to do if the flow file doesn't have the charset indicated as an attribute? - What to do if the charset indicated by the flowfile attribute isn't supported? There are various cases to consider is all and your idea is a good one to pursue in my view. We had wanted to make it be an enumerated value at one point so users could only selected from known/valid charsets. But your idea is good too. Thanks Joe On Thu, May 12, 2016 at 2:58 PM, dale.chang13 <[email protected]> wrote: > What is the purpose of not allowing a Processor property to support > expression language? Not allowing a property such as "Character set" in the > ExtractText Processor is proving to be a hindrance. Would it affect NiFi > under the hood if it were otherwise? > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/Purpose-of-Disallowing-Attribute-Expression-tp10221.html > Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
