Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fields added with AddFields transformations in builder manifests are downcased

Open
#268 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reproducing the provided builder manifest with the Python CDK's AddFields transformation and trace the sync path that creates the field. Compare it with the Airbyte test interface behavior, then verify that the resulting field retains the configured conversationId casing.

Written by the indexing model from the issue text.

Description

community

I have a transformation that adds a field. When I sync, the field does get added, but it is downcased. This does not happen on the airbyte test interface in-app.

transformations:
    - type: AddFields
      fields:
        - path:
            - conversationId
          value: "{{stream_partition.conversationId}}"

The field is added, but it is added as conversationid instead of conversationId

Dominant language
Python
Stars
26
Forks
53
Avg merge
7d 2h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from airbytehq/airbyte-python-cdk

All issues in airbytehq/airbyte-python-cdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.