Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
The design for materializations (materialized views) allows for them to be populated on demand (e.g. as an ArrayTable) the first time that the materialization is needed or to already exist, having been populated by the user.
According to Wei Xue the latter case does not work. Calcite tries to create a new table with the same name as the current table, then makes the name unique by adding a digit, then goes ahead and populates it.
We need to (a) allow such materializations to be defined in the JSON model, (b) document how to define them, (c) make them work, (d) add tests.
Cc James R. Taylor, as this is related to optimization for Phoenix secondary indexes.