Data type conversion should either be disabled or handled once an object is created

  • 26 October 2016
  • 2 replies

Userlevel 1
Currently we are allowing users to change data type of a field through COM if there is no data in the object. But this change is happening only in Mongo and not in the redshift table. Because of this, there are lot of errors through out S3 and data load API connectors. I believe that this should either be disabled or handled properly. Once the redshift table is created, we should disable data type conversion even if there is no data. Or when the data type conversion is made through COM, we should automatically create a new column with same name and the required data type, and then delete the older field. Or we should have a flag that shows if there is any mismatch between data types between Mongo and Redshift tables.

2 replies

Userlevel 6
Badge +3
Phani -
Can you get this logged as a bug in JIRA?  Seems High priority to get this working properly.
Userlevel 1
Hi Denise,

I have created a JIRA request for this. Please find the link to JIRA request here.