11-04-2014 12:20 PM
I looked at the options provided by sqoop export operation but could not find any options to handle bad records. For example once in a while it is possible that a character is present where a number is expected in a huge set of records. Is there a way to handle these scenarios in sqoop without failing the job and providing the bad records in a file.
Even if this is out of the box functionality is there any work around by extending the code?
11-04-2014 12:26 PM
11-04-2014 06:34 PM
number to string was just an example, I am just saying bad records in general.
Another example would be length of value is too long. Do i have to handle each of those individually? Currently it rolls back all the import/export when it hits a bad record