CarlosJuncher03 commented on issue #7129: URL: https://github.com/apache/hop/issues/7129#issuecomment-4459591503
A complementary use case would be to allow the transformation to use an optional schema/mapping file, selected directly in the transformation's own configuration. This would be useful when most of the pipeline remains the same, but the JSON mapping changes between files or runs. In this case, using Metadata Injection can be more complex than necessary if only the input schema changes. The transformation could work in two modes: automatic discovery when no schema is provided, or schema-based mapping when a metadata/schema file is selected. This schema could define the output fields, data types, nested field mappings, and behavior for missing or extra fields. I see this as a lighter alternative for simple schema variation cases, not as a replacement for Metadata Injection. -- 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]
