Hi, Firstly, I know that the transactional topology is deprecated, but this is some legacy code I have to work with, and currently we cannot afford migrating it to a Trident topology, so I have to stick to the transactional one.
So my issue is that, based on some business conditions, one of my bolts may (or may not) emit a tuple. If the bolt emits it, then no issue whatsoever. However, it the bolt does not emit a tuple, then the whole topology gets stuck as nothing arrives to the final ICommitter bolt. Therefore, how could I handle the scenario where a bolt does not emit a tuple (randomly) in a transaction topology? I thought about actually emitting a "dummy" tuple, and then modify the rest of bolts to "ignore" it, but this smells a bit to me and I'm wondering whether there's a better and more elegant solution to this scenario. Thanks in advance. Regards, Enrique Medina.
