getredash/redash

Add support for BigQuery's RECORD field type

Open

#4207 opened on Oct 2, 2019

View on GitHub
 (6 comments) (1 reaction) (0 assignees)Python (24,845 stars) (4,236 forks)batch import
Backendhacktoberfesthelp wanted

Description

Currently when you query a RECORD field type, you will get some weird object in the query output (see example). Instead we need to deconstruct it into separate columns (field.sub_field) like we do for MongoDB.

Contributor guide

Tech stack
pythonjavascriptgcpsql
Domain
dataanalyticsbackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of BigQuery data typesFamiliarity with PythonKnowledge of Redash query result handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Investigate how Redash handles MongoDB nested fields (likely in the query runner code) and apply similar logic to BigQuery's RECORD fields. Look at the BigQuery data source implementation in the Redash codebase, e.g., redash/query runner/big query.py. Check the existing MongoDB handling for reference in redash/query runner/mongodb.py. Ensure that sub fields are expanded into separate columns with dot notation.