Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/2966
> we don't want to change recordField.getFieldName() - that is the NiFi
class and has nothing to do with Avro. We really want to avoid enforcing any
Avro naming peculiarities on NiFi - we should only enforce them for Avro, so I
think the AvroTypeUtil is the right place to put this.
Yeah totally agree here.
I didn't change ``recordField.getFieldName()``, I just wrapped it, in
``AvroTypeUtil``, to ensure the name is normalized. My concern was more about
methods like ``lookupField`` where we assign the field name to the record field
object. Just want to ensure that this pair/map is not used outside of the
``AvroTypeUtil`` where we would try to access the record field object with a
non-normalized field name. Does that make sense?
---
