[
https://issues.apache.org/jira/browse/NIFI-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339949#comment-15339949
]
ASF subversion and git services commented on NIFI-1895:
-------------------------------------------------------
Commit 0d2a9dc7e51dc9c271276ce42fa7fe140857aeae in nifi's branch
refs/heads/master from [~ryan_templeton]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=0d2a9dc ]
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.
Signed-off-by: Bryan Bende <[email protected]>
> 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)
