Github user krichter722 commented on the issue:
https://github.com/apache/storm/pull/459
> It would probably be preferable to do as you suggest, regarding a
configuration class, but I'm not sure how much work there is to do there.
I wouldn't do it for all Maps, just the ones carrying complex types (I'm
sticking to my description above). On the other hand, having type safe
configuration classes for all Maps increases type safety to a maximum, but
that'd be a few hundred person hours (I'm saying that after going through a
large portion of the code making extremely trivial changes).
> I think it's definitely worth consideration, though. Maybe a dev list
email would be a good place to get opinions.
When I find more time, sure. Are you OK with merging this PR? It's a
contained unit of work and essentially a pareto optimization that cannot cause
any runtime exception that would not already occur and there're no compile time
issues.
---
