Some functions in ESQL doesn't serialize their Source. That's fine, as long as it isn't used.

However, some of those functions emit warnings with the warnExceptions annotation, which means that their use the Source to get the line numbers, and the text of the function.
If they are executed in a datanode after serialization, the warnings may not be correct.

This is an issue to track and fix them all.

Currently tracked functions that may emit wrong warnings:

• DateDiff
• MvSlice
• MvSum
• All children of BinarySpatialFunction
• Replace

Most of those aren't confirmed, they just happen to not serialize their source and have a warnExceptions