Currently functions are only registered during user written code. Many of the functions (with exception of bloom and map creation) can be auto registered and used without other knowledge of Quality internals. This could be true of using auto defined user lambdas in a later release.
The plugin should be defaulted to a call to registerQualityFunctions on the driver plugin side, with the parameters as non final defs to allow simple overriding at the root plugin level.
As the driver plugin framework is only from 3 onwards it's a good opportunity to stub out the 2.4 impl but deprecate 2.4 at the same time for some future removal.
Currently functions are only registered during user written code. Many of the functions (with exception of bloom and map creation) can be auto registered and used without other knowledge of Quality internals. This could be true of using auto defined user lambdas in a later release.
The plugin should be defaulted to a call to registerQualityFunctions on the driver plugin side, with the parameters as non final defs to allow simple overriding at the root plugin level.
As the driver plugin framework is only from 3 onwards it's a good opportunity to stub out the 2.4 impl but deprecate 2.4 at the same time for some future removal.