[ 
https://issues.apache.org/jira/browse/NIFI-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248347#comment-16248347
 ] 

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_r150375912
  
    --- 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");
    +    protected static final AllowableValue NULL_FIELD_SKIP  = new 
AllowableValue("skip-field", "Skip Field", "Skip the field (don't process it at 
all).");
    +
    +    protected static final PropertyDescriptor NULL_FIELD_STRATEGY = new 
PropertyDescriptor.Builder()
    +            .name("hbase-record-null-field-strategy")
    +            .displayName("Null Field Strategy")
    +            .required(true)
    +            .defaultValue("empty-string")
    --- End diff --
    
    IMHO, I personally prefer having 'Skip Field' as the default value, because 
I think this processor is used more for ingesting stream of data, than updating 
existing data. In that sense, I prefer not to store empty bytes to minimize 
resource utilization.


> 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)

Reply via email to