Closed cabeca closed 3 years ago
Here is a second take on the problem.
I also have this issue and it would be really nice to have this handled, as I see thousands of these exceptions an hour. Looks like the second patch proposed here to deal with it effectively.
I wonder if this problem goes away in logstash 1.1.6 which has much improved text encoding support. Thoughts?
I wonder if this problem goes away in logstash 1.1.6 which has much improved text encoding support. Thoughts?
I will try to build master and see what results I get.
You can fetch daily builds here: http://r.logstash.net/jenkins/job/logstash.jar.daily/lastSuccessfulBuild/artifact/build/logstash-1.1.6.dev-monolithic.jar
As quick feedback. This is then fixed in logstash 1.1.6-dev by using the "encoding" parameter as you suggested. In my case setting it to any valid encoding will make it work.
Here is my change as reported in:
https://logstash.jira.com/browse/LOGSTASH-436
Best Regards Miguel Cabeça