mattcasters commented on issue #2814: URL: https://github.com/apache/hop/issues/2814#issuecomment-5450636773
I haven't been communicating properly in this issue so my appologies to you all for that. But indeed, "works on my machine" was one of the main concerns plus a series of unintended consequences where a data engineers spends a lot of time chasing string conversion issues, usually right when they want to put something in production on a remote server. My preference is always to go to the bottom of what we're trying to achieve and as long as we can do that I'm fine with the conclusions. I understand the underlying frustrations and issues involved with locale and timezones with respect to data integration. It's the bane of a lot of data integration projects. Some projects and environments will get data from all over the place with times in UTC, some will have a mix, some will be fixed for a certain country and timezone. My feeling as such was that if there's a solution to be implemented, that it should be at the level of a project or project lifecycle environment. That being said, I'm not against making it also an option in the Hop GUI and part of the new Hop installation configurator. Language, locale and timezone are perhaps important enough to ask about and set as a default for the developer. We can take a big step forward in clarifying the situation. -- 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]
