[
https://issues.apache.org/jira/browse/NIFI-10245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Wise updated NIFI-10245:
-----------------------------
Description:
We're current processing data which arrives with "None" in place of empty/null
values. Since we don't have a use for those, we'd prefer to drop them prior to
JSON conversion. Because the current implementation doesn't include
StrReplace, we have to use a slower ReplaceText processor to do this.
ParseEnum is also still missing, although I believe that there's already a
ticket for that (NIFI-8140).
was:
We're current processing data which arrives with "None" in place of empty/null
values. Since we don't have a use for those, we'd prefer to drop them prior to
JSON conversion. Because the current implementation doesn't include
StrReplace, we have to use a slower ReplaceText processor to do this.
ParseEnum is also still missing, although I believe that there's already a
ticket for that.
> Implement SuperCSV's StrReplace function in the ValidateCsv Processor
> ---------------------------------------------------------------------
>
> Key: NIFI-10245
> URL: https://issues.apache.org/jira/browse/NIFI-10245
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: John Wise
> Priority: Trivial
> Labels: supercsv
>
> We're current processing data which arrives with "None" in place of
> empty/null values. Since we don't have a use for those, we'd prefer to drop
> them prior to JSON conversion. Because the current implementation doesn't
> include StrReplace, we have to use a slower ReplaceText processor to do this.
> ParseEnum is also still missing, although I believe that there's already a
> ticket for that (NIFI-8140).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
