I've noticed that the CalcitePrepare interface creates a parser in both the
parse and prepare paths, but only the prepare path applies the custom
parser config from the context. Is this intentional? Shouldn't both paths
use the config from the context?

Andrew

Reply via email to