Github user srdo commented on the issue:

    https://github.com/apache/storm/pull/1999
  
    @hmcl Either one is fine by me. Keeping it consistent with the old spout is 
probably the best solution. The only case where defaulting to emitting nulls 
makes sense is if the user supplies a RecordTranslator that sometimes returns 
null erroneously, because they'll then see the bug when they get unexpected 
nulls, but I don't think it's a big problem. 


---
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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to