sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abraham Elmahrek (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-2162) Sqoop2: InputEditable should be optional in JSON API
Date Tue, 03 Mar 2015 01:45:04 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abraham Elmahrek updated SQOOP-2162:
------------------------------------
    Description: 
Currently, it is not optional. The following JSON request will throw an exception:

{code:type=json}
{
    "id": -1,
    "inputs": [
        {
            "id": -1,
            "name": "Enum",
            "overrides": "",
            "sensitive": false,
            "type": "ENUM",
            "value": "YES",
            "values": "YES,NO"
        }
    ],
    "name": "c",
    "type": "JOB"
}
{code}

This breaks backwards compatibiltiy of our APIs. This Jira should fix that by providing a
default value.

  was:
Currently, it is not optional. The following JSON request will throw an exception:

{code:type=json}
{
    "id": -1,
    "inputs": [
        {
            "id": -1,
            "name": "Enum",
            "overrides": "",
            "sensitive": false,
            "type": "ENUM",
            "value": "YES",
            "values": "YES,NO"
        }
    ],
    "name": "c",
    "type": "JOB"
}
{code}


> Sqoop2: InputEditable should be optional in JSON API
> ----------------------------------------------------
>
>                 Key: SQOOP-2162
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2162
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-api
>    Affects Versions: 1.99.5
>            Reporter: Abraham Elmahrek
>            Assignee: Abraham Elmahrek
>             Fix For: 1.99.6
>
>         Attachments: SQOOP-2162.0.patch
>
>
> Currently, it is not optional. The following JSON request will throw an exception:
> {code:type=json}
> {
>     "id": -1,
>     "inputs": [
>         {
>             "id": -1,
>             "name": "Enum",
>             "overrides": "",
>             "sensitive": false,
>             "type": "ENUM",
>             "value": "YES",
>             "values": "YES,NO"
>         }
>     ],
>     "name": "c",
>     "type": "JOB"
> }
> {code}
> This breaks backwards compatibiltiy of our APIs. This Jira should fix that by providing
a default value.



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

Mime
View raw message