ahmedabu98 commented on code in PR #31172:
URL: https://github.com/apache/beam/pull/31172#discussion_r1595690110


##########
sdks/java/managed/src/main/java/org/apache/beam/sdk/managed/ManagedSchemaTransformProvider.java:
##########
@@ -202,7 +203,26 @@ Row getConfigurationRow() {
   static Row getRowConfig(ManagedConfig config, Schema transformSchema) {
     // May return an empty row (perhaps the underlying transform doesn't have 
any required
     // parameters)
-    return YamlUtils.toBeamRow(config.resolveUnderlyingConfig(), 
transformSchema, false);
+    String yamlConfig = config.resolveUnderlyingConfig();
+    Map<String, Object> configMap = YamlUtils.yamlStringToMap(yamlConfig);
+
+    // The config Row object will be used to build the underlying 
SchemaTransform.
+    // If a mapping for the SchemaTransform exists, we use it to update 
parameter names and align
+    // with the underlying config schema
+    Map<String, String> mapping = 
MAPPINGS.get(config.getTransformIdentifier());

Review Comment:
   Similar to the reasoning above, a mapping exists only if the transform needs 
one. 
   In the Iceberg case, we are already producing a configuration schema with 
`snake_case` convention, so no remapping of names is needed.



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