[jira] [Updated] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work
[ https://issues.apache.org/jira/browse/ATLAS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3978: --- Attachment: ATLAS-3978.patch > In Administration, Audits filter for 'OR' condition does not work > - > > Key: ATLAS-3978 > URL: https://issues.apache.org/jira/browse/ATLAS-3978 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3978.patch, OR condition not working.mkv > > > Description:: > When user uses OR condition it does not apply on filter, results are listed > with AND condition. PFA evidence file [OR condition not working.mkv] > Steps to regenerate:: > # Go to Administration- Audits > # Select the OR condition filter > # Check the console for response > # Results are listed with 'AND' operator instead of 'OR' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3986) UI Allow user to update the date format from JAVA property file
[ https://issues.apache.org/jira/browse/ATLAS-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3986: --- Summary: UI Allow user to update the date format from JAVA property file (was: UI Allow user to update the date format from JAVA properties file) > UI Allow user to update the date format from JAVA property file > --- > > Key: ATLAS-3986 > URL: https://issues.apache.org/jira/browse/ATLAS-3986 > Project: Atlas > Issue Type: Sub-task >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3986) UI Allow user to update the date format from JAVA properties file
[ https://issues.apache.org/jira/browse/ATLAS-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3986: --- Fix Version/s: 2.2.0 3.0.0 > UI Allow user to update the date format from JAVA properties file > - > > Key: ATLAS-3986 > URL: https://issues.apache.org/jira/browse/ATLAS-3986 > Project: Atlas > Issue Type: Sub-task >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3986) UI Allow user to update the date format from JAVA properties file
Keval Bhatt created ATLAS-3986: -- Summary: UI Allow user to update the date format from JAVA properties file Key: ATLAS-3986 URL: https://issues.apache.org/jira/browse/ATLAS-3986 Project: Atlas Issue Type: Sub-task Reporter: Keval Bhatt Assignee: Keval Bhatt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3361) UI: improve Lineage, Relationship graph position changes
[ https://issues.apache.org/jira/browse/ATLAS-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt resolved ATLAS-3361. Resolution: Invalid > UI: improve Lineage, Relationship graph position changes > > > Key: ATLAS-3361 > URL: https://issues.apache.org/jira/browse/ATLAS-3361 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210120#comment-17210120 ] Keval Bhatt commented on ATLAS-3692: The issue is fixed by ATLAS-3964. > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3692: --- Fix Version/s: 2.2.0 3.0.0 > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt resolved ATLAS-3692. Resolution: Fixed > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Major > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3692: --- Parent: (was: ATLAS-3964) Issue Type: Bug (was: Sub-task) > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3692: --- Parent: ATLAS-3964 Issue Type: Sub-task (was: Bug) > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Major > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3979) Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name.
[ https://issues.apache.org/jira/browse/ATLAS-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210115#comment-17210115 ] ASF subversion and git services commented on ATLAS-3979: Commit 58d630bf19540710a36ec47ee9fdfd771aafa5b7 in atlas's branch refs/heads/branch-2.0 from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=58d630b ] ATLAS-3979: Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name. (cherry picked from commit 70c1087a121feb3fe88cc67681b470109443ff81) > Beta UI : Removing one of the filters with an attribute name removes all of > the filters with that attribute name. > - > > Key: ATLAS-3979 > URL: https://issues.apache.org/jira/browse/ATLAS-3979 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3979.patch > > > Create a basic search with filters: > typename = _ALL_ENTITY_TYPES > filters: > _classificationNames = tag1 and > _classificationNames = tag2 and > _createdBy = hive > Fire Search. > From UI , remove "_classificationNames = tag1" filter . > This removes "_classificationNames = tag2" filter too since the attribute > name _classificationNames is same. > Other attribute _createdBy is intact. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3981) UI: Create Entity button is shown for a user without create entity permission in ranger
[ https://issues.apache.org/jira/browse/ATLAS-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210114#comment-17210114 ] ASF subversion and git services commented on ATLAS-3981: Commit ba8b490cd192b497d3bc4996f68e016814a92fbb in atlas's branch refs/heads/branch-2.0 from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ba8b490 ] ATLAS-3981: UI: Create Entity button is shown for a user without create entity permission in ranger (cherry picked from commit f5ffd06486f6ef3c28236c6c70e74561542d30c1) > UI: Create Entity button is shown for a user without create entity permission > in ranger > --- > > Key: ATLAS-3981 > URL: https://issues.apache.org/jira/browse/ATLAS-3981 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3981.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3979) Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name.
[ https://issues.apache.org/jira/browse/ATLAS-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210113#comment-17210113 ] ASF subversion and git services commented on ATLAS-3979: Commit 70c1087a121feb3fe88cc67681b470109443ff81 in atlas's branch refs/heads/master from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=70c1087 ] ATLAS-3979: Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name. > Beta UI : Removing one of the filters with an attribute name removes all of > the filters with that attribute name. > - > > Key: ATLAS-3979 > URL: https://issues.apache.org/jira/browse/ATLAS-3979 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3979.patch > > > Create a basic search with filters: > typename = _ALL_ENTITY_TYPES > filters: > _classificationNames = tag1 and > _classificationNames = tag2 and > _createdBy = hive > Fire Search. > From UI , remove "_classificationNames = tag1" filter . > This removes "_classificationNames = tag2" filter too since the attribute > name _classificationNames is same. > Other attribute _createdBy is intact. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3981) UI: Create Entity button is shown for a user without create entity permission in ranger
[ https://issues.apache.org/jira/browse/ATLAS-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210112#comment-17210112 ] ASF subversion and git services commented on ATLAS-3981: Commit f5ffd06486f6ef3c28236c6c70e74561542d30c1 in atlas's branch refs/heads/master from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f5ffd06 ] ATLAS-3981: UI: Create Entity button is shown for a user without create entity permission in ranger > UI: Create Entity button is shown for a user without create entity permission > in ranger > --- > > Key: ATLAS-3981 > URL: https://issues.apache.org/jira/browse/ATLAS-3981 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3981.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3979) Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name.
[ https://issues.apache.org/jira/browse/ATLAS-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210105#comment-17210105 ] Durga Kadam commented on ATLAS-3979: +1 > Beta UI : Removing one of the filters with an attribute name removes all of > the filters with that attribute name. > - > > Key: ATLAS-3979 > URL: https://issues.apache.org/jira/browse/ATLAS-3979 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3979.patch > > > Create a basic search with filters: > typename = _ALL_ENTITY_TYPES > filters: > _classificationNames = tag1 and > _classificationNames = tag2 and > _createdBy = hive > Fire Search. > From UI , remove "_classificationNames = tag1" filter . > This removes "_classificationNames = tag2" filter too since the attribute > name _classificationNames is same. > Other attribute _createdBy is intact. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3981) UI: Create Entity button is shown for a user without create entity permission in ranger
[ https://issues.apache.org/jira/browse/ATLAS-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210073#comment-17210073 ] Durga Kadam commented on ATLAS-3981: +1 > UI: Create Entity button is shown for a user without create entity permission > in ranger > --- > > Key: ATLAS-3981 > URL: https://issues.apache.org/jira/browse/ATLAS-3981 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3981.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work
[ https://issues.apache.org/jira/browse/ATLAS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3978: --- Fix Version/s: 2.2.0 3.0.0 > In Administration, Audits filter for 'OR' condition does not work > - > > Key: ATLAS-3978 > URL: https://issues.apache.org/jira/browse/ATLAS-3978 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: OR condition not working.mkv > > > Description:: > When user uses OR condition it does not apply on filter, results are listed > with AND condition. PFA evidence file [OR condition not working.mkv] > Steps to regenerate:: > # Go to Administration- Audits > # Select the OR condition filter > # Check the console for response > # Results are listed with 'AND' operator instead of 'OR' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3971) Move authorization check for Business Metadata before type exist check
[ https://issues.apache.org/jira/browse/ATLAS-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-3971. Fix Version/s: 2.2.0 3.0.0 Resolution: Fixed > Move authorization check for Business Metadata before type exist check > -- > > Key: ATLAS-3971 > URL: https://issues.apache.org/jira/browse/ATLAS-3971 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3971.patch > > > Refactor authorization check for Business Metadata before type exist check, > so that enduser is aware that a duplicate type creation is being attempted > which exist he is authorized to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3971) Move authorization check for Business Metadata before type exist check
[ https://issues.apache.org/jira/browse/ATLAS-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210037#comment-17210037 ] ASF subversion and git services commented on ATLAS-3971: Commit 92b70715e0bf50fe7c3dcc5227182202f8fe0c6e in atlas's branch refs/heads/branch-2.0 from Nixon Rodrigues [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=92b7071 ] ATLAS-3971 :- Move authorization check for Business Metadata before type exist check. (cherry picked from commit 8098bc5643cd45f53d2d9284785693a406d8a270) > Move authorization check for Business Metadata before type exist check > -- > > Key: ATLAS-3971 > URL: https://issues.apache.org/jira/browse/ATLAS-3971 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Attachments: ATLAS-3971.patch > > > Refactor authorization check for Business Metadata before type exist check, > so that enduser is aware that a duplicate type creation is being attempted > which exist he is authorized to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3971) Move authorization check for Business Metadata before type exist check
[ https://issues.apache.org/jira/browse/ATLAS-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210034#comment-17210034 ] ASF subversion and git services commented on ATLAS-3971: Commit 8098bc5643cd45f53d2d9284785693a406d8a270 in atlas's branch refs/heads/master from Nixon Rodrigues [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8098bc5 ] ATLAS-3971 :- Move authorization check for Business Metadata before type exist check. > Move authorization check for Business Metadata before type exist check > -- > > Key: ATLAS-3971 > URL: https://issues.apache.org/jira/browse/ATLAS-3971 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Attachments: ATLAS-3971.patch > > > Refactor authorization check for Business Metadata before type exist check, > so that enduser is aware that a duplicate type creation is being attempted > which exist he is authorized to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3985) Not able to assign classification with mandatory attribute of type "array"
Dharshana M Krishnamoorthy created ATLAS-3985:
-
Summary: Not able to assign classification with mandatory
attribute of type "array"
Key: ATLAS-3985
URL: https://issues.apache.org/jira/browse/ATLAS-3985
Project: Atlas
Issue Type: Bug
Components: atlas-core, atlas-webui
Reporter: Dharshana M Krishnamoorthy
Attachments: Screenshot 2020-10-07 at 1.40.43 PM.png, Screenshot
2020-10-07 at 1.41.17 PM.png
Create a classification that has mandatory attribute of type "*array*"
via REST api
{code:java|title=Create classification with payload:}
{
"enumDefs": [],
"structDefs": [],
"classificationDefs": [
{
"category": "CLASSIFICATION",
"guid": "8996315b-b5fe-48c6-b9d0-4668fhkfd21af",
"createdBy": "hrt_qa",
"updatedBy": "hrt_qa",
"createTime": 1602057743077,
"updateTime": 1602057743077,
"version": 1,
"name": "read_auth_test_tag1",
"description": "read_auth_test_tag1",
"typeVersion": "1.0",
"attributeDefs": [
{
"name": "type_long_min",
"typeName": "long",
"isOptional": true,
"cardinality": "SINGLE",
"valuesMinCount": 0,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": false
},
{
"name":"type_arr_list",
"typeName":"array",
"isOptional":false,
"cardinality":"LIST",
"valuesMinCount":1,
"valuesMaxCount":2147483647,
"isUnique":false,
"isIndexable":false
},
{
"name":"type_set",
"typeName":"array",
"isOptional":false,
"cardinality":"SET",
"valuesMinCount":1,
"valuesMaxCount":2147483647,
"isUnique":false,
"isIndexable":false
}
],
"superTypes": [],
"entityTypes": [],
"subTypes": []
}
],
"entityDefs": [],
"relationshipDefs": [],
"businessMetadataDefs": []
}
{code}
Assign the same to an entity.
The assignment fails as the attributes of type "array" are not visible
on UI
{code:java|title=error message}
{"errorCode":"ATLAS-400-00-01A",
"errorMessage":"invalid parameters: read_auth_test_tag1.type_arr_list:
mandatory attribute value missing in type read_auth_test_tag1"}
{code}
The assignment fails via both UI and rest api.
In UI creation of attribute of such a type is not allowed but via rest api it
is possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Dharshana M Krishnamoorthy updated ATLAS-3976: -- Description: 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 was: hrt_qa has crud permission on classification PII is created by hrt_qa hrt_1 has read-only permission on classification PII When hrt_1 is trying to create PII again, since its a read-only user 403- unauthorised to create should be thrown, instead 409 conflict is thrown > 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: Nixon Rodrigues >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)
