[
https://issues.apache.org/jira/browse/METRON-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302032#comment-15302032
]
ASF GitHub Bot commented on METRON-186:
---------------------------------------
Github user nickwallen commented on the pull request:
https://github.com/apache/incubator-metron/pull/136#issuecomment-221862663
I am wondering if `mapping` is the most descriptive word we can use here.
We are also using map in a lot of different contexts in the configuration that
makes it a bit confusing; `fieldToTypeMap`, `fieldMap`.
I am sure there are better alternatives, but `transform` is the word that
comes first to my mind. I think if we write the docs, the most descriptive
word will more easily fall out. That's what tends to happen for me at least.
> Create a fieldMapping functionality which allows for parsed fields to be
> transformed
> ------------------------------------------------------------------------------------
>
> Key: METRON-186
> URL: https://issues.apache.org/jira/browse/METRON-186
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Assignee: Casey Stella
>
> Currently the parsers take care of transforming raw data to the parsed JSON
> representation. Allow for a layer to be placed at a sensor level to
> transform input fields from the parsed messages to create new fields. For
> instance, mapping IANA protocol numbers to a standardized textual
> representation (i.e. 6 maps to TCP).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
