[STORM-2331] Anchoring emit in JavaScript only works with exactly one anchor

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0, 1.1.0
• Component/s: storm-multilang
• Assignee: Antti Järvinen
• Reporter: Antti Järvinen
• Created: 28/Jan/17 11:06
• Updated: 02/Feb/17 06:48
• Resolved: 02/Feb/17 06:48

Description

org.apache.storm.task.ShellBolt.handleEmit method expects to find list of tuple ids from the message to anchor the emit to.

The storm.js function __emit can only handle case of specifying exactly one anchor. If none is specified the message will contain anchor list [undefined] and if multiple anchors are specified the message will contain nested anchor list [["anchor1", "anchor2"]].

In the case of not anchoring to any the ShellBolt will throw runtime exception when ConcurrentHashMap tries to call .hashCode() on null. In the case of multiple anchors the ShellBolt will probably throw some cast error because the anchor array cannot be cast to List<String> (did not test).

The fix should be made in storm.js

Issue Links

• links to: GitHub Pull Request #1901