Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-1900

When a record column and its child column are retrieved together, the record column might not be inferred as record type properly

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.11.0
    • Component/s: Planner/Optimizer
    • Labels:
      None

      Description

      For example, given a following query, the column 'glossary' can be inferred as the TEXT type rather than the RECORD type.

      default> select glossary from self_desc_table2 where char_length(glossary."GlossDiv".title) > 0 
      

      This is because columns of the query are inferred in an arbitrary order, and there isn't any routine to resolve the conflict of inferred data type.

        Attachments

        1. TAJO-1900.patch
          6 kB
          Jihoon Son

          Activity

            People

            • Assignee:
              jihoonson Jihoon Son
              Reporter:
              jihoonson Jihoon Son
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: