[NIFI-3928] Improve handling of DataTypeUtils.isNumberTypeCompatible

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: Extensions
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 17/May/17 14:48
• Updated: 30/May/17 20:22
• Resolved: 30/May/17 20:22

Description

The DataTypeUtils class has a method named isNumberTypeCompatible that takes as an argument a Consumer<String>. We should instead make this a Predicate<String> and make the logic that is passed to this method more efficient in determining whether or not a value matches. For instance, to determine if a value is an Integer, it's calling Integer.parseInt() instead of matching against a regular expression or iterating over the characters and testing via String.charAt(int) and Character.isDigit(char).

Issue Links

• duplicates: NIFI-3989 DataTypeUtils handles isLongTypeCompatible, isDoubleTypeCompatible, etc. poorly