When writing a Float value, using an uppercase F, to Vertica with the tVerticaOutput component in Copy mode, the Float value is rounded off to the nearest integer. The same values, but with the schema set to not nullable (that is, a float with lowercase f) works fine, and decimals are retained in Vertica.
This is a known bug in Talend v6.5.1.
The Job design is shown below:
The tMap component mappings are shown below:
To workaround this issue, remove the 0 from the Precision setting in the Talend schema, as shown below: