Actually this has nothing to do with the Elasticsearch output plugin being http vs. node.
Jordan has already confirmed the issue with BOM: https://github.com/logstash-plugins/logstash-codec-json/issues/1#issuecomment-66532688 On Wednesday, December 10, 2014 4:05:38 PM UTC-8, Brian wrote: > > We use the HTTP protocol from logstash to send to Elasticsearch, and > therefore we have never had this issue. > > There is a version of ES bundled with logstash, and if it doesn't match > the version of ES you are using to store the logs then you may see problems > if you don't use the HTTP protocol. > > Brian > > On Wednesday, December 10, 2014 3:53:30 PM UTC-5, Vagif Abilov wrote: >> >> Thank you Aaron, done. I've created an issue. But I'd like to find out if >> there's a workaround for this problem. What's really strange that the same >> Logstash installation works with similar JSON files on other machines. >> > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/16ad8f2f-6f8d-4007-becc-49a2df176ac1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
