emitting batches of tuples

Hello All, Is it possible emit batches of tuples, as opposed to one tuple at a time? In other word, is it possible to batch the tuples before emitting them? An application for batching the tuples is for example for writing the tuples to a tcp socket but not wanting to do a flush after each tuple

Re: emitting batches of tuples

I think I can give you an idea. You can emit several times in a unique tuple processing. Do a for loop, and execute emit function inside the loop to emit multiple tuples. On 3 November 2014 12:42, clay teahouse clayteaho...@gmail.com wrote: Hello All, Is it possible emit batches of tuples,

[jira] [Commented] (STORM-248) cluster.xml location is hardcoded for workers.

[ https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194517#comment-14194517 ] koray sariteke commented on STORM-248: -- I got it as a first step in storm.

Re: test clojure code

Here is what has worked for me: cd storm-core mvn clojure:repl (use 'clojure.test) (use 'YOUR TEST NAMESPACE) (run-tests 'YOUR TEST NAMESPACE) Ref: https://github.com/apache/storm/pull/14#issuecomment-31481945 -- Derek On Friday, October 31, 2014 7:04 AM, koray mehmet

Re: Enquiry regarding a project on @stormprocessor

I am curious what this project offers over using a redis client directly? Or compared to writing a trident state implementation for redis? - Bobby On Monday, November 3, 2014 2:35 PM, Abhishek Bhattacharjee abhishek.bhattacharje...@gmail.com wrote: Hi, We ( me and the CCed persons)

Re: Enquiry regarding a project on @stormprocessor

I skimmed some files of storm-redis, but I'm still curious that what's the key point from storm-redis. So I have some questions. - Is Redis for skipping completed tuples when root tuple is replayed, or continue processing tuple from last state? - Do users need to handle states it by his/her hand?

[GitHub] storm pull request: STORM-497: don't modify the mapping while the ...

Github user clockfly commented on the pull request: https://github.com/apache/storm/pull/257#issuecomment-61579721 @HeartSaVioR, The performance is not a concern, since taskToQueueId will only be modified for a few times. +1 for the patch --- If your project is set

[jira] [Resolved] (STORM-497) b.s.m.netty.Server.getMessageQueueId is not thread safe, and can return null

[ https://issues.apache.org/jira/browse/STORM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Zhong resolved STORM-497. -- Resolution: Fixed Fix Version/s: 0.9.3-rc2 b.s.m.netty.Server.getMessageQueueId is not thread

[GitHub] storm pull request: STORM-188: Allow user to specifiy full configu...

Github user clockfly commented on the pull request: https://github.com/apache/storm/pull/120#issuecomment-61599764 @d2r , sorry it takes so long. Now, the patch is synced with upstream. --- If your project is set up for it, you can reply to this email and have your

[jira] [Commented] (STORM-188) Allow user to specifiy full configuration path when running storm command

[ https://issues.apache.org/jira/browse/STORM-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195793#comment-14195793 ] ASF GitHub Bot commented on STORM-188: -- Github user clockfly commented on the pull

[jira] [Commented] (STORM-493) Workers don't inherit storm.conf.file/storm.options properties of the supervisor

[ https://issues.apache.org/jira/browse/STORM-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195806#comment-14195806 ] ASF GitHub Bot commented on STORM-493: -- Github user clockfly commented on the pull

[GitHub] storm pull request: Update README.md

Github user clockfly commented on the pull request: https://github.com/apache/storm/pull/292#issuecomment-61600425 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

[jira] [Commented] (STORM-329) Add Option to Config Message handling strategy when connection timeout

[ https://issues.apache.org/jira/browse/STORM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195808#comment-14195808 ] ASF GitHub Bot commented on STORM-329: -- Github user clockfly commented on the pull

[GitHub] storm pull request: STORM-253: Allow storm worker to use dynamic p...

GitHub user clockfly reopened a pull request: https://github.com/apache/storm/pull/45 STORM-253: Allow storm worker to use dynamic port instead of pre-configed. Add a ne... PR for [STORM-253](https://issues.apache.org/jira/browse/STORM-253) Allow supervisor to decide

[jira] [Commented] (STORM-253) Allow worker to choose available port instead of pre-configed

[ https://issues.apache.org/jira/browse/STORM-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195812#comment-14195812 ] ASF GitHub Bot commented on STORM-253: -- GitHub user clockfly reopened a pull request:

[GitHub] storm pull request: Update README.md

Github user clockfly commented on the pull request: https://github.com/apache/storm/pull/292#issuecomment-61601001 @lukedemi Please add the JIRA number to the title of the pull request? --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Commented] (STORM-535) setup 'java.library.path' for native-storm code if necessary

[ https://issues.apache.org/jira/browse/STORM-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195822#comment-14195822 ] ASF GitHub Bot commented on STORM-535: -- Github user clockfly commented on the pull

[jira] [Commented] (STORM-422) storm.cmd limits the number of arguments that can be passed to 'storm jar' on Windows

[ https://issues.apache.org/jira/browse/STORM-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195831#comment-14195831 ] ASF GitHub Bot commented on STORM-422: -- Github user asfgit closed the pull request at:

[jira] [Commented] (STORM-422) storm.cmd limits the number of arguments that can be passed to 'storm jar' on Windows

[ https://issues.apache.org/jira/browse/STORM-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195839#comment-14195839 ] Sean Zhong commented on STORM-422: -- committed at b64e7b7a74126f5dbf01ff257090f6396ed38ab2