Varun Vasudev updated YARN-1713:

    Attachment: apache-yarn-1713.7.patch

bq.    RMWebServices.submitNewApplication > submitApplication


bq.    We need a GetNewApplication API similar to the one in RPC


bq.    Can we keep the validation logic same for RPCs and web-services? You 
have additional checks in web-services that don't quite exist in RPCs.

Fixed. All validation is done by the ClientRMService. Turns out we didn't need 
the additional checks in the web services code.

    Can we name the json objects to be closer to the RPC object names?
    Can we match the XML element names to either match the RPC level objects or 
the json objects? Consistency with one set or the other.


I've updated the ContainerLaunchContextInfo to better address the passing of 
credentials. Let me know your thoughts.

I haven't updated the docs in this patch. Once the patch it approved I'll 
upload a final patch with the docs updated.

> Implement getnewapplication and submitapp as part of RM web service
> -------------------------------------------------------------------
>                 Key: YARN-1713
>                 URL: https://issues.apache.org/jira/browse/YARN-1713
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Varun Vasudev
>            Assignee: Varun Vasudev
>         Attachments: apache-yarn-1713.3.patch, apache-yarn-1713.4.patch, 
> apache-yarn-1713.5.patch, apache-yarn-1713.6.patch, apache-yarn-1713.7.patch, 
> apache-yarn-1713.cumulative.2.patch, apache-yarn-1713.cumulative.3.patch, 
> apache-yarn-1713.cumulative.4.patch, apache-yarn-1713.cumulative.patch, 
> apache-yarn-1713.patch

This message was sent by Atlassian JIRA

Reply via email to