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

ASF GitHub Bot commented on NIFI-1895:
--------------------------------------

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi/pull/542

    NIFI-1895 for 0.x

    This pull request contains @rtempleton 's work from PR 513, but rebased for 
the 0.x branch.
    
    In addition, there is another commit by me which adds a new property to 
PutHBaseJSON allowing the user to specify how to store the values. The reason 
for this is that we can't change the behavior for existing users who may want 
the processor to continue working how it was. This change makes the default 
behavior the same as previous versions, but allows the user to enable the 
change Ryan made. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bbende/nifi NIFI-1895-0x

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/542.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #542
    
----
commit 0ca89d019d1f04fbcb08a8ac6ff2916cf094f114
Author: rtempleton <[email protected]>
Date:   2016-06-09T15:16:49Z

    NIFI-1895 PutHBaseJSON processor treats all values as Strings
    
    The operator will now inspect the node value to determine type and convert 
as such.
    Numeric integral - Long (assumes widest type)
    Numeric not integral - Double (assumes widest type)
    Logical - Boolean
    everything else (including current Complex Type logic) - String
    
    Values that represent the row key continue to be implictly treated as 
Strings by the processor
    
    Removed depenency on HBase utility Bytes class from the PutHBaseJSON 
processor.
    Convenience methods to encode to byte array are now wrapped by the 
appropriate HBaseClientService instance.

commit 04285af71b3aba741b3cbf480f7ea466c84791c3
Author: Bryan Bende <[email protected]>
Date:   2016-06-17T21:10:40Z

    NIFI-1895 Adding a property to PutHBaseJSON to allow specifying how to 
store the values

----


> PutHBaseJSON processor treats all Values as Strings
> ---------------------------------------------------
>
>                 Key: NIFI-1895
>                 URL: https://issues.apache.org/jira/browse/NIFI-1895
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 0.6.1
>            Reporter: Ryan Templeton
>
> line 184 of PutHBaseJSON.java treats all JsonNode values as strings by 
> calling the .asText() method. We are working with using this processor to 
> load IoT time series data and this causes issues in HBase with 
> timestamps/numerics not getting sorted correctly.
> The operator should inspect the node value to determine type and convert as 
> such.
> Numeric integral - Long (assumes widest type)
> Numeric not integral - Double (assumes widest type)
> Logical - Boolean
> everything else (including current Complex Type logic) - String



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to