So you're seeing a different substitution result when using %key% in:
FILTER '...%key%...'
versus:
PROCESSING 'NATIVE_FILTER=...%key%'
If so that would be a bug. The value that replaces %key% should be
consistent. The value you supply could be different though because how the
expression is
Good morning everyone,
we built an application which uses a runtime substitution for the filter
string. And we found a different behavior between (the old) Filter and
the native_processing filter if two values are parsed.
the request http://?..=vaule1,value2
results to
'value1','value2' with
