[
https://issues.apache.org/jira/browse/NIFI-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248346#comment-16248346
]
ASF GitHub Bot commented on NIFI-4578:
--------------------------------------
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2256#discussion_r150375690
--- Diff:
nifi-nar-bundles/nifi-hbase-bundle/nifi-hbase-processors/src/main/java/org/apache/nifi/hbase/PutHBaseRecord.java
---
@@ -127,6 +127,18 @@
.defaultValue("1000")
.build();
+ protected static final AllowableValue NULL_FIELD_EMPTY = new
AllowableValue("empty-string", "Empty String", "Use an empty string");
--- End diff --
Shouldn't the name of this option be 'Empty Bytes'? As there's Record data
types other than String, 'Empty Bytes' sounds more appropriate to me.
> PutHBaseRecord fails on null record field values
> ------------------------------------------------
>
> Key: NIFI-4578
> URL: https://issues.apache.org/jira/browse/NIFI-4578
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
>
> A NullPointerException is thrown when a nullable field has a null value. A
> strategy for handling this needs to be added.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
