While developing EQL functions, some(see #54135 & #53999) end up being translated into other expressions which replaces them during optimization.
To avoid code repetition this pattern should be formalized; for example by introducing a Substitute scalar function, that does not return a script nor a pipe and has a dedicated method for getting its replacement.
While developing EQL functions, some(see #54135 & #53999) end up being translated into other expressions which replaces them during optimization.
To avoid code repetition this pattern should be formalized; for example by introducing a
Substitutescalar function, that does not return a script nor a pipe and has a dedicated method for getting its replacement.