Hi,
Try using the replace text processor in "Literal Replace" mode for the Replacement Strategy setting. It's no obvious, but I have placed a single space in the Search Value setting.
![_mark__0-1621634057941.png _mark__0-1621634057941.png](https://community.cloudera.com/t5/image/serverpage/image-id/31261i71D87ACEA73F2961/image-size/medium?v=v2&px=400)
Alternatively, you could explore using an Avro schema to achieve this, and this links in nicely with your other question too. For example, given a flow file with the content (I'm using the GenerateFlowFile to create this):
Using this flow as a test:
![_mark__3-1621634539863.png _mark__3-1621634539863.png](https://community.cloudera.com/t5/image/serverpage/image-id/31264iE6FEF2005F778FD2/image-size/medium?v=v2&px=400)
I've created content in the GenerateFlowFile of:
![_mark__1-1621634278941.png _mark__1-1621634278941.png](https://community.cloudera.com/t5/image/serverpage/image-id/31262i885CEBC443E0BD99/image-size/medium?v=v2&px=400)
with an attribute called avro.schema:
![_mark__7-1621635075850.png _mark__7-1621635075850.png](https://community.cloudera.com/t5/image/serverpage/image-id/31268i14AF99739459B484/image-size/medium?v=v2&px=400)
Note the highlighted "name" attribute which defines the name you need on the output, and the "aliases" array value which is the input name value.
For reference, here's the GenerateFlowFile configuration:
![_mark__4-1621634613915.png _mark__4-1621634613915.png](https://community.cloudera.com/t5/image/serverpage/image-id/31265i25D78945F6539FD3/image-size/medium?v=v2&px=400)
The ConvertRecord has the following CSVReader configured:
![_mark__5-1621634692840.png _mark__5-1621634692840.png](https://community.cloudera.com/t5/image/serverpage/image-id/31266i102F472646F42093/image-size/medium?v=v2&px=400)
And using an otherwise normally configured CSVRecordSetWriter I get the following output:
![_mark__6-1621634753638.png _mark__6-1621634753638.png](https://community.cloudera.com/t5/image/serverpage/image-id/31267i45047F5A182E757E/image-size/medium?v=v2&px=400)
Also note that I have also changed the case using this approach, in fact you can rename the column to whatever you need.
I found working with Avro schemas a bit of a steep learning curve, but definitely worth the time investment. I mention this in particular as it compliments your other question about date formats very well.
Hope that helps