You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Ramachandran (Jira)" <ji...@apache.org> on 2023/03/01 03:42:00 UTC

[jira] [Commented] (RANGER-4112) Update servicedef by name results in 400 status code while the same request works with update servicedef using id

    [ https://issues.apache.org/jira/browse/RANGER-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694836#comment-17694836 ] 

Ramachandran commented on RANGER-4112:
--------------------------------------

[~pradeep] 

It is a miss from our side not intentional. As part of UT, i should have added the negative Test case to get this issue.

> Update servicedef by name results in 400 status code while the same request works with update servicedef using id
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-4112
>                 URL: https://issues.apache.org/jira/browse/RANGER-4112
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: Abhishek
>            Assignee: Pradeep Agrawal
>            Priority: Major
>             Fix For: 3.0.0, 2.4.0
>
>         Attachments: 0001-RANGER-4112-Update-servicedef-by-name-results-in-400.patch, Screenshot 2023-02-28 at 3.21.18 PM.png
>
>
> {color:#172b4d}If a PUT request is made to update the servicedef by id (BASE_URL/service/public/v2/api/servicedef/id), the request passes,{color}
> {color:#172b4d}but if the same PUT request is made to update the servicedef by name (BASE_URL/service/public/v2/api/servicedef/name/\{servicedef_name}), then it results in 400 Bad request.{color}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)