Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.27.0
-
None
-
None
Description
Currently, calcite-core.jar contains the relevant parser template files, however, the usage of the templates is not clear from the client perspective (especially when you are new to Calcite).
It would be nice if Calcite published a plugin that simplifies building a parser extension.
We could reuse the same plugin in calcite-babel module. Currently babel references $rootDir/core/... directrly rather than fetching the parser templates from core jar.
It might make sense to ship parser templates in its own jar file, however, I have no strong opinion here. Parser.jj consumes <1% of the compressed jar size(225K compresses to 44K), so it is not a big deal, yet having a meaningful artifact name for the parser templates looks like the right thing to do.
Attachments
Issue Links
- is related to
-
CALCITE-707 Built-in support for simple DDL statements
- Closed