I forget where I read it, but I was told that there is no de jure size limit on tuples. My topology will have tuples 1M in size, and outliers much larger than that. I haven’t seen any issues. Obviously at some point, you run out of memory…. ☺
****This email did not originate from the Premier, Inc. network. Use caution when opening attachments or clicking on URLs.*****
Thanks. What if it's big? My Strings end up being a couple thousand characters long, and each map has around 500 of them. Seems daunting to emit such a tuple. Any thoughts on that?
On Tue, Nov 21, 2017 at 7:23 PM, Stig Rohde Døssing <email@example.com> wrote:
I think that as long as you ensure that everything in the map can be serialized, it's fine.
2017-11-21 18:31 GMT+01:00 Marco Costantini <firstname.lastname@example.org>:
I have a batching bolt which ultimately makes a Map<String, Set<String>>. At a time I decide, I need to emit that map to the next bolt in the topology. I've tried it and it works, but I'm curious as to whether this is an anti-pattern or if there are problems with doing this that I am unaware of.
Please and thanks,