You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/05 03:42:26 UTC

[jira] [Updated] (STORM-519) HBaseLookupBolt should pass the input tuple to ValueMapper to allow users to enrich input tuple.

     [ https://issues.apache.org/jira/browse/STORM-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-519:
-------------------------------
    Component/s: storm-hbase

> HBaseLookupBolt should pass the input tuple to ValueMapper to allow users to enrich input tuple.
> ------------------------------------------------------------------------------------------------
>
>                 Key: STORM-519
>                 URL: https://issues.apache.org/jira/browse/STORM-519
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-hbase
>    Affects Versions: 0.9.3
>            Reporter: Parth Brahmbhatt
>            Assignee: Parth Brahmbhatt
>            Priority: Minor
>             Fix For: 0.9.3
>
>
> Currently the hbase lookup bolt only passes the result returned after the lookup is performed to HBaseValueMapper interface. This restricts the user to only return result instance's variable as values that can be emitted. 
> The general use case is , user receives a tuple , it looks up some value from hbase for this tuple, the lookup bolt returns some combination of original tuple and new lookup value. With the current interface the user can only return/emit values from the lookup and not from original tuple. I propose to pass the original input tuple along with the result to interface.



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