After upgrading to New York some of your MySQL / MariaDB data sources can experience issues while loading data if you have an old version of MySQL DB server which can not negotiate on the collation type.
You may experience the international accented characters as question marks. For example, instead of à, è, etc, you may observe question marks (?) within strings.
New York and onwards
New York release bundles a new and improved version of MySQL / MariaDB JDBC driver, and it's also included with MID Server. When MariaDB JDBC driver initiates a connection against a DB server, it also detects what the target DB server is configured for character set and collation type. Some old deployments of MySQL server seem to be incompatible for this process and the connection collation type and character set falls back to a collation and character set which is not UTF-8. Then, MariaDB JDBC driver processes this result set assuming it's UTF-8, which causes incorrect character conversions.
In order to instruct the DB to send the result set in UTF-8, you will need to do additional configuration on the data source. To get the form ready, you will need to add the "Connection URL" field to the data source form. In order to do that;
After you have made the field visible, you can start configuring your MySQL / MariaDB data source.
The end result should look like:
Then import your data one more time. This time accented characters should work fine.
"Connection URL" on Data Source form is an auto-populated field, which is filled with the values gathered from other fields, and in normal circumstances, it shouldn't be modified manually. If you make a change on any other field values (like DB Name) then the field content will change after the save operation.