You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/03/08 08:54:00 UTC

[jira] [Commented] (ATLAS-3976) On creating a type with a type_name that already exists as a read-only user 409 is thrown instead on 403

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

ASF subversion and git services commented on ATLAS-3976:
--------------------------------------------------------

Commit 12e35d2f15578619b6375c37dc2087cc3e1e6cce in atlas's branch refs/heads/master from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=12e35d2 ]

ATLAS-3976 : On creating a type with a type_name that already exists as a read-only user 409 is thrown instead on 403


> On creating a type with a type_name  that already exists as a read-only user 409 is thrown instead on 403
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-3976
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3976
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Dharshana M Krishnamoorthy
>            Assignee: chaitali borole
>            Priority: Major
>
> hrt_qa has crud permission on business_metadata
> bm_1 is created by hrt_qa
> hrt_1 has read-only permission on business_metadata bm_1
> When hrt_1 is trying to create bm_1 again, since hrt_1 is a read-only user 403 unauthorised should be thrown, instead 409 conflict is thrown



--
This message was sent by Atlassian Jira
(v8.3.4#803005)