[
https://issues.apache.org/jira/browse/SQOOP-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378077#comment-14378077
]
Jarek Jarcec Cecho commented on SQOOP-2113:
-------------------------------------------
Actually we've explicitly designed the configuration object in a way that the
default value (not specified by user) is {{null}}. That is for example one
reason why our configuration objects don't support primitive types, but only
objects (e.g. {{Integer}} instead of {{int}}).
I'm still not entire sure what problem do you see though. The fact that we are
not storing "nulls" in database is just a small optimization. Obviously one
need to create entry in {{JOB_INPUT}} table if it don't exists already. We are
already supporting updating configuration objects (e.g. users can change values
from {{null}} to concrete value), so it doesn't seem as a new problem to me?
> Modify REST API for the RU operation on job and link config
> -----------------------------------------------------------
>
> Key: SQOOP-2113
> URL: https://issues.apache.org/jira/browse/SQOOP-2113
> Project: Sqoop
> Issue Type: Bug
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.6
>
> Attachments: SQOOP-2113-1.patch, SQOOP-2113-1.patch,
> SQOOP-2113-2.patch
>
>
> based on the design doc for 1516, support the RU operation on configs for rest
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
