River will stop import if MapperParsingExpcetion was raised

[soulski]

I had problem that river will stop import if it fail to parse object that sync from mongodb. Failure might come from invalid format object or different type of same field. How could I make it still keep running without stop when there is an error.

example of error that make river stop import rg.elasticsearch.index.mapper.MapperParsingException: object mapping for [users] tried to parse as object, but got EOF, has a concrete value been provided to it? at org.elasticsearch.index.mapper.object.ObjectMapper.parse(ObjectMapper.java:467) at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:515) at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:462) at org.elasticsearch.index.shard.service.InternalIndexShard.prepareIndex(InternalIndexShard.java:392) at org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:203) at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:556) at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:426) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722)

[richardwilly98]

Can you please send the full ES log file? I am not sure to understand the context

[tmaiaroto]

I also get this error. https://gist.github.com/tmaiaroto/eeaeb123f6185c864479

Any way to skip over errors and just ignore the document and continue indexing the rest? I can't guarantee the consistency of my data unfortunately (which is part of why I'm using MongoDB in the first place).

[Guibod]

Anyone know how to avoid that ?