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/07/08 08:13:11 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=15367382#comment-15367382 ] 

ASF GitHub Bot commented on STORM-1919:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/storm/pull/1517


> 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)