Closed apupier closed 6 years ago
We need a general solution for what to do with exchanges that cause an exception in the camel route, as these generally are going to require the user to figure out what to do with them.
I wonder for this case where you're splitting the string maybe we need some additional configuration available that lets the user specify that if the split fails it's okay and just stick the value into one of the target fields or if the split fails then an exception should be generated which would then cause the exchange to go into a dead letter queue kinda deal to be manually dealt with at some point.
This is a bug in atlasmap runtime, having inappropriate error level. Let's change this to WARN level, so that camel-atlasmap won't throw an Exception.
This issue was moved to atlasmap/atlasmap-runtime#275
otherwise this exception is thrown:
the error is only in pod log, a normal user would not have access to it so it will silently fail from Fuse Ignite interface.
For TP2, it might be nice to add a note in the tutorial. For future, Keith is wondering:
I guess both ways are valid depending on the usecase, so having the possibility to configure it would be even better.