This repository has been archived by the owner on Jul 9, 2021. It is now read-only.
[SQOOP-3278]:Direct export to Netezza and encoding #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Closing conflicting PRs older than a year. Please reopen if it is still applicable. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Direct mode used an OutputStream writes to an export file using UTF-8. So, if your targeted Netezza uses an ISO encoding, non ASCII chars will be corrupted when Netezza loads the export file.
Using an OutputStreamWriter and relying on existing 'encoding' extended parameter (SQOOP-2607) enables to set the encoding that will be used to write the export file.