uber/queryparser

Column usage doesn't include hive struct accessors

Open

#11 opened on Aug 29, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Haskell (145 forks)batch import
good first issue

Repository metrics

Stars
 (1,079 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

For tables where the majority of 'columns' are abstracted under a top-level column, e.g. body or msg, we don't surface the struct accessor as the column name, rendering analysis of these queries unusable.

Ideally, if we had a msg.name, msg.attrs.foo, msg.attrs.bar struct, we'd see the leaf struct names as the column name, i.e. msg.name, msg.attrs.foo, etc. Instead, we currently see msg for all of them.

Contributor guide

Research direction
Inspect how the parser extracts column names from struct types in Hive queries. Look at the code that handles struct field access (e.g., `msg.name`) and ensure it returns the full path instead of just the top level column.
Tech stack
None
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
SQLHaskell
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60