cube-js/cube

Variable Length Decimal Support to Handle Cube Store Parquet Data Type Issues

Open

#3,412 opened on Sep 10, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (1,965 forks)batch import
cube storehelp wanted

Repository metrics

Stars
 (19,563 stars)
PR merge metrics
 (Avg merge 5d 16h) (138 merged PRs in 30d)

Description

Describe the bug When leveraging a MySQL decimal field that is defined as DECIMAL(65,30), the pre-aggregated results cannot be stored within Cube Store.

To Reproduce Steps to reproduce the behavior:

  1. Create a MySQL table (likely any database will do as its a Parquet conversion issue) with DECIMAL(65,30).
  2. Insert extremely large values in this field.
  3. Perform an aggregate query using SUM
  4. Define as a pre-aggregate query
  5. Watch the CREATE TABLE process fail when using Cube Store as your pre-aggregate data store repository.

Expected behavior

  1. Ideal behavior - Cube Store can correctly map data types of this nature.
  2. Acceptable behavior - Variable length can be defined as part of your measurement definition for pre-aggregate consumption

Screenshots N/A

Version: Current

Additional context None

Contributor guide

Research direction
Investigate how Cube Store maps MySQL DECIMAL(65,30) to Parquet data types and identify the cause of the CREATE TABLE failure. Check the data type conversion logic and consider adding variable length decimal support.
Tech stack
rust
Domain
backenddatabase
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.
Needs investigation
Prerequisites
SQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50