I have following Kettle transformation:
The output is:
2017/06/02 14:51:10 - Write to log.0 - ------------> Linenr 1------------------------------
2017/06/02 14:51:10 - Write to log.0 - Text = This is line 1
2017/06/02 14:51:10 - Write to log.0 - Length = 11
2017/06/02 14:51:10 - Write to log.0 - Copy = [B@709B5D90
2017/06/02 14:51:10 - Write to log.0 -
2017/06/02 14:51:10 - Write to log.0 - ====================
2017/06/02 14:51:10 - Write to log.0 -
2017/06/02 14:51:10 - Write to log.0 - ------------> Linenr 2------------------------------
2017/06/02 14:51:10 - Write to log.0 - Text = This is line 2 and is longer
2017/06/02 14:51:10 - Write to log.0 - Length = 11
2017/06/02 14:51:10 - Write to log.0 - Copy = [B@7E5CADF3
2017/06/02 14:51:10 - Write to log.0 -
2017/06/02 14:51:10 - Write to log.0 - ====================
2017/06/02 14:51:10 - Write to log.0 -
2017/06/02 14:51:10 - Write to log.0 - ------------> Linenr 3------------------------------
2017/06/02 14:51:10 - Write to log.0 - Text = This is line 3 and is much longer
2017/06/02 14:51:10 - Write to log.0 - Length = 11
2017/06/02 14:51:10 - Write to log.0 - Copy = [B@7A6336E0
It seems kettle refers to the column "Text" by its hashcode instead of its value. What am I doing wrong?
The values you see are not hashcodes but references to raw data. This happens when the input step has Lazy conversion enabled. The Calculator step should be triggering the conversion to strings but for some reason it is skipped in this case.
Uncheck Lazy conversion in the CSV input step to fix it.