When importing JDBC SQL Types:
Sqoop currently uses the org.apache.sqoop.hive.HiveTypes.toHiveType method, where all of these types are mapped to STRING type.
Given that in fact, the JDBC value returned is of type Long, let me propose we can output the type for Hive as:
This is also in line with org.apache.sqoop.manager.ConnManager.toAvroType, where the type is
Some of the connectors override the toJavaType:
which may indicate different handling.
The SQLServerManager uses Java String as the output type, because of timezones.
Same holds true for OraOopConnManager, although it has a separate configuration boolean value
'oraoop.timestamp.string' which controls whether the import will use timezones and convert date types
to Java String, or timezones are going to be dropped and import will behave the 'sqoop way'.
Both of these connectors already handle these types as String by default, proposed change would not affect them.
Other connectors are needed to be checked.
Some of the connectors override the toHiveType:
This connector uses the 'sqoop way':
and only when not resolved, the type used is decided:
This code is affected with proposed change. As the Hive TIMESTAMP is timezone-less, we have to change the handling in this method - respect the property 'oraoop.timestamp.string' - if true, output STRING hive type, if false, go with 'sqoop way'.
The Hive Type is only used when generating the table ddl (create statement) and Hive can properly recognize the JDBC compliant java.sql.Timestamp format "YYYY-MM-DD HH:MM:SS.fffffffff", so no connector should be affected in a way, that Hive would not read the resulting column values.
However, thorough testing should be done on all connectors before releasing any column type behavior changes.