Problem with use of AS with an select statement

[EricTonissen]

I have this pipeline running using a DB2 database

The result on windows is as expected

Query with AS.0 - SQL query : SELECT pv.VARIABLE_VALUE AS config_name FROM PROCESS_VARIABLES pv
Metadata structure of stream.0 - Signaling 'output done' to 1 output rowsets.
Write to log.0 -
Write to log.0 - ------------> Linenr 1------------------------------
Write to log.0 - Position = 1
Write to log.0 - Fieldname = CONFIG_NAME
Write to log.0 - Comments = CONFIG_NAME
Write to log.0 - Type = String
Write to log.0 - Length = 100
Write to log.0 - Precision = -1
Write to log.0 - FormatMask = null
Write to log.0 - Origin = Query with AS
Write to log.0 -
Write to log.0 - ====================

The result on Linux is as NOT as expected

Query with AS.0 - SQL query : SELECT pv.VARIABLE_VALUE AS config_name FROM PROCESS_VARIABLES pv
Metadata structure of stream.0 - Signaling 'output done' to 1 output rowsets.
Write to log.0 -
Write to log.0 - ------------> Linenr 1------------------------------
Write to log.0 - Position = 1
Write to log.0 - Fieldname = VARIABLE_VALUE
Write to log.0 - Comments = CONFIG_NAME
Write to log.0 - Type = String
Write to log.0 - Length = 100
Write to log.0 - Precision = -1
Write to log.0 - FormatMask = null
Write to log.0 - Origin = Query with AS
Write to log.0 -
Write to log.0 - ====================

Is there something wrong ?

The db2 jdbc drivers on both machines are the same.

[bamaer]

The difference between Windows and Linux is a bit surprising, but afaik, that's been an issue with the DB2 JDBC driver for a loooong time.

[bamaer]

I can't test this, but it looks like setting the option useJDBC4ColumnNameAndLabelSemantics with a value of 1 could help to resolve this.

[EricTonissen]

Adding this to the attributes did the trick "EXTRA_OPTION_DB2.useJDBC4ColumnNameAndLabelSemantics": "false",