sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Veena Basavaraj (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2261) Input value create/ update/ delete handling with null values
Date Tue, 24 Mar 2015 19:03:53 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378383#comment-14378383
] 

Veena Basavaraj commented on SQOOP-2261:
----------------------------------------

[~jarcec] I have added sub ticket to address the issue I have found in SQOOP-2113.

I prefer option #1, but if there is a strong preference to support #2, I sure can make that
change, since the current code added in SQOOP-1516 should be fixed to handle this use case.

> Input value create/ update/ delete handling with null values
> ------------------------------------------------------------
>
>                 Key: SQOOP-2261
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2261
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>             Fix For: 1.99.6
>
>
> The current code for updateConfig does not handle the use cases for null inputs added
in LINK_INPUT and JOB_INPUT
> either allow adding them by changing createInputValues
> or change the update*Config methods to handle
> 1. insert if not found on update
> 2. delete if update results in null value.
> or atleast #1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message