[STORM-1668] Flux silently fails while setting a non-existent property.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0, 2.0.0
• Fix Version/s: 1.0.0
• Component/s: Flux
• Epic Link: Release Apache Storm 1.0.0
• Assignee: P. Taylor Goetz
• Reporter: Parag Shah
• Created: 30/Mar/16 23:20
• Updated: 01/Apr/16 03:17
• Resolved: 01/Apr/16 03:16

Description

Currently, if a yaml file has a property with a name that does not exist on the java topology component object then flux silently fails by logging a message and does not throw an exception. This needs to be changed so that flux throws the exception failing topology submission so that user can take corrective action.