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

NameResolver cannot find nested records properly

    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

      See the title.
      You can reproduce as follows:

      default> CREATE EXTERNAL TABLE json_test (
      id TEXT, type TEXT, url TEXT,
      actor RECORD (
        id bigint,
        login text
      ),
      payload RECORD (
        push_id bigint,
        commits RECORD (
          message text,
          url text
        )
      ),
      public BOOLEAN,
      created_at text
      )
      USING JSON 
      LOCATION 'path'
      ;
      default>
      default> select type, payload.commits.message as msg from gh_json_test limit 3;
      ERROR: column 'payload.commits.message' does not exist
      

        Attachments

          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: