mattcasters commented on PR #8017: URL: https://github.com/apache/hop/pull/8017#issuecomment-5341788850
Both inbound and outbound data type mappings can live in user-space. They should never be conflated and be source specific, not even databsae specific. For example, Iceberge v1/2 doesn't provide lengths and precisions for data types. This means that it's something that users would want to supply themselves before the data ends up in an EDW. All that I see as being separate to what you seem to be doing here, providing better support for, allowing rules to be defined for data typing by database plugins. I think it's a nice improvement. Don't worry about the hop-data-vault code, it's handling a separate challenge: `source --> data catalog --> target` -- 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]
