[NIFI-1938] Investigate renaming replace expression language method

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 0.6.1
• Component/s: Core Framework
• Labels: expression-language
• Assignee: Unassigned
• Reporter: Andy LoPresto
• Created: 28/May/16 00:07
• Updated: 12/Jul/16 16:27

Description

As explored in NIFI-1919, the expression language string replacement methods could be more clearly named to differentiate their actions – the difference between replace and replaceAll is not their frequency of operation, but rather that replace accepts only literal strings, while replaceAll interprets the provided search pattern as a regular expression.

Related, the ReplaceEvaluator, ReplaceAllEvaluator, and new ReplaceFirstEvaluator classes differ only by one line for each respective operation. It may be possible to refactor this to remove duplicate code.

Issue Links

• is related to: NIFI-1919 Expression Language only evaluates regular expression replacement on replaceAll, not replace