PG1204 opened a new pull request, #7299: URL: https://github.com/apache/texera/pull/7299
### What changes were proposed in this PR? If the HuggingFace operator's `Input Image Column` (or `Input Audio Column`) named a column that doesn't exist in the input table, `use_image_column` / `use_audio_column` silently became false and the user got the misleading "No image source. Set an Input Image Column or upload an image.", even though they *had* set one, just misspelled it. This distinguishes the two cases: at that point there's no upload and the column resolved to false, which when a column name is actually configured, can only mean it isn't in the table. So a non-empty configured column now produces a clear "Input Image Column '<name>' not found in the input table. Available columns: [...]" error instead of the generic "No image source" message. Same for audio. ### Any related issues, documentation, discussions? Closes #7197. ### How was this PR tested? `sbt "WorkflowOperator/testOnly org.apache.texera.amber.operator.huggingFace.* org.apache.texera.amber.util.PythonCodeRawInvalidTextSpec"`: passes (126 tests). Added a test asserting the generated script produces the "Input Image/Audio Column '...' not found" errors; `PythonCodeRawInvalidTextSpec` py-compiles the generated Python (guards the added nested indentation). scalafmt clean. ### Was this PR authored or co-authored using generative AI tooling? This PR was co-authored with Claude Opus 4.8 in compliance with ASF policy. -- 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]
