Github user ctramnitz commented on the issue:
https://github.com/apache/incubator-metron/pull/579
I agree to both of your points, defining it with the final name from the
beginning would be more efficient and we should come up with a more normalized
and standardized field naming convention in general.
However, the second part is something for all parsers, not just this one,
so it's a little bit out of scope for this PR. In fact, this PR doesn't change
the concept of the previous code, it just makes the "intermediate" field names
more consistent by following the vendor documentation.
My suggestion would be to either merge this PR as-is or with
one-time-definition of already defined Metron field names. To follow-up on the
other topic we create a new Jira to define a normalized message format for all
parsers (and enrichments), with subtasks to adapt each of the parsers
(including this one).
---
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.
---
