Apache Hop version?
2.16.0
Java version?
jdk-17.0.12
Operating system
Windows
What happened?
When German umlauts (ä, ö, ü) are used in a SQL file that is read by the SQL action, the umlauts are not stored correctly in the source database.
- The SQL input file is encoded in UTF-8.
- The workflow is executed on Windows.
- It works correctly if the SQL file is encoded in Windows-1252, but it should also work with UTF-8.
- When the workflow is executed on Linux, the umlauts are stored correctly.
The current workaround it to first read the sql file (load file content in memory transform) with utf-8 encoding, and then pass the loaded content as a variable to the SQL action.
Issue Priority
Priority: 3
Issue Component
Component: Actions