I have a similar issue. The data is already ASCII and per the customers request we are using ASCII \037 as a seperator in our tdch cli scripts. Upon execution we error out because the data is being stuffed into the first column and is not understanding the ASCII seperator. It does work when we translate the seperator to a \t. Any suggestions if we can support ASCII seperators in TDCH because it works in pure, non-TD sqoop.
I have a similar issue. The data is already ASCII and per the customers request we are using ASCII \037 as a seperator in our tdch cli scripts. Upon execution we error out because the data is being stuffed into the first column and is not understanding the ASCII seperator. It does work when we translate the seperator to a \t. Any suggestions if we can support ASCII seperators in TDCH because it works in pure, non-TD sqoop.
--Josh