[
https://issues.apache.org/jira/browse/IGNITE-16487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-16487:
-----------------------------------
Reviewer: Aleksandr Polovtcev
> Use PATCH HTTP verb instead of PUT for modifying cluster/node configuration
> ---------------------------------------------------------------------------
>
> Key: IGNITE-16487
> URL: https://issues.apache.org/jira/browse/IGNITE-16487
> Project: Ignite
> Issue Type: Improvement
> Components: rest
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, both /management/v1/configuration/node/ andÂ
> /management/v1/configuration/cluster/ are bound to PUT for modification of
> the configuration.
> In RESTful APIs, PUT usually performs a complete replacement of an entity
> (see
> [https://hub.packtpub.com/what-are-rest-verbs-and-status-codes-tutorial/] ),
> but in our case the configuration is actually patched (the client passes a
> diff, not the complete configuration).
> So it makes sense to use PATCH verb instead of PUT.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
