Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.4.0-incubating
    • Component/s: None
    • Labels:
      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 Maryann 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 Taylor, as this is related to optimization for Phoenix secondary indexes.

        Attachments

          Activity

            People

            • Assignee:
              julianhyde Julian Hyde
              Reporter:
              julianhyde Julian Hyde
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: