Github user roshannaik commented on the issue:
https://github.com/apache/storm/pull/1942
@HeartSaVioR
I am OK with that line of thinking of handling aliases, as you are looking
to make it more intuitive to user. .. although we may not have a real problem
to justify public interface changes.
However... the author's concern is quite the opposite ... it is not from
a user perspective. He is trying to make code *more generic* (as he puts
it) by **removing** aliasing ... because we need to make the alias known to
Hdfs Spout.... Which means no enums, no text() or sequence() etc.
*Side note:* This approach of using aliases OR class names in the same
place has precedence in other projects as well... Apache Flume uses this
pattern a fair amount.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
