[GitHub] nickwallen edited a comment on issue #1325: METRON-1970 Add Metadata to Error Messages Generated During Parsing

[GitBox <gi...@apache.org>]

nickwallen edited a comment on issue #1325: METRON-1970 Add Metadata to Error Messages Generated During Parsing
URL: https://github.com/apache/metron/pull/1325#issuecomment-460359027
 
 
   > ... although it'd be nice to add the well understood fields.
   
   The only well-understood field would be topic which ends up looking like `metron.metadata.topic`.  And that is assuming that the user doesn't change the prefix which by default is `metron.metadata`.  
   
   No other fields are added auto-magically.  All other metadata fields are custom fields defined by the user.
   
   What due diligence do you think I should do here?  
     * Make sure the error metadata "topic" field is indexed properly with our out-of-the-box index templates in Elasticsearch?    
     * Or since that prefix can be changed by the user, which would break any template I provide, maybe I should just add some docs describing how a user should update their index templates when using metadata?
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services