Those sound like good feature ideas. The way to get them into Calcite is to add
new variables to the template file, provide empty defaults for the variables,
and then override the variables in Druid’s parser.
For an example, see the changes to core/src/main/codegen/config.fmpp in
https://githu
Thanks for the note! Do you have any pointers to projects that do this in
sort of a "best practices" way?
As to specifics: one thing I wanted to explore is adding keywords that do
some of the same things as our query context parameters, so you don't have
to set context parameters in order to get t
Some specifics would be useful. But in general, adding a new keyword
(reserved or non-reserved) will require changes to the paser. Calcite
allows (I won't say it makes it easy) for projects like Druid to
create a derived parser by building a parser from the same parser
template as Calcite's core pa
Hey Druids,
I'm looking into how to add keywords to Druid's SQL dialect, and I wanted
to ask if anyone has enough familiarity with Calcite to point at some info
about how to do that without needing to modify Calcite itself?
