apache / apache/storm

[STORM-3717] Fail function won’t be called if msgId was not entered in emmit

Open
#7,499 1 comment 0 reactions 0 assignees View on GitHub
imported-jira-issue rfe
Dominant language
Java
Stars
6.7k
Forks
4k
Avg merge
1d 7h
Merged PRs (30d)
62

Description

Hey, 

When I tried to use your technology, I tried to implement fail method on Spout (implementing BaseRichBolt), on the spout I emitted without msgId and the fail function was not even called even though I implemented it.

I was stuck on this for around 7 hours trying to figure why my code doesn’t reach fail.

 

I think the current flow is not intuitive, I think default msgId (-1 or something) for msg without msgId or even a warning or exception is better than the current flow.

 

I would like to hear your opinion about that if you still support this flow about why 

you prefer to implement like that.

 

thank you!

---
Originally reported by nadi488, imported from: Fail function won’t be called if msgId was not entered in emmit


  • status: Open
  • priority: Major
  • resolution: Unresolved
  • imported: 2025-01-24

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported Spout behavior: emit without a msgId, then observe whether the fail method is reached. Review the surrounding Storm callback flow and determine whether the intended fix is a default msgId, a warning or exception, or documented existing behavior; done requires an agreed behavior and a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.