You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2016/07/08 08:14:10 UTC

[jira] [Resolved] (STORM-1919) Introduce FilterBolt on storm-redis

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

Jungtaek Lim resolved STORM-1919.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0
                   2.0.0

Merged into master and 1.x-branch.

> 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
>             Fix For: 2.0.0, 1.1.0
>
>
> 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)