carloea2 commented on PR #8637: URL: https://github.com/apache/texera/pull/8637#issuecomment-6179514158
Could you check structured configuration values in the property-fix path? The new field-name validation and number/boolean handling help, but at `e7c0d7b` an existing array or object field still falls through `coerceToFieldType()` and becomes a string. In an isolated service reproduction using a mocked model response, `fix_type: "property_change"`, `original_snippet: "outputColumns"`, and `suggested_snippet: "[]"` replaced the operator's `outputColumns` array with the string "[]" and requested a rerun. Could you restrict property fixes to supported fields/types, or parse and validate structured replacements against the operator's JSON schema before writing? Please cover an invalid array/object replacement leaving the graph unchanged and not rerunning, alongside a valid supported property fix. -- 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]
