uber/queryparser

Column usage doesn't include hive struct accessors

Open

#11 建立於 2017年8月29日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Haskell (1,079 star) (145 fork)batch import
good first issue

描述

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.

貢獻者指南

技術棧
sql
領域
databaseanalytics
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic understanding of SQL parsingFamiliarity with Hive struct syntax
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
Investigate the column name extraction logic in the parser. The issue requests that when accessing struct fields like msg.name, the column name should reflect the leaf struct name. Look at how the parser currently retrieves column names and identify where the struct accessor is lost. Consider modifications to propagate the full path. See the issue at https://github.com/uber/queryparser/issues/11.