Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-5923 Supporting the single cell storage format for mutable global indexes
  3. PHOENIX-6220

CREATE INDEX shouldn't ignore IMMUTABLE_STORAGE_SCHEME and COLUMN_ENDCODED_BYTES

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 5.1.0, 4.16.0
    • None
    • None

    Description

      IMMUTABLE_STORAGE_SCHEME and COLUMN_ENCODED_BYTES that is specified in CREATE INDEX needs to be respected. Today, it is ignored and value is just gotten from the parent. Parent table can still use ONE_CELL_PER_COLUMN storage scheme. If the parent table is using COLUMN_ENCODED_BYTES=0 (none), we recommend using COLUMN_ENCODED_BYTES=2 for the index table by default (can be overriden) when SINGLE_CELL storage scheme is used. 2-byte column mapping enables to define 65535 columns which should be enough.

      Attachments

        1. PHOENIX-6220.4.x.001.patch
          16 kB
          Gokcen Iskender
        2. PHOENIX-6220.4.x.002.patch
          16 kB
          Gokcen Iskender
        3. PHOENIX-6220.4.x.003.patch
          16 kB
          Gokcen Iskender

        Issue Links

          is a clone of

          Sub-task - The sub-task of the issue PHOENIX-6219 GlobalIndexChecker should work for index:SINGLE_CELL_ARRAY_WITH_OFFSETS and data:ONE_CELL_PER_COLUMN

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #963

          Activity

            People

              giskender Gokcen Iskender
              giskender Gokcen Iskender
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: