[ 
https://issues.apache.org/jira/browse/METRON-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059410#comment-16059410
 ] 

ASF GitHub Bot commented on METRON-1001:
----------------------------------------

Github user cestella commented on a diff in the pull request:

    https://github.com/apache/metron/pull/621#discussion_r123512796
  
    --- Diff: 
metron-platform/metron-parsers/src/main/java/org/apache/metron/parsers/bolt/ParserBolt.java
 ---
    @@ -129,18 +148,29 @@ public void execute(Tuple tuple) {
           boolean ackTuple = !writer.handleAck();
           int numWritten = 0;
           if(sensorParserConfig != null) {
    +        Map<String, Object> metadata = getMetadata(tuple, 
sensorParserConfig.readMetadata());
             List<FieldValidator> fieldValidations = 
getConfigurations().getFieldValidations();
             Optional<List<JSONObject>> messages = 
parser.parseOptional(originalMessage);
             for (JSONObject message : 
messages.orElse(Collections.emptyList())) {
               message.put(Constants.SENSOR_TYPE, getSensorType());
    --- End diff --
    
    * If you turn on parsing metadata and do not indicate to merge the 
metadata, it will be available to stellar field transformations.
    * If you turn on parsing metadata and *do* indicate that you wish to merge 
the metadata, it will be both merged and available to stellar field 
transformations.


> Allow metron to ingest parser metadata along with data
> ------------------------------------------------------
>
>                 Key: METRON-1001
>                 URL: https://issues.apache.org/jira/browse/METRON-1001
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Casey Stella
>            Assignee: Casey Stella
>
> Currently, we only ingest data in Metron.  Often, there is valuable metadata 
> constructed up-stream of Metron that is relevant to enrichment and cross-cuts 
> many data formats.  Take, for instance, a multi-tenancy case where multiple 
> sources come in and you'd like to tag the data with the customer ID.  In this 
> case you're stuck finding ways to add the metadata to each data source's 
> format.  Rather than do that, we should allow metadata to be ingested along 
> with the data associated with it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to