You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/24 11:55:16 UTC
[jira] [Commented] (STORM-1919) Introduce FilterBolt on storm-redis
[ https://issues.apache.org/jira/browse/STORM-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348179#comment-15348179 ]
ASF GitHub Bot commented on STORM-1919:
---------------------------------------
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/1517
STORM-1919 Introduce FilterBolt on storm-redis
* introduce RedisFilterBolt, and relevant class (RedisFilterMapper)
* add example topology: WhitelistWordCount
* update how to use to README.md
* also correct some javadocs
It should be easy to backport to 1.x-branch as well so I didn't create another pull request against 1.x-branch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/HeartSaVioR/storm STORM-1919
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1517.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 #1517
----
commit 5e72b7c90f6e157ad7e5a194697547dbf3b22fee
Author: Jungtaek Lim <ka...@gmail.com>
Date: 2016-06-24T11:50:49Z
STORM-1919 Introduce FilterBolt on storm-redis
* introduce RedisFilterBolt, and relevant class (RedisFilterMapper)
* add example topology: WhitelistWordCount
* update how to use to README.md
* also correct some javadocs
----
> Introduce FilterBolt on storm-redis
> -----------------------------------
>
> Key: STORM-1919
> URL: https://issues.apache.org/jira/browse/STORM-1919
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-redis
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
>
> While discussing about STORM-1880, it would be better to have FilterBolt explicitly instead of letting users set up their lookup mapper to act as filter.
> There's other benefit here: we can use exists / hexists on STRING / HASH datatype instead of retrieving actual value which reduces execution time / latency from Redis side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)