Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 04-15-2018 07:17 AM
I'm only encountering this error when I import from mssql windows server 2003. When I import from MYSQL 5.5 to MYSQL 5.6 it does not have any problem. I'm using sqljdbc4.jar for the sql driver.
I also attached the screen shot of the error.
Please help me getting rid this error without mapping timestamp column to string.
Created 04-15-2018 07:22 AM
To Override the default mapping from SQL type to Hive type for configured columns use --map-column-hive option.
Refer to the documentation here
Created 04-18-2018 08:36 PM
Unfortunately no but setting the attribute --map-column-hive Date=Timestamp to Sqoop will definitely work
Created 04-15-2018 07:22 AM
To Override the default mapping from SQL type to Hive type for configured columns use --map-column-hive option.
Refer to the documentation here
Created 04-15-2018 07:38 AM
thank you for your fast response @Geoffrey Shelton Okot. I already know that --map-column-hive is used to override the default mapping from SQL type to Hive type. Is there any other way to get rid of that error without using --map-column-hive??
Created 04-18-2018 08:36 PM
Unfortunately no but setting the attribute --map-column-hive Date=Timestamp to Sqoop will definitely work