[
https://issues.apache.org/jira/browse/STORM-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378781#comment-14378781
]
Jungtaek Lim edited comment on STORM-691 at 3/25/15 8:48 AM:
-------------------------------------------------------------
[~revans2] Let me expose my opinion about issue version (including STORM-703,
and further issues).
Storm-redis will be released on 0.10.0 first, and seems like it's not scheduled
yet.
Since users can have first impression for storm-redis on 0.10.0, and we have
more time to improve, what do you think about applying improvements to 0.10.0
and release first version of storm-redis with whole improvements as many as
possible?
Surely it shouldn't block to release 0.10.0.
was (Author: kabhwan):
[~revans2] Let me expose my opinion about issue version (including STORM-703,
and further issues).
Storm-redis will be released on 0.10.0 first, and seems like it's not scheduled
yet.
Since cause users can have first impression for storm-redis on 0.10.0, and we
have more time to improve, what do you think about applying improvements to
0.10.0 and release first version of storm-redis with whole improvements as many
as possible?
Surely it shouldn't block to release 0.10.0.
> [storm-redis] Add basic lookup / persist bolts
> ----------------------------------------------
>
> Key: STORM-691
> URL: https://issues.apache.org/jira/browse/STORM-691
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 0.10.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Minor
> Fix For: 0.11.0
>
>
> Currently storm-redis provides AbstractRedisBolt for normal (not Trident)
> Bolt.
> Jedis is easy to use so it may be enough, but we can also provide
> implementations of AbstractRedisBolt for simple usage.
> eg. store (key, value) pair, get key's value
> Since Redis has various data types and commands, we can't cover whole things,
> but seems like below things could be considered.
> || Type || Read || Write ||
> | STRING | GET (key) | SET (key, value) |
> | HASH | HGET (key, field) | HSET (key, field, value) |
> | LIST | LPOP (key) | RPUSH (key, value) |
> | SET | SCARD (key) | SADD (key, member) |
> | SORTED SET | ZSCORE (key, member) | ZADD (key, score, member) |
> | HLL (HyperLogLog) | PFCOUNT (key) | PFADD (key, element) |
> Btw, since we will normally get key & value from tuple (as most external
> module did), HASH, SET, SORTED SET needs additional key to process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
