[
https://issues.apache.org/jira/browse/SQOOP-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthic Hariharan updated SQOOP-2355:
-------------------------------------
Description:
There seems to be some issue with sqoop outputs for bit columns into HDFS.
Every time we perform a full table copy of a mysql table that has bit(1)
columns in it, sqoop replaces entries that have true or 000001 in them into the
[SOH character|http://en.wikipedia.org/wiki/C0_and_C1_control_codes#SOH]. This
issue doesn't seem to be happening if we are performing a sqoop incremental
import and merge process. I am aware that the community is working on getting
Sqoop 2 out of the door but is there a solution to this?
was:
There seems to be some issue with sqoop outputs for bit columns into HDFS.
Every time we perform a full table copy of a mysql table that has bit columns
in it, sqoop replaces entries that have true or 000001 in them into the [SOH
character|http://en.wikipedia.org/wiki/C0_and_C1_control_codes#SOH]. This issue
doesn't seem to be happening if we are performing a sqoop incremental import
and merge process. I am aware that the community is working on getting Sqoop 2
out of the door but can is there a solution to this?
> Sqoop full table import outputs ^A character for bit columns with true values
> -----------------------------------------------------------------------------
>
> Key: SQOOP-2355
> URL: https://issues.apache.org/jira/browse/SQOOP-2355
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.5
> Reporter: Karthic Hariharan
>
> There seems to be some issue with sqoop outputs for bit columns into HDFS.
> Every time we perform a full table copy of a mysql table that has bit(1)
> columns in it, sqoop replaces entries that have true or 000001 in them into
> the [SOH character|http://en.wikipedia.org/wiki/C0_and_C1_control_codes#SOH].
> This issue doesn't seem to be happening if we are performing a sqoop
> incremental import and merge process. I am aware that the community is
> working on getting Sqoop 2 out of the door but is there a solution to this?
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
