[
https://issues.apache.org/jira/browse/SQOOP-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-1678:
-----------------------------------
Summary: Sqoop2: [HDFS Connector] Configurable null values (was: Sqoop2:
Configurable null values)
> Sqoop2: [HDFS Connector] Configurable null values
> -------------------------------------------------
>
> Key: SQOOP-1678
> URL: https://issues.apache.org/jira/browse/SQOOP-1678
> Project: Sqoop
> Issue Type: Improvement
> Components: sqoop2-hdfs-connector
> Affects Versions: 1.99.4
> Reporter: Abraham Elmahrek
> Assignee: Abraham Elmahrek
> Fix For: 1.99.5
>
> Attachments: SQOOP-1678.0.patch
>
>
> Jobs should be able to define what the null values look like.
> Simple table:
> {noformat}
> +-------+-------------+------+-----+---------+-------+
> | Field | Type | Null | Key | Default | Extra |
> +-------+-------------+------+-----+---------+-------+
> | id | int(11) | NO | PRI | 0 | |
> | name | varchar(35) | YES | | NULL | |
> +-------+-------------+------+-----+---------+-------+
> {noformat}
> Content:
> {noformat}
> +----+------+
> | id | name |
> +----+------+
> | 1 | |
> | 2 | test |
> +----+------+
> 2 rows in set (0.00 sec)
> {noformat}
> Assuming the above blank "name" is null, then we should be able to tell the
> HDFS connector to choose different representations of NULL. Current default
> is NULL, but a blank value may be preferred instead:
> {noformat}
> 1,NULL
> {noformat}
> or
> {noformat}
> 1,
> {noformat}
> or
> {noformat}
> 1,-
> {noformat}
> etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
