[
https://issues.apache.org/jira/browse/STORM-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161122#comment-14161122
]
ASF GitHub Bot commented on STORM-519:
--------------------------------------
GitHub user Parth-Brahmbhatt opened a pull request:
https://github.com/apache/storm/pull/283
STORM-519 adding tuple as an input param to HBaseValueMapper so user can...
... chose to emit fields from original tuple in addition to lookup result.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Parth-Brahmbhatt/incubator-storm STORM-519
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/283.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 #283
----
commit f87bb3135b4dcfd2b73689a35bf0b73a6cc5bc75
Author: Parth Brahmbhatt <[email protected]>
Date: 2014-10-06T22:21:28Z
STORM-519 adding tuple as an input param to HBaseValueMapper so user can
chose to emit fields from original tuple in addition to lookup result.
----
> 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
> Affects Versions: 0.9.3
> Reporter: 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)
