Actually, it seems the root cause is that the materialization uses the
wrong configuration.
org.apache.calcite.materialize.MaterializationService.DefaultTableFactory#createTable
creates a new connection with the default configuration that does
TO_UPPER. Would it be ok for it to receive a CalciteConnectionConfig?
Mit freundlichen Grüßen,
------------------------------------------------------------------------
*Christian Beikov*
Am 24.08.2017 um 11:36 schrieb Christian Beikov:
Seems org.apache.calcite.prepare.CalcitePrepareImpl#prepare2_ misses a
call to
org.apache.calcite.sql.parser.SqlParser.ConfigBuilder#setCaseSensitive
to configure the parser according to the LEX configuration. Is that a
bug or expected?
Mit freundlichen Grüßen,
------------------------------------------------------------------------
*Christian Beikov*
Am 24.08.2017 um 11:24 schrieb Christian Beikov:
Hey,
I have configured Lex.MYSQL_ANSI but when a query gets parsed, the
column names of select items are "to-upper-cased".
I'm having problems with matching the row types of materialized views
and the source sql because of that. Any idea how to fix that?
--
Mit freundlichen Grüßen,
------------------------------------------------------------------------
*Christian Beikov*
