Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
Dane999
Partner - Contributor
Partner - Contributor

Datatype issue - Oracle Number(8) changed to INT when loaded to Kafka with Avro

I am using an Oracle source, loading to Kafka in Avro format. Use logical data types for specific data types is NOT checked.

This is causing my Number(8) column to get changed to an INT. 

Are there any options i can use to avoid creating a transformation for each column that this applies to ?

Labels (3)
1 Solution

Accepted Solutions
SwathiPulagam
Support
Support

Hi @Dane999,

 

Below is the data type conversion from Oracle to Replicate:

 

 

From Replicate to Kafka:

 

 

 

If your precision is between 1 and 9 then Kafka Avro primitive datatype will be INT. So what are you expecting for the Target datatype?

And please provide the exact datatype on the source side.

 

Thanks,

Swathi

View solution in original post

4 Replies
SwathiPulagam
Support
Support

Hi @Dane999,

 

Below is the data type conversion from Oracle to Replicate:

 

 

From Replicate to Kafka:

 

 

 

If your precision is between 1 and 9 then Kafka Avro primitive datatype will be INT. So what are you expecting for the Target datatype?

And please provide the exact datatype on the source side.

 

Thanks,

Swathi

Dane999
Partner - Contributor
Partner - Contributor
Author

this is the Oracle source:

Dane999_0-1663010671983.png

Kafka we are seeing: 

Dane999_1-1663010941132.png

 

shashi_holla
Support
Support

Hi @Dane999 

Please provide more details on the actual issue with having INT on the Kafka side. Is it causing any data truncation?

Thank you,

SwathiPulagam
Support
Support

Hi @Dane999 ,

 

As I mentioned in my previous post it is working as described in the user guide. 

What are you expecting in the Kafka target?

If you are expecting the same datatype like source as "number" then it is not a feasible option. Since Kafka has limited data types we will map with appropriate available datatypes in Kafka target.

 

Thanks,

Swathi