Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Sat, 9 Aug 2014 18:58:13 +0000 (UTC)
From: "Zhijie Shen (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12733051.1407610670327.49803.1407610693466@arcas>
In-Reply-To: <JIRA.12733051.1407610670327@arcas>
References: <JIRA.12733051.1407610670327@arcas>
Subject: [jira] [Created] (YARN-2401) Rethinking of the HTTP method of
 TimelineWebServices#postEntities
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Zhijie Shen created YARN-2401:
---------------------------------

             Summary: Rethinking of the HTTP method of TimelineWebServices#postEntities
                 Key: YARN-2401
                 URL: https://issues.apache.org/jira/browse/YARN-2401
             Project: Hadoop YARN
          Issue Type: Sub-task
          Components: timelineserver
            Reporter: Zhijie Shen
            Assignee: Zhijie Shen


Now TimelineWebServices#postEntities is using POST. However, semantically, postEntities is creating an entity or append more data into it. POST may not be the most proper method to for this API.

AFAIK, PUT is used to update the entire resource and supposed to be idempotent. Therefore, I'm not sure it's an idea to change the method to PUT because once the entity is created, the following updates are actually appending more data to the existing one. The best fit should be PATCH, however, it requires the additional implementation at the web services side. Hence, somebody online suggested using POST for partial non-idempotent update as well. We need to think more about it.


--
This message was sent by Atlassian JIRA
(v6.2#6252)