yzeng1618 opened a new issue, #9272: URL: https://github.com/apache/seatunnel/issues/9272
### Search before asking - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description When using the SeaTunnel Doris connector for data synchronization, there is a need to support case-insensitive column name handling. Currently, the Doris connector preserves the original case of column names by default, but in certain scenarios, it's necessary to ignore case differences for more flexible matching between source and target table column names. This requirement is particularly prominent when integrating with Oracle databases. Oracle has a significant characteristic: by default, table names and field names are automatically converted to uppercase for storage (unless defined with double quotes). Meanwhile, identifiers in Doris typically use lowercase form. This difference leads to frequent mapping issues during data synchronization from Oracle to Doris due to case mismatches. ### Usage Scenario - Oracle to Doris data migration, resolving conflicts between Oracle's default uppercase and Doris's lowercase - When the table structure of the source system differs from the Doris table structure in terms of column name case - Cross-database system data migration, where different systems have different case sensitivity handling - Scenarios where ignoring column name case differences simplifies configuration - Situations with historical data where column names have inconsistent casing but need to be processed uniformly ### Related issues no ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
