Support for Case-Sensitive Column Names in Data Pipelines

[coder-pandit]

Problem

Currently, Olake converts all column names to lowercase during data loads from source to destination (e.g., in Parquet files). This behavior can cause issues for systems where case sensitivity is enabled.

For example, in our setup using Amazon Redshift with case sensitivity enabled, this transformation leads to inconsistencies between the source and destination schemas.

Proposed Solution

Introduce an option in the Olake UI to preserve the original case of column names during data transfer.

To maintain backward compatibility, this option can be disabled by default and made configurable for users who require case-sensitive column handling.

[merlynm20]

@coder-pandit Thanks for raising the feature request, we’ll keep you updated on its progress.

[ganesh8068]

Hi, I have already raised PR #957 for this. Could you please assign this issue to me? Thank you!

[nayanj98]

@ganesh8068 Assigning the issue to you.