apache / apache/pinot

Allow unnested field to be renamed during ingestion of complex type

Open
#8,161 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
6.1k
Forks
1.5k
Avg merge
2d 3h
Merged PRs (30d)
195

Description

Pinot supports unnesting a complex type as documented here: https://docs.pinot.apache.org/basics/data-import/complex-type#handle-the-complex-type-with-ingestion-configurations

As part of this operation, nested fields appear as flat columns in Pinot with this naming convention: '.'.

It might be useful to rename such "unnested" fields to a user chosen config. For instance, user may choose to only retain '' in the above example. There may be other ways to specify this renaming policy.

Contributor guide

Open the contributing guide

Research direction

Start with the complex-type ingestion configuration documentation linked in the issue and trace the existing unnesting configuration. Done means a user-configurable renaming policy is defined for flattened fields such as ., with the behavior documented for ingestion users.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.