Just upgraded to 2019.0.2.0 and the BulkAttributeRenamer shows some unexpected behaviour, when an attribute's name contains special characters (in my case German umlauts "äöü", but I assume any non-ascii trigger the problem). Problem did NOT occur in 2017.1.2.
The transformer's mode of operation (prefix, regex etc.) doesn't seem to matter: simply adding a prefix is enough to trigger the bug.
Minimal example to reproduce:
- Create a feature with an attribute name, e.g. "ÄTTRIBUTE" = 1
- Add a prefix to it with BulkAttributeRenamer, e.g. "FOO_"
- Note you now have "FOO_ÄTTRIBUTE" as expected, but with an empty value (instead of =1) AND you still have "ÄTTRIBUTE" carrying the original value (only visible when inspecting all of the feature's attributes, i.e. click the row in inspector)
Can anyone else reproduce this?
Best answer by fmelizard
View original