I guess trait really feels different from your config. I guess `Context`
is where you are looking for, see below.
/**
* Does nothing.
*
* @deprecated Previously, this method installed the cancellation-checking
* flag for this planner, but is now deprecated. Now, you should add a
* {@link Can
Hi Stamatis,
Thanks a lot for your reply. Yes, it seems the traits currently in Calcite
are used by the optimizer. I wonder whether we can extend it for other
use-cases. For example, I want to provide a way to the users that they can
set memory or cpu settings for an aggregate node from the user a
Hi Hequn,
I would describe traits as properties associated with RelNodes that provide
useful information to the optimizer (rules etc.) in order to generate a
plan.
If the configuration you are referring to is meant to guide the optimizer
in generating a plan then it seems ok to use traits. If not
