Julian Hyde created CALCITE-761:
-----------------------------------
Summary: Pre-populated materializations
Key: CALCITE-761
URL: https://issues.apache.org/jira/browse/CALCITE-761
Project: Calcite
Issue Type: Bug
Reporter: Julian Hyde
Assignee: Julian Hyde
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 [~maryannxue] 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 [~jamestaylor], as this is related to optimization for Phoenix secondary
indexes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
