Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
I feel that this one is quite valid concern - we're not explicitly specifying what encoding we're using when serializing/deserializing data. We're depending on the default UTF-8 being set, which is not optimal as some users can change that and then things will break.
I'll attach class to fix this in the client module and will fix other module as I'll get to them.
Attachments
Attachments
Issue Links
- is related to
-
SQOOP-2551 Sqoop2: Explicit encode data sent in SqoopClient with charset
- Resolved