[TAJO-1752] NameResolver cannot find nested records properly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.11.0
• Component/s: Planner/Optimizer
• Assignee: Jihoon Son
• Reporter: Jihoon Son
• Created: 12/Aug/15 06:16
• Updated: 12/Aug/15 12:10
• Resolved: 12/Aug/15 09:55

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