[
https://issues.apache.org/jira/browse/APEXMALHAR-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199171#comment-15199171
]
Bhupesh Chawda commented on APEXMALHAR-2020:
--------------------------------------------
Discussions here:
http://mail-archives.apache.org/mod_mbox/apex-dev/201603.mbox/%3CCAHvM9d1=vAXUfHVh-f9HWgD2=9e-fA5MF9cAj=+beWpUeg=k...@mail.gmail.com%3E
> HBase Row key type should be configurable
> -----------------------------------------
>
> Key: APEXMALHAR-2020
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2020
> Project: Apache Apex Malhar
> Issue Type: Improvement
> Reporter: Bhupesh Chawda
> Assignee: Bhupesh Chawda
>
> In the current design of HBase input and output operators, the row key is
> hard-coded to be of String type.
> In case of numeric keys which are typecasted to String, incremental read is
> problematic. For example, after reading key = 9, we may not be able to read
> any record with say, key = 8888, when though numerically 8888 > 9,
> lexicographically "9" > "8888".
> This is the case when data is being read from an HBase store where data is
> constantly coming in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
