Skip to content

Allow unnested field to be renamed during ingestion of complex type #8161

@icefury71

Description

@icefury71

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions