yzeng1618 commented on PR #9273:
URL: https://github.com/apache/seatunnel/pull/9273#issuecomment-2861174152

   > Why not use 
https://seatunnel.apache.org/docs/2.3.10/transform-v2/table-rename and 
https://seatunnel.apache.org/docs/2.3.10/transform-v2/field-rename to change 
name to lowercase?
   
   ## 1. Complexity in Scenarios with Numerous Fields
   For tables containing hundreds of fields, using transform plugins for field 
renaming becomes extremely cumbersome. Each field requires individual 
configuration, resulting in verbose and difficult-to-maintain configuration 
files. For example:
   
   ```hocon
   transform {
     FieldRename {
       source_table_name = "table1"
       result_table_name = "table1"
       field_name = {
         FIELD1 = "field1"
         FIELD2 = "field2"
         // ... potentially hundreds of fields
         FIELD500 = "field500"
       }
     }
   }
    ```
   ```
   
   ## 2. Complexity in Multi-Table/Full Database Synchronization Scenarios
   In multi-table or full database synchronization scenarios, using transform 
plugins becomes even more complex. Each table requires separate TableRename and 
FieldRename configurations, leading to extremely large configuration files. 
Additionally, if table structures change (e.g., adding new fields), the 
configuration files must be updated accordingly.
   
   ## 3. Flexibility of Code-Level Optimization
   Handling case sensitivity at the code level provides greater flexibility and 
functional extensibility:
   
   ### Enables automatic table creation functionality when case insensitivity 
parameters are set (currently developed, pending evaluation)
   
   ## 4态Consistency with Other Connectors
    The Iceberg connector also provides parameters to control case sensitivity, 
providing a unified user experience.
   
   


-- 
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]

Reply via email to