You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by GitBox <gi...@apache.org> on 2019/02/04 20:07:01 UTC

[GitHub] justinleet commented on issue #1325: METRON-1970 Add Metadata to Error Messages Generated During Parsing

justinleet commented on issue #1325: METRON-1970 Add Metadata to Error Messages Generated During Parsing
URL: https://github.com/apache/metron/pull/1325#issuecomment-460393409
 
 
   The validation I'd do is to at least test my assumption (dynamic mapping) for ES. And then I'd make sure any differences get documented.  The documentation you mention (things like how to upgrade schemas to alleviate this sort of thing) would be great.
   
   Just to reiterate for anyone hopping in, I think this definitely fits the use case of getting things to Kafka (which helps out with things like replay use cases if a user decides to reconsume data).
   
   For the real time stores, my concern is that they behave differently. A) That ES's dynamic mapping means we do map this data and B) That Solr drops it completely.  This could have implications on dashboarding. I'm okay with this PR just going through to Kafka if there's not a reasonable way to align ES and Solr here.  It might be worth a follow-on ticket.
   
   

----------------------------------------------------------------
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