The output from a harvester run by a handler currently looks like this in the pipeline logs:
2020-03-04 11:31:45,974 INFO tasks.ABOS_SOTS[8f152b75-8c2b-435c-84a3-040c8bba9a4f] --- START TALEND OUTPUT ---
updated file 'IMOS_ABOS-SOTS_W_20190318_SOFS_FV00_SOFS-8-2019-MRU-Surface-wave-height-realtime.nc': {'is_harvested': True}
b'INFO 3/4/20 11:31 AM:liquibase: Successfully acquired change log lock\nINFO 3/4/20 11:31 AM:liquibase: Reading from anmn_metadata.databasechangelog\nINFO 3/4/20 11:31 AM:liquibase: Reading from anmn_metadata.databasechangelog\nINFO 3/4/20 11:31 AM:liquibase: Successfully released change log lock\nStart of try block\ntempFile_cid /tmp/talend-temp-3347967097857309966/changelog.xml\n***********************\nconn host:dbprod.emii.org.au, port:5432, schema:anmn_metadata, name:harvest?loginTimeout=1000&ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory, user:anmn_metadata\nurl_cid:jdbc:postgresql://dbprod.emii.org.au:5432/harvest?loginTimeout=1000&ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory\nschema_cid:anmn_metadata\nuserName_cid:anmn_metadata\nINFO 3/4/20 11:31 AM:liquibase: Successfully acquired change log lock\nINFO 3/4/20 11:31 AM:liquibase: Reading from anmn_metadata.databasechangelog\nINFO 3/4/20 11:31 AM:liquibase: Reading from anmn_metadata.databasechangelog\nINFO 3/4/20 11:31 AM:liquibase: Successfully released change log lock\n***** completed finally block ***********\nIn finally block\nStart of try block\ntempFile_cid /tmp/talend-temp-9197821981654341388/changelog.xml\n***********************\nconn host:dbprod.emii.org.au, port:5432, schema:anmn_metadata, name:harvest?loginTimeout=1000&ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory, user:anmn_metadata\nurl_cid:jdbc:postgresql://dbprod.emii.org.au:5432/harvest?loginTimeout=1000&ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory\nschema_cid:anmn_metadata\nuserName_cid:anmn_metadata\nINFO 3/4/20 11:31 AM:liquibase: Successfully acquired change log lock\nINFO 3/4/20 11:31 AM:liquibase: Reading from anmn_metadata.databasechangelog\nINFO 3/4/20 11:31 AM:liquibase: Reading from anmn_metadata.databasechangelog\nINFO 3/4/20 11:31 AM:liquibase: Successfully released change log lock\n***** completed finally block ***********\nIn finally block\nSLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".\nSLF4J: Defaulting to no-operation (NOP) logger implementation\nSLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.\n* iNewOrModifiedFileList_1 modified/new resource file_id=83206\n'
--- END TALEND OUTPUT ---
I think the reason it's all on one line is that Python 3 is printing it as a byte string and not turning the '\n' into a newline.
While we're looking at this output, it would make the logs easier to read (and parse) if each line of the talend output was indented (e.g. 4 spaces), or had some other starting characters (e.g. ">> ") to identify it as "quoted" external log.
The output from a harvester run by a handler currently looks like this in the pipeline logs:
I think the reason it's all on one line is that Python 3 is printing it as a byte string and not turning the '\n' into a newline.
While we're looking at this output, it would make the logs easier to read (and parse) if each line of the talend output was indented (e.g. 4 spaces), or had some other starting characters (e.g. ">> ") to identify it as "quoted" external log.