Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Replacement for tOracleInput

 

  • What has happened here is the tOracleInput component (available in v6.5.1) has been replaced with tJDBCInput in v7.1.1 forward
  • This framework (gets data from Relational DB sources to Hive) is still running in v6.5.1
  • We have modified it to use tJDBCInput and our expectation is that it works in the same way
  • Here’s an example of what is happening:
  • In the Source (Oracle) the date is stored as 2020-06-05 12:39:19.345123
  • The default output of the date column using tJDBCInput component is Fri Jun 05 12:39:19 SGT 2020
  • If we cast it to a date datatype (in tJDBCInput), the output is 2020-06-05 12:39:19.345 (trimming it)
  • If we cast it to a string datatype (in tJDBCInput), the output is 2020-06-05 12:39:19.345123 (expected result)

 

The challenge here is all applications using Talend, when they upgrade to v7.3, will have to do the above or similar changes if they want to see the same output they were seeing in v6.5.1 and that too only after casting a “Date” datatype to “String”.

 

How do I get the same format (2020-06-05 12:39:19.345123) as the source in 7.3?

Labels (2)
0 Replies