[jira] [Commented] (ATLAS-4225) Support for Chinese character in entity data.
[ https://issues.apache.org/jira/browse/ATLAS-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841448#comment-17841448 ] chaitali borole commented on ATLAS-4225: In below case this above patch won't work : Description field contains "THIS IS DESCRIPTION FIELD". Now, if we search for each word separately, i.e., (THIS, IS, DESCRIPTION, or FIELD), we will get the output. However, if we search for "THIS IS" or "DESCRIPTION FIELD", it will not work as the space acts as a delimiter here. So (THIS - 1st Token) (IS 2nd Token) and so on.. Similarly, in the case of CJK, "期日" each character is a token. So, if we search for "期", we will get the response or if we search for "日", we will get the response. However, if we search for "期日" together, we will not get an answer. though this works as per design similar to English characters. > Support for Chinese character in entity data. > - > > Key: ATLAS-4225 > URL: https://issues.apache.org/jira/browse/ATLAS-4225 > Project: Atlas > Issue Type: New Feature >Reporter: Mayank Jain >Assignee: chaitali borole >Priority: Major > Attachments: ATLAS-4225-3.patch > > > Currently we only allow English characters to be used to adding entity data > that is labels , Custom Attributes and Business-Metadata. > > We need to support for Chinese and other languages as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4225) Support for Chinese character in entity data.
[ https://issues.apache.org/jira/browse/ATLAS-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4225: -- Assignee: chaitali borole (was: Mayank Jain) > Support for Chinese character in entity data. > - > > Key: ATLAS-4225 > URL: https://issues.apache.org/jira/browse/ATLAS-4225 > Project: Atlas > Issue Type: New Feature >Reporter: Mayank Jain >Assignee: chaitali borole >Priority: Major > Attachments: ATLAS-4225-3.patch > > > Currently we only allow English characters to be used to adding entity data > that is labels , Custom Attributes and Business-Metadata. > > We need to support for Chinese and other languages as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4833) Export/Import : When relationship is updated to block tag , the imported lineage doesn't have the updated relationship
[
https://issues.apache.org/jira/browse/ATLAS-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4833:
--
Assignee: chaitali borole
> Export/Import : When relationship is updated to block tag , the imported
> lineage doesn't have the updated relationship
> --
>
> Key: ATLAS-4833
> URL: https://issues.apache.org/jira/browse/ATLAS-4833
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Sharmadha S
>Assignee: chaitali borole
>Priority: Major
>
> _+*PROBLEM STATEMENT:*+_
> Export/Import : When relationship is updated to block tag , the imported
> lineage doesn't have the updated relationship
>
> _+*STEPS TO REPRODUCE:*+_
> # In cluster1 create lineage as the following:
> # table1 -{-}(edge1){-}{-}> process1{-} {-}(edge2){-}-> table2
> # Update edge1 relationship - set propagation from table to process as None
> # Add tag to table1 , the tag is not propagated to process1 and table2
> # Now export the table2 entity to cluster2
> # In cluster2, process2 and table2 have the tag propagated from table1
>
> _+*CURRENT BEHAVIOUR:*+_
> edge1 relationship in cluster2 doesn't have the propagation blocked.
>
> _+*EXPECTED BEHAVIOUR:*+_
> edge1 relationship in cluster2 should have the propagation blocked.
>
> _+*OCCURRENCE:*+_
> Consistently reproducible.
>
> _+*HISTORY OF FAILURE:*+_
> Test case added newly
>
> _+*IMPACT:*+_
> Security issue at customer
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4802) Atlas 'updateTime' parameter is not updated when business metadata, labels is edited.
[
https://issues.apache.org/jira/browse/ATLAS-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole updated ATLAS-4802:
---
Summary: Atlas 'updateTime' parameter is not updated when business
metadata, labels is edited. (was: Atlas 'updateTime' parameter is not updated
when business metadata is edited.)
> Atlas 'updateTime' parameter is not updated when business metadata, labels is
> edited.
> -
>
> Key: ATLAS-4802
> URL: https://issues.apache.org/jira/browse/ATLAS-4802
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> When updating the business metadata on an atlas entity, the 'updateTime'
> system attribute is not changed.
> Updates to other aspects, such as technical properties and user defined
> attributes does update the timestamp, but not the business metadata.
> This appears to be a issue with the core Atlas product.
> curl -u admin:hadoop12345! -X GET --header 'Content-Type:
> application/json;charset=UTF-8'
> "http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
> {"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
>
> deserializer","position":3,"type":"string","table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table"}},"guid":"5b4e426e-404f-4a10-abab-f0b3879c0acb","isIncomplete":false,"status":"ACTIVE","createdBy":"hive","updatedBy":"hive","createTime":1697203083822,"updateTime":1697203083822,"version":0,"relationshipAttributes":{"inputToProcesses":[],"pipeline":null,"schema":[],"model":null,"meanings":[],"table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table","entityStatus":"ACTIVE","displayText":"mv_creation_metadata","relationshipType":"hive_table_columns","relationshipGuid":"39f22e08-8ff2-4bd3-9a2f-9e2efce69fba","relationshipStatus":"ACTIVE","relationshipAttributes":{"typeName":"hive_table_columns"}},"outputFromProcesses":[]},"labels":[]}}
>
> After adding business metadata "text : value1" to the entity txn_list
> (hive_column),
>
> curl -u admin:hadoop12345! -X GET --header 'Content-Type:
> application/json;charset=UTF-8'
> "http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
> {"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
>
> deserializer","position":3,"type":"string","table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table"}},"guid":"5b4e426e-404f-4a10-abab-f0b3879c0acb","isIncomplete":false,"status":"ACTIVE","createdBy":"hive","updatedBy":"hive","createTime":1697203083822,"updateTime":1697203083822,"version":0,"relationshipAttributes":{"inputToProcesses":[],"pipeline":null,"schema":[],"model":null,"meanings":[],"table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table","entityStatus":"ACTIVE","displayText":"mv_creation_metadata","relationshipType":"hive_table_columns","relationshipGuid":"39f22e08-8ff2-4bd3-9a2f-9e2efce69fba","relationshipStatus":"ACTIVE","relationshipAttributes":{"typeName":"hive_table_columns"}},"outputFromProcesses":[]},"businessAttributes":{"demo":{"text":"value1"}},"labels":[]}}
>
> As seen "updateTime":1697203083822 still remains the same.
> However, if we add an user-defined property "age : 20",
>
> curl -u admin:hadoop12345! -X GET --header 'Content-Type:
> application/json;charset=UTF-8'
> "http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
> {"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
>
>
[jira] [Commented] (ATLAS-4225) Support for Chinese character in entity data.
[ https://issues.apache.org/jira/browse/ATLAS-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823133#comment-17823133 ] chaitali borole commented on ATLAS-4225: creating a new RR with patch which is in sync with latest code. https://reviews.apache.org/r/74925/ > Support for Chinese character in entity data. > - > > Key: ATLAS-4225 > URL: https://issues.apache.org/jira/browse/ATLAS-4225 > Project: Atlas > Issue Type: New Feature >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > Attachments: ATLAS-4225-3.patch > > > Currently we only allow English characters to be used to adding entity data > that is labels , Custom Attributes and Business-Metadata. > > We need to support for Chinese and other languages as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4788) Encrpytion of clear text kafka password in application.properties
[ https://issues.apache.org/jira/browse/ATLAS-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4788: --- Summary: Encrpytion of clear text kafka password in application.properties (was: Encrpytion of kafka password in ap+plication.properties) > Encrpytion of clear text kafka password in application.properties > -- > > Key: ATLAS-4788 > URL: https://issues.apache.org/jira/browse/ATLAS-4788 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > atlas.jaas.KafkaClient.option.username=username > atlas.jaas.KafkaClient.option.password= > We have to encrypt this passsword using jceks file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4788) Encrpytion of kafka password in ap+plication.properties
[ https://issues.apache.org/jira/browse/ATLAS-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4788: --- Summary: Encrpytion of kafka password in ap+plication.properties (was: Kafka password is in clear text in application.properties) > Encrpytion of kafka password in ap+plication.properties > --- > > Key: ATLAS-4788 > URL: https://issues.apache.org/jira/browse/ATLAS-4788 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > atlas.jaas.KafkaClient.option.username=username > atlas.jaas.KafkaClient.option.password= > We have to encrypt this passsword using jceks file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4802) Atlas 'updateTime' parameter is not updated when business metadata is edited.
chaitali borole created ATLAS-4802:
--
Summary: Atlas 'updateTime' parameter is not updated when business
metadata is edited.
Key: ATLAS-4802
URL: https://issues.apache.org/jira/browse/ATLAS-4802
Project: Atlas
Issue Type: Improvement
Components: atlas-core
Affects Versions: 3.0.0
Reporter: chaitali borole
Assignee: chaitali borole
When updating the business metadata on an atlas entity, the 'updateTime' system
attribute is not changed.
Updates to other aspects, such as technical properties and user defined
attributes does update the timestamp, but not the business metadata.
This appears to be a issue with the core Atlas product.
curl -u admin:hadoop12345! -X GET --header 'Content-Type:
application/json;charset=UTF-8'
"http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
{"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
deserializer","position":3,"type":"string","table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table"}},"guid":"5b4e426e-404f-4a10-abab-f0b3879c0acb","isIncomplete":false,"status":"ACTIVE","createdBy":"hive","updatedBy":"hive","createTime":1697203083822,"updateTime":1697203083822,"version":0,"relationshipAttributes":{"inputToProcesses":[],"pipeline":null,"schema":[],"model":null,"meanings":[],"table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table","entityStatus":"ACTIVE","displayText":"mv_creation_metadata","relationshipType":"hive_table_columns","relationshipGuid":"39f22e08-8ff2-4bd3-9a2f-9e2efce69fba","relationshipStatus":"ACTIVE","relationshipAttributes":{"typeName":"hive_table_columns"}},"outputFromProcesses":[]},"labels":[]}}
After adding business metadata "text : value1" to the entity txn_list
(hive_column),
curl -u admin:hadoop12345! -X GET --header 'Content-Type:
application/json;charset=UTF-8'
"http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
{"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
deserializer","position":3,"type":"string","table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table"}},"guid":"5b4e426e-404f-4a10-abab-f0b3879c0acb","isIncomplete":false,"status":"ACTIVE","createdBy":"hive","updatedBy":"hive","createTime":1697203083822,"updateTime":1697203083822,"version":0,"relationshipAttributes":{"inputToProcesses":[],"pipeline":null,"schema":[],"model":null,"meanings":[],"table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table","entityStatus":"ACTIVE","displayText":"mv_creation_metadata","relationshipType":"hive_table_columns","relationshipGuid":"39f22e08-8ff2-4bd3-9a2f-9e2efce69fba","relationshipStatus":"ACTIVE","relationshipAttributes":{"typeName":"hive_table_columns"}},"outputFromProcesses":[]},"businessAttributes":{"demo":{"text":"value1"}},"labels":[]}}
As seen "updateTime":1697203083822 still remains the same.
However, if we add an user-defined property "age : 20",
curl -u admin:hadoop12345! -X GET --header 'Content-Type:
application/json;charset=UTF-8'
"http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
{"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
deserializer","position":3,"type":"string","table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table"}},"guid":"5b4e426e-404f-4a10-abab-f0b3879c0acb","isIncomplete":false,"status":"ACTIVE","createdBy":"hive","updatedBy":"admin","createTime":1697203083822,"updateTime":1697203987465,"version":0,"relationshipAttributes":{"inputToProcesses":[],"pipeline":null,"schema":[],"model":null,"meanings":[],"table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table","entityStatus":"ACTIVE","displayText":"mv_creation_metadata","relationshipType":"hive_table_columns","relationshipGuid":"39f22e08-8ff2-4bd3-9a2f-9e2efce69fba","relationshipStatus":"ACTIVE","relationshipAttributes":{"typeName":"hive_table_columns"}},"outputFromProcesses":[]},"customAttributes":{"age":"20"},"businessAttributes":{"demo":{"text":"value1"}},"labels":[]}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4788) Kafka password is in clear text in application.properties
[ https://issues.apache.org/jira/browse/ATLAS-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4788: --- Summary: Kafka password is in clear text in application.properties (was: Kafka pass is in clear text in application.properties) > Kafka password is in clear text in application.properties > - > > Key: ATLAS-4788 > URL: https://issues.apache.org/jira/browse/ATLAS-4788 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > atlas.jaas.KafkaClient.option.username=username > atlas.jaas.KafkaClient.option.password= > We have to encrypt this passsword using jceks file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4788) Kafka pass is in clear text in application.properties
chaitali borole created ATLAS-4788: -- Summary: Kafka pass is in clear text in application.properties Key: ATLAS-4788 URL: https://issues.apache.org/jira/browse/ATLAS-4788 Project: Atlas Issue Type: Improvement Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Fix For: 3.0.0 atlas.jaas.KafkaClient.option.username=username atlas.jaas.KafkaClient.option.password= We have to encrypt this passsword using jceks file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4757) Regression : DSL queries redirected to passive server fails
chaitali borole created ATLAS-4757:
--
Summary: Regression : DSL queries redirected to passive server
fails
Key: ATLAS-4757
URL: https://issues.apache.org/jira/browse/ATLAS-4757
Project: Atlas
Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: chaitali borole
Assignee: chaitali borole
When redirected query is encoded as below
http://localhost:21000/api/atlas/v2/search/dsl?typeName=hive_table=name=%2522table_a_impala_avwei_20%2522
this fails with below error :
{ "errorCode": "ATLAS-400-00-059", "errorMessage": "Invalid DSL query:
`hive_table` name=%22table_a_impala_avwei_20%22 limit 100 offset 0 | Reason:
DSL Semantic Error - table_a_impala_avwei_20 type not found, DSL Semantic Error
- table_a_impala_avwei_20 type not found, DSL Semantic Error - 22 type not
found, DSL Semantic Error - 22 type not found. Please refer to Atlas DSL
grammar for more information"}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4756) Entity_update should be sent after classification is deleted and added from ctas and parent
[ https://issues.apache.org/jira/browse/ATLAS-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4756: --- Summary: Entity_update should be sent after classification is deleted and added from ctas and parent (was: Atlas is not passing ENTITY_UPDATE notification to Tagsync on classification delete) > Entity_update should be sent after classification is deleted and added from > ctas and parent > --- > > Key: ATLAS-4756 > URL: https://issues.apache.org/jira/browse/ATLAS-4756 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > ENTITY_UPDATE notification from ATLAS is expected for below scenarios: > 1. When classification is propagated from parent table to CTAS. > 2. When only propagation is removed from CTAS. > 3. When classification is removed from parent. > 4.When Parent table or CTAS table is dropped. > Currently when deferred action is enabled CLASSIFICATION_ADD, > CLASSIFICATION_DELETE notification message sent is incorrect. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4756) Atlas is not passing ENTITY_UPDATE notification to Tagsync on classification delete
chaitali borole created ATLAS-4756: -- Summary: Atlas is not passing ENTITY_UPDATE notification to Tagsync on classification delete Key: ATLAS-4756 URL: https://issues.apache.org/jira/browse/ATLAS-4756 Project: Atlas Issue Type: Improvement Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole ENTITY_UPDATE notification from ATLAS is expected for below scenarios: 1. When classification is propagated from parent table to CTAS. 2. When only propagation is removed from CTAS. 3. When classification is removed from parent. 4.When Parent table or CTAS table is dropped. Currently when deferred action is enabled CLASSIFICATION_ADD, CLASSIFICATION_DELETE notification message sent is incorrect. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4717) When user doesn't have CRUD permission on classification , classification tag is still shown on detailsPage
[ https://issues.apache.org/jira/browse/ATLAS-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4717: --- Description: https://issues.apache.org/jira/browse/ATLAS-4717 Create tag - ptag Associate ptag to entity e1 in detailsPage of entity e1 , tag is visible. For user admin Deny permissions to create , read , update , delete classification types. Visit entity e1 as admin user. So here classification is still visible when associated with entities on search page as well as details page Only classification under the classifications tab on UI are hidden. was: Create tag - ptag Create tag - ctag with parent tag as ptag Associate ctag to entity e1 in detailsPage of entity e1 , ctag@ptag is seen. For user admin Deny permissions to create , read , update , delete classification types. Visit entity e1 as admin user. Now only ctag is seen instead of ctag@ptag When search page is loaded after the deny policy we cannot access entity As entitydef is empty in the response > When user doesn't have CRUD permission on classification , classification tag > is still shown on detailsPage > --- > > Key: ATLAS-4717 > URL: https://issues.apache.org/jira/browse/ATLAS-4717 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > https://issues.apache.org/jira/browse/ATLAS-4717 > Create tag - ptag > Associate ptag to entity e1 > in detailsPage of entity e1 , tag is visible. > For user admin > Deny permissions to create , read , update , delete classification types. > Visit entity e1 as admin user. > So here classification is still visible when associated with entities on > search page as well as details page > Only classification under the classifications tab on UI are hidden. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4717) When user doesn't have CRUD permission on classification , classification tag is still shown on detailsPage
[ https://issues.apache.org/jira/browse/ATLAS-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4717: --- Description: Create tag - ptag Create tag - ctag with parent tag as ptag Associate ctag to entity e1 in detailsPage of entity e1 , ctag@ptag is seen. For user admin Deny permissions to create , read , update , delete classification types. Visit entity e1 as admin user. Now only ctag is seen instead of ctag@ptag When search page is loaded after the deny policy we cannot access entity As entitydef is empty in the response was: Create tag - ptag Create tag - ctag with parent tag as ptag Associate ctag to entity e1 in detailsPage of entity e1 , ctag@ptag is seen. For user admin Deny permissions to create , read , update , delete classification types. Visit entity e1 as admin user. Now only ctag is seen instead of ctag@ptag > When user doesn't have CRUD permission on classification , classification tag > is still shown on detailsPage > --- > > Key: ATLAS-4717 > URL: https://issues.apache.org/jira/browse/ATLAS-4717 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Create tag - ptag > Create tag - ctag with parent tag as ptag > Associate ctag to entity e1 > in detailsPage of entity e1 , ctag@ptag is seen. > For user admin > Deny permissions to create , read , update , delete classification types. > Visit entity e1 as admin user. > Now only ctag is seen instead of ctag@ptag > When search page is loaded after the deny policy we cannot access entity > As entitydef is empty in the response -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4717) When user doesn't have CRUD permission on classification , classification tag is still shown on detailsPage
chaitali borole created ATLAS-4717: -- Summary: When user doesn't have CRUD permission on classification , classification tag is still shown on detailsPage Key: ATLAS-4717 URL: https://issues.apache.org/jira/browse/ATLAS-4717 Project: Atlas Issue Type: Improvement Reporter: chaitali borole Assignee: chaitali borole Create tag - ptag Create tag - ctag with parent tag as ptag Associate ctag to entity e1 in detailsPage of entity e1 , ctag@ptag is seen. For user admin Deny permissions to create , read , update , delete classification types. Visit entity e1 as admin user. Now only ctag is seen instead of ctag@ptag -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-3403) Term assigned to historical entity is not visible in Search results page.
[ https://issues.apache.org/jira/browse/ATLAS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3403: --- Fix Version/s: 3.0.0 > Term assigned to historical entity is not visible in Search results page. > - > > Key: ATLAS-3403 > URL: https://issues.apache.org/jira/browse/ATLAS-3403 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Rahul Kurup >Assignee: chaitali borole >Priority: Minor > Fix For: 3.0.0 > > > Let us consider that a classification and a term has been assigned to an > entity. > If that entity is deleted, and then when the "Show Historical Entities" > filter is enabled on the search results page for that entity, the > classification is displayed but not the term. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-3403) Term assigned to historical entity is not visible in Search results page.
[ https://issues.apache.org/jira/browse/ATLAS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3403: --- Affects Version/s: 3.0.0 > Term assigned to historical entity is not visible in Search results page. > - > > Key: ATLAS-3403 > URL: https://issues.apache.org/jira/browse/ATLAS-3403 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Rahul Kurup >Assignee: chaitali borole >Priority: Minor > > Let us consider that a classification and a term has been assigned to an > entity. > If that entity is deleted, and then when the "Show Historical Entities" > filter is enabled on the search results page for that entity, the > classification is displayed but not the term. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4697) Upgrade Jackson version to 2.12.7.1
chaitali borole created ATLAS-4697: -- Summary: Upgrade Jackson version to 2.12.7.1 Key: ATLAS-4697 URL: https://issues.apache.org/jira/browse/ATLAS-4697 Project: Atlas Issue Type: Improvement Affects Versions: 2.1.0, 3.0.0 Reporter: chaitali borole Current jackson-databind version is 2.11.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4688) Atlas - Upgrade Snake-yaml to 1.32
[ https://issues.apache.org/jira/browse/ATLAS-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4688: --- Summary: Atlas - Upgrade Snake-yaml to 1.32 (was: Atlas - Upgrade Snakye-yaml to 1.32) > Atlas - Upgrade Snake-yaml to 1.32 > -- > > Key: ATLAS-4688 > URL: https://issues.apache.org/jira/browse/ATLAS-4688 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Currently Snake-yaml uses 1.26 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4688) Atlas - Upgrade Snakye-yaml to 1.32
chaitali borole created ATLAS-4688: -- Summary: Atlas - Upgrade Snakye-yaml to 1.32 Key: ATLAS-4688 URL: https://issues.apache.org/jira/browse/ATLAS-4688 Project: Atlas Issue Type: Improvement Affects Versions: 2.0.0, 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Currently Snake-yaml uses 1.26 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0
[ https://issues.apache.org/jira/browse/ATLAS-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4677: --- Fix Version/s: 2.0.0 > Atlas - Upgrade commons-configuration to 2.8.0 > -- > > Key: ATLAS-4677 > URL: https://issues.apache.org/jira/browse/ATLAS-4677 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > Current version for commons-configuration2 is 2.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0
chaitali borole created ATLAS-4677: -- Summary: Atlas - Upgrade commons-configuration to 2.8.0 Key: ATLAS-4677 URL: https://issues.apache.org/jira/browse/ATLAS-4677 Project: Atlas Issue Type: Improvement Affects Versions: 2.0.0, 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Current version for commons-configuration2 is 2.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4670) Upgrade Jackson version to 2.13.3
chaitali borole created ATLAS-4670: -- Summary: Upgrade Jackson version to 2.13.3 Key: ATLAS-4670 URL: https://issues.apache.org/jira/browse/ATLAS-4670 Project: Atlas Issue Type: Improvement Affects Versions: 2.0.0, 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Currently jackson version is 2.11.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4669) Atlas - Upgrade Junit to 4.13.2
[ https://issues.apache.org/jira/browse/ATLAS-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4669: -- Assignee: chaitali borole > Atlas - Upgrade Junit to 4.13.2 > --- > > Key: ATLAS-4669 > URL: https://issues.apache.org/jira/browse/ATLAS-4669 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > currently Junit version is 4.13.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4669) Atlas - Upgrade Junit to 4.13.2
[ https://issues.apache.org/jira/browse/ATLAS-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4669: --- Description: currently Junit version is 4.13.1 > Atlas - Upgrade Junit to 4.13.2 > --- > > Key: ATLAS-4669 > URL: https://issues.apache.org/jira/browse/ATLAS-4669 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Priority: Major > > currently Junit version is 4.13.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4669) Atlas - Upgrade Junit to 4.13.2
chaitali borole created ATLAS-4669: -- Summary: Atlas - Upgrade Junit to 4.13.2 Key: ATLAS-4669 URL: https://issues.apache.org/jira/browse/ATLAS-4669 Project: Atlas Issue Type: Improvement Reporter: chaitali borole -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4662) Upgrade POI to 5.2.2
[ https://issues.apache.org/jira/browse/ATLAS-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4662: --- Description: POI and POI-ooxml version is 4.1.1 > Upgrade POI to 5.2.2 > > > Key: ATLAS-4662 > URL: https://issues.apache.org/jira/browse/ATLAS-4662 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > POI and POI-ooxml version is 4.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4662) Upgrade POI to 5.2.2
chaitali borole created ATLAS-4662: -- Summary: Upgrade POI to 5.2.2 Key: ATLAS-4662 URL: https://issues.apache.org/jira/browse/ATLAS-4662 Project: Atlas Issue Type: Improvement Affects Versions: 2.0.0, 3.0.0 Reporter: chaitali borole Assignee: chaitali borole -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4647) Upgrade Spring Security to 5.7.2
[ https://issues.apache.org/jira/browse/ATLAS-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4647: --- Fix Version/s: 2.0.0 > Upgrade Spring Security to 5.7.2 > > > Key: ATLAS-4647 > URL: https://issues.apache.org/jira/browse/ATLAS-4647 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > Current version for spring-security is 5.7.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4653) Upgrade Hadoop to 3.3.3
[ https://issues.apache.org/jira/browse/ATLAS-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4653: --- Description: currently Hadoop is using 3.3.0 and 3.0.3 This patch also upgrades jackson-databind to 2.13.3 and commons-beanutils to 1.9.4 was:currently Hadoop is using 3.3.0 and 3.0.3 > Upgrade Hadoop to 3.3.3 > --- > > Key: ATLAS-4653 > URL: https://issues.apache.org/jira/browse/ATLAS-4653 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > currently Hadoop is using 3.3.0 and 3.0.3 > This patch also upgrades jackson-databind to 2.13.3 and commons-beanutils to > 1.9.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4653) Upgrade Hadoop to 3.3.3
chaitali borole created ATLAS-4653: -- Summary: Upgrade Hadoop to 3.3.3 Key: ATLAS-4653 URL: https://issues.apache.org/jira/browse/ATLAS-4653 Project: Atlas Issue Type: Improvement Reporter: chaitali borole Assignee: chaitali borole currently Hadoop is using 3.3.0 and 3.0.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4651) Upgrade Apache ZooKeeper to 3.8.0
chaitali borole created ATLAS-4651: -- Summary: Upgrade Apache ZooKeeper to 3.8.0 Key: ATLAS-4651 URL: https://issues.apache.org/jira/browse/ATLAS-4651 Project: Atlas Issue Type: Improvement Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Current version of zookeeper is 3.5.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4650) Upgrade Apache Commons BeanUtils to 1.9.4
chaitali borole created ATLAS-4650: -- Summary: Upgrade Apache Commons BeanUtils to 1.9.4 Key: ATLAS-4650 URL: https://issues.apache.org/jira/browse/ATLAS-4650 Project: Atlas Issue Type: Improvement Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Currently Commons BeanUtils version is 1.9.2,1.8.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4649) Upgrade Spring Framework to 4.3.30.RELEASE/5.3.21
chaitali borole created ATLAS-4649: -- Summary: Upgrade Spring Framework to 4.3.30.RELEASE/5.3.21 Key: ATLAS-4649 URL: https://issues.apache.org/jira/browse/ATLAS-4649 Project: Atlas Issue Type: Improvement Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Fix For: 3.0.0 current version for Spring Framework is 5.3.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4648) Upgrade Netty version to 4.1.78.Final
[ https://issues.apache.org/jira/browse/ATLAS-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4648: --- Summary: Upgrade Netty version to 4.1.78.Final (was: Upgrade Netty Project to 4.1.78.Final) > Upgrade Netty version to 4.1.78.Final > - > > Key: ATLAS-4648 > URL: https://issues.apache.org/jira/browse/ATLAS-4648 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > current version for Netty to 4.1.77.Final -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4648) Upgrade Netty Project to 4.1.78.Final
chaitali borole created ATLAS-4648: -- Summary: Upgrade Netty Project to 4.1.78.Final Key: ATLAS-4648 URL: https://issues.apache.org/jira/browse/ATLAS-4648 Project: Atlas Issue Type: Improvement Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Fix For: 3.0.0 current version for Netty to 4.1.77.Final -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4647) Upgrade Spring Security to 5.7.2
[ https://issues.apache.org/jira/browse/ATLAS-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4647: --- Summary: Upgrade Spring Security to 5.7.2 (was: Atlas - Upgrade Spring Security to 5.7.2) > Upgrade Spring Security to 5.7.2 > > > Key: ATLAS-4647 > URL: https://issues.apache.org/jira/browse/ATLAS-4647 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > Current version for spring-security is 5.7.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4647) Atlas - Upgrade Spring Security to 5.7.2
chaitali borole created ATLAS-4647: -- Summary: Atlas - Upgrade Spring Security to 5.7.2 Key: ATLAS-4647 URL: https://issues.apache.org/jira/browse/ATLAS-4647 Project: Atlas Issue Type: Improvement Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Fix For: 3.0.0 Current version for spring-security is 5.7.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4507) Atlas - Upgrade testng to 7.0.0
[ https://issues.apache.org/jira/browse/ATLAS-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4507: --- Summary: Atlas - Upgrade testng to 7.0.0 (was: Atlas - Upgrade testng to 6.11 or later) > Atlas - Upgrade testng to 7.0.0 > --- > > Key: ATLAS-4507 > URL: https://issues.apache.org/jira/browse/ATLAS-4507 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Currently Atlas is using 6.9.4 version for testng Upgrading testng to 6.11 or > later -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4507) Atlas - Upgrade testng to 7.0.0
[ https://issues.apache.org/jira/browse/ATLAS-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4507: --- Description: Currently Atlas is using 6.9.4 version for testng Upgrading testng to 7.0.0 was:Currently Atlas is using 6.9.4 version for testng Upgrading testng to 6.11 or later > Atlas - Upgrade testng to 7.0.0 > --- > > Key: ATLAS-4507 > URL: https://issues.apache.org/jira/browse/ATLAS-4507 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Currently Atlas is using 6.9.4 version for testng Upgrading testng to 7.0.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (ATLAS-4507) Atlas - Upgrade testng to 6.11 or later
[ https://issues.apache.org/jira/browse/ATLAS-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4507: -- Assignee: chaitali borole > Atlas - Upgrade testng to 6.11 or later > --- > > Key: ATLAS-4507 > URL: https://issues.apache.org/jira/browse/ATLAS-4507 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Currently Atlas is using 6.9.4 version for testng Upgrading testng to 6.11 or > later -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4507) Atlas - Upgrade testng to 6.11 or later
chaitali borole created ATLAS-4507: -- Summary: Atlas - Upgrade testng to 6.11 or later Key: ATLAS-4507 URL: https://issues.apache.org/jira/browse/ATLAS-4507 Project: Atlas Issue Type: Improvement Reporter: chaitali borole Currently Atlas is using 6.9.4 version for testng Upgrading testng to 6.11 or later -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4503) Handle cross version messages in Atlas server
[ https://issues.apache.org/jira/browse/ATLAS-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4503: --- Summary: Handle cross version messages in Atlas server (was: SDX Version Compatibility: Handle cross version messages in Atlas server) > Handle cross version messages in Atlas server > - > > Key: ATLAS-4503 > URL: https://issues.apache.org/jira/browse/ATLAS-4503 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > Atlas sever can receive notification messages from atlas hooks running on > different version (than Atlas server version). When messages are not > compatible, error logs should be thrown. > Log Error/Warning in Atlas logs about cross-compat version messages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4503) SDX Version Compatibility: Handle cross version messages in Atlas server
chaitali borole created ATLAS-4503: -- Summary: SDX Version Compatibility: Handle cross version messages in Atlas server Key: ATLAS-4503 URL: https://issues.apache.org/jira/browse/ATLAS-4503 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: 2.0.0, 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Fix For: 3.0.0, 2.0.0 Atlas sever can receive notification messages from atlas hooks running on different version (than Atlas server version). When messages are not compatible, error logs should be thrown. Log Error/Warning in Atlas logs about cross-compat version messages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4496) Atlas - Upgrade elasticsearch to 7.14.0
chaitali borole created ATLAS-4496: -- Summary: Atlas - Upgrade elasticsearch to 7.14.0 Key: ATLAS-4496 URL: https://issues.apache.org/jira/browse/ATLAS-4496 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: 2.0.0, 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Fix For: 3.0.0, 2.0.0 Currently Atlas is using elasticsearch version 7.6.0 upgrading it to 7.14.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4493) Upgrade netty to 4.1.69
[ https://issues.apache.org/jira/browse/ATLAS-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4493: --- Summary: Upgrade netty to 4.1.69 (was: Upgrade netty to 4.1.68+) > Upgrade netty to 4.1.69 > --- > > Key: ATLAS-4493 > URL: https://issues.apache.org/jira/browse/ATLAS-4493 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Upgrading netty to 4.1.69 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (ATLAS-4493) atlas - Upgrade netty to 4.1.68+
[ https://issues.apache.org/jira/browse/ATLAS-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4493: -- Assignee: chaitali borole > atlas - Upgrade netty to 4.1.68+ > > > Key: ATLAS-4493 > URL: https://issues.apache.org/jira/browse/ATLAS-4493 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Upgrading netty to 4.1.69 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4493) Upgrade netty to 4.1.68+
[ https://issues.apache.org/jira/browse/ATLAS-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4493: --- Summary: Upgrade netty to 4.1.68+ (was: atlas - Upgrade netty to 4.1.68+) > Upgrade netty to 4.1.68+ > > > Key: ATLAS-4493 > URL: https://issues.apache.org/jira/browse/ATLAS-4493 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Upgrading netty to 4.1.69 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4493) atlas - Upgrade netty to 4.1.68+
chaitali borole created ATLAS-4493: -- Summary: atlas - Upgrade netty to 4.1.68+ Key: ATLAS-4493 URL: https://issues.apache.org/jira/browse/ATLAS-4493 Project: Atlas Issue Type: Improvement Affects Versions: 2.0.0, 3.0.0 Reporter: chaitali borole Upgrading netty to 4.1.69 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4079) Atlas-Upgrade jackson to 2.11.0+
[ https://issues.apache.org/jira/browse/ATLAS-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4079: --- Fix Version/s: 2.3.0 > Atlas-Upgrade jackson to 2.11.0+ > > > Key: ATLAS-4079 > URL: https://issues.apache.org/jira/browse/ATLAS-4079 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > Upgrade jackson to 2.11.0+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4079) Atlas-Upgrade jackson to 2.11.0+
[ https://issues.apache.org/jira/browse/ATLAS-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4079: --- Affects Version/s: 2.3.0 > Atlas-Upgrade jackson to 2.11.0+ > > > Key: ATLAS-4079 > URL: https://issues.apache.org/jira/browse/ATLAS-4079 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > Upgrade jackson to 2.11.0+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4446) Atlas - Upgrade elasticsearch to 7.6.0
[ https://issues.apache.org/jira/browse/ATLAS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4446: --- Summary: Atlas - Upgrade elasticsearch to 7.6.0 (was: Atlas - Upgrade elasticsearch to 7.14.0) > Atlas - Upgrade elasticsearch to 7.6.0 > -- > > Key: ATLAS-4446 > URL: https://issues.apache.org/jira/browse/ATLAS-4446 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Currently Elastic search is at 6.8.17 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4446) Atlas - Upgrade elasticsearch to 7.14.0
chaitali borole created ATLAS-4446: -- Summary: Atlas - Upgrade elasticsearch to 7.14.0 Key: ATLAS-4446 URL: https://issues.apache.org/jira/browse/ATLAS-4446 Project: Atlas Issue Type: Improvement Reporter: chaitali borole Assignee: chaitali borole Currently Elastic search is at 6.8.17 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4440) Upgrade Atlas's Kafka dependency to 2.8
[ https://issues.apache.org/jira/browse/ATLAS-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424001#comment-17424001 ] chaitali borole commented on ATLAS-4440: Hello [~amestry], Patch looks good to me. +1 for the patch. > Upgrade Atlas's Kafka dependency to 2.8 > --- > > Key: ATLAS-4440 > URL: https://issues.apache.org/jira/browse/ATLAS-4440 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Viktor Somogyi-Vass >Assignee: Viktor Somogyi-Vass >Priority: Major > Attachments: 0001-ATLAS-4440-Update-Kafka-dependency-to-2.8.1.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4428) Enhance Atlas hook messages to capture hook version & message source
chaitali borole created ATLAS-4428: -- Summary: Enhance Atlas hook messages to capture hook version & message source Key: ATLAS-4428 URL: https://issues.apache.org/jira/browse/ATLAS-4428 Project: Atlas Issue Type: Improvement Reporter: chaitali borole Assignee: chaitali borole Atlas hook messages doesn't specify the source information of the messages coming i.e. which hook source - HiveServer2, HiveMetastore, Impala, Spark, HBase, Kafka. Each hook message already captures, the msgSourceIP, msgCreatedBy and msgCreationTime info. In addition to these, we should capture the msgSource information as well. When messages come from different hook versions, Atlas server should be aware of the version of different hook messages to process the message based on the hook version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4377) Atlas - Upgrade Spring Security to 5.4.4+/5.3.8+/5.2.9+
chaitali borole created ATLAS-4377: -- Summary: Atlas - Upgrade Spring Security to 5.4.4+/5.3.8+/5.2.9+ Key: ATLAS-4377 URL: https://issues.apache.org/jira/browse/ATLAS-4377 Project: Atlas Issue Type: Improvement Reporter: chaitali borole Assignee: chaitali borole Atlas is pulling in Spring security 4.2.17.RELEASE upgrade to 5.4.4, 5.3.8, or 5.2.9 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4376) AtlasClientV2 getRelationshipDefByName does not work
chaitali borole created ATLAS-4376:
--
Summary: AtlasClientV2 getRelationshipDefByName does not work
Key: ATLAS-4376
URL: https://issues.apache.org/jira/browse/ATLAS-4376
Project: Atlas
Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: chaitali borole
Assignee: chaitali borole
Fix For: 3.0.0
When tried to get the typedef of a relationship by:
atlasClient.getRelationshipDefByName(name)
This will get translated into the following REST request:
/api/atlas/v2/types/structdef/name/
{name}
The correct REST request should be:
/api/atlas/v2/types/relationshipdef/name/{name}
The reason why it's querying a structdef and not a relationshipdef is due to a
bug in AtlasClientV2 line 1135:
} else if (AtlasStructDef.class.isAssignableFrom(typeDefClass)) {
return "structdef";
} else if (AtlasRelationshipDef.class.isAssignableFrom(typeDefClass)) {
return "relationshipdef";
Since AtlasRelationshipDef extends AtlasStructDef, the first "if" branch will
always be true and the second "if" branch will never happen. The fix for this
issue is to reverse the two "if" branches.
provide test cases for all "if" branches to ensure the querying works correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4208) [Atlas: Audits] 2 audits are created when a label is added and removed in 1 go from an entity
[ https://issues.apache.org/jira/browse/ATLAS-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole resolved ATLAS-4208. Resolution: Not A Bug > [Atlas: Audits] 2 audits are created when a label is added and removed in 1 > go from an entity > - > > Key: ATLAS-4208 > URL: https://issues.apache.org/jira/browse/ATLAS-4208 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: chaitali borole >Priority: Major > > *Scenario:* > Add few labels to an entity > Now update the labels by adding 1 more and removing an old label associated > with the entity > > *Observation:* > 2 audit entries are created > *Expectation:* > 1 new audit has to be created with labels added and removed provided in same > audit -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4208) [Atlas: Audits] 2 audits are created when a label is added and removed in 1 go from an entity
[ https://issues.apache.org/jira/browse/ATLAS-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383315#comment-17383315 ] chaitali borole commented on ATLAS-4208: Hello [~dharshmk], I debugged and reproduced the scenario looks like it works fine by design and one entityAuditEvent can have only one action. > [Atlas: Audits] 2 audits are created when a label is added and removed in 1 > go from an entity > - > > Key: ATLAS-4208 > URL: https://issues.apache.org/jira/browse/ATLAS-4208 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: chaitali borole >Priority: Major > > *Scenario:* > Add few labels to an entity > Now update the labels by adding 1 more and removing an old label associated > with the entity > > *Observation:* > 2 audit entries are created > *Expectation:* > 1 new audit has to be created with labels added and removed provided in same > audit -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4351) Maven-jetty throwing warnings when running Integration tests for conflicting jars in classpath
chaitali borole created ATLAS-4351: -- Summary: Maven-jetty throwing warnings when running Integration tests for conflicting jars in classpath Key: ATLAS-4351 URL: https://issues.apache.org/jira/browse/ATLAS-4351 Project: Atlas Issue Type: Improvement Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Fix For: 3.0.0 Below warnings are thrown when integration tests executed : [INFO] jetty-9.4.31.v20200723; built: 2020-07-23T17:57:36.812Z; git: 450ba27947e13e66baa8cd1ce7e85a4461cacc1d; jvm 1.8.0_291-b10 [WARNING] javax.activation.ActivationDataFlavor scanned from multiple locations: jar: [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/jakarta.activation-api-1.2.1.jar!/javax/activation/ActivationDataFlavor.class] , jar: [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.activation-api-1.2.0.jar!/javax/activation/ActivationDataFlavor.class] [WARNING] com.google.common.base.Stopwatch$1 scanned from multiple locations: jar: [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/guava-25.1-jre.jar!/com/google/common/base/Stopwatch$1.class] , jar: [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/janusgraph-hbase-0.5.3.jar!/com/google/common/base/Stopwatch$1.class] [WARNING] javax.servlet.AsyncContext scanned from multiple locations: jar: [file:///home/jenkins/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncContext.class] , jar: [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncContext.class] [WARNING] javax.servlet.AsyncEvent scanned from multiple locations: jar: [file:///home/jenkins/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncEvent.class] , jar: [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncEvent.class] [WARNING] javax.servlet.AsyncListener scanned from multiple locations: jar: [file:///home/jenkins/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncListener.class] , jar: [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncListener.class] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4208) [Atlas: Audits] 2 audits are created when a label is added and removed in 1 go from an entity
[ https://issues.apache.org/jira/browse/ATLAS-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4208: -- Assignee: chaitali borole > [Atlas: Audits] 2 audits are created when a label is added and removed in 1 > go from an entity > - > > Key: ATLAS-4208 > URL: https://issues.apache.org/jira/browse/ATLAS-4208 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: chaitali borole >Priority: Major > > *Scenario:* > Add few labels to an entity > Now update the labels by adding 1 more and removing an old label associated > with the entity > > *Observation:* > 2 audit entries are created > *Expectation:* > 1 new audit has to be created with labels added and removed provided in same > audit -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4317) Atlas should use downstream Curator
[ https://issues.apache.org/jira/browse/ATLAS-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4317: -- Assignee: chaitali borole > Atlas should use downstream Curator > --- > > Key: ATLAS-4317 > URL: https://issues.apache.org/jira/browse/ATLAS-4317 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Upgrade curator jar version to 4.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4317) Atlas should use downstream Curator
[ https://issues.apache.org/jira/browse/ATLAS-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4317: --- Description: Upgrade curator jar version to 4.3.0 > Atlas should use downstream Curator > --- > > Key: ATLAS-4317 > URL: https://issues.apache.org/jira/browse/ATLAS-4317 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Priority: Major > > Upgrade curator jar version to 4.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4317) Atlas should use downstream Curator
chaitali borole created ATLAS-4317: -- Summary: Atlas should use downstream Curator Key: ATLAS-4317 URL: https://issues.apache.org/jira/browse/ATLAS-4317 Project: Atlas Issue Type: Improvement Reporter: chaitali borole -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4174) [Atlas: Glossary Term Bulk Import] When the file size is large (5 mb) bulk import times out
[ https://issues.apache.org/jira/browse/ATLAS-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4174: -- Assignee: chaitali borole (was: Mayank Jain) > [Atlas: Glossary Term Bulk Import] When the file size is large (5 mb) bulk > import times out > --- > > Key: ATLAS-4174 > URL: https://issues.apache.org/jira/browse/ATLAS-4174 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: chaitali borole >Priority: Major > Attachments: Screen Recording 2021-02-23 at 2.33.42 PM.mov, > only_names.csv > > > When file size is large bulk import times out. > Attached a sample input for which the bulk import times out > Sample input: [^only_names.csv] > Video: [^Screen Recording 2021-02-23 at 2.33.42 PM.mov] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4255) Atlas - Upgrade netty to 4.1.61
chaitali borole created ATLAS-4255: -- Summary: Atlas - Upgrade netty to 4.1.61 Key: ATLAS-4255 URL: https://issues.apache.org/jira/browse/ATLAS-4255 Project: Atlas Issue Type: Task Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Currently Atlas is pulling netty jar versions 4.1.47,4.1.51 Upgrade it to latest 4.1.61 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4179) [Atlas: Glossary Term Bulk Import] Incorrect error message when only dependent term is not present in bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4179:
--
Assignee: chaitali borole
> [Atlas: Glossary Term Bulk Import] Incorrect error message when only
> dependent term is not present in bulk import
> -
>
> Key: ATLAS-4179
> URL: https://issues.apache.org/jira/browse/ATLAS-4179
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Minor
> Attachments: Screenshot 2021-02-26 at 1.10.32 AM.png
>
>
> {code:java}
> glossary_rb,term_1,"short description","long description", "Example", "G1",
> "Usage",,"gloss_1:term_2"{code}
> Consider the above input, say *gloss_1* is present but term *term_2* is not
> present, error message conveys, that both glossary and term are not present
> Error message:
> {code:java}
> {"errorCode":"ATLAS-500-00-001",
> "errorMessage":"The uploaded file has not been processed due to the following
> errors : \n[\nThe provided Reference Glossary and TermName does not exist in
> the system term_2:gloss_1 for record with TermName : term_1 and GlossaryName
> : glossary_rb]"}{code}
> !Screenshot 2021-02-26 at 1.10.32 AM.png|width=606,height=247!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4228) Kafka topic names should be configurable
[ https://issues.apache.org/jira/browse/ATLAS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole resolved ATLAS-4228. Resolution: Abandoned > Kafka topic names should be configurable > > > Key: ATLAS-4228 > URL: https://issues.apache.org/jira/browse/ATLAS-4228 > Project: Atlas > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > We need to provide functionality where in names of the kafka topics can be > customised using property configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4228) Kafka topic names should be configurable
chaitali borole created ATLAS-4228: -- Summary: Kafka topic names should be configurable Key: ATLAS-4228 URL: https://issues.apache.org/jira/browse/ATLAS-4228 Project: Atlas Issue Type: Task Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole We need to provide functionality where in names of the kafka topics can be customised using property configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4221) Solr collection names should be configurable
[ https://issues.apache.org/jira/browse/ATLAS-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4221: --- Description: Currently in Atlas, the collection names are not configurable We need to provide functionality where in names of the solr collections can be customized using property configuration was: Currently in Atlas, the collection names are not configurable We need to provide customised collections in solr > Solr collection names should be configurable > > > Key: ATLAS-4221 > URL: https://issues.apache.org/jira/browse/ATLAS-4221 > Project: Atlas > Issue Type: Task >Affects Versions: 2.1.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Currently in Atlas, the collection names are not configurable > We need to provide functionality where in names of the solr collections can > be customized using property configuration -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4221) Solr collection names should be configurable
chaitali borole created ATLAS-4221: -- Summary: Solr collection names should be configurable Key: ATLAS-4221 URL: https://issues.apache.org/jira/browse/ATLAS-4221 Project: Atlas Issue Type: Task Affects Versions: 2.1.0, 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Currently in Atlas, the collection names are not configurable We need to provide customised collections in solr -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4194) [Read Type Auth] Metrics API shows the typecounts for types not readable by user
[ https://issues.apache.org/jira/browse/ATLAS-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4194: --- Affects Version/s: 3.0.0 2.0.0 > [Read Type Auth] Metrics API shows the typecounts for types not readable by > user > > > Key: ATLAS-4194 > URL: https://issues.apache.org/jira/browse/ATLAS-4194 > Project: Atlas > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > user hrt_qa doesn't have permission to read any classification/entity type. > But Metrics API shows wrong typecount and tagcount too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4194) [Read Type Auth] Metrics API shows the typecounts for types not readable by user
chaitali borole created ATLAS-4194: -- Summary: [Read Type Auth] Metrics API shows the typecounts for types not readable by user Key: ATLAS-4194 URL: https://issues.apache.org/jira/browse/ATLAS-4194 Project: Atlas Issue Type: Task Reporter: chaitali borole Assignee: chaitali borole user hrt_qa doesn't have permission to read any classification/entity type. But Metrics API shows wrong typecount and tagcount too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4180) [Atlas: Glossary Term Bulk Import] Update error message thrown while using "@" in glossary/term name
[
https://issues.apache.org/jira/browse/ATLAS-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4180:
--
Assignee: chaitali borole
> [Atlas: Glossary Term Bulk Import] Update error message thrown while using
> "@" in glossary/term name
>
>
> Key: ATLAS-4180
> URL: https://issues.apache.org/jira/browse/ATLAS-4180
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Minor
>
> Input: *@ in term name*
> {code:java}
> "glossary_1","@term_1" {code}
> Error:
> {code:java}
> {"errorCode":"ATLAS-500-00-016","errorMessage":"Error occurred while creating
> glossary term: {0}","errorCause":"name cannot contain following special chars
> (@, .)"} {code}
> *Expectation*:
> * Replace *{0}* with actual term name
> * Convey the reason in error message
>
> Input: *@ in glossary name*
> {code:java}
> "@glossary_1","term_1"{code}
> Error:
> {code:java}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"The uploaded file has not
> been processed due to the following errors : \n[The provided Glossary Name is
> invalid : @glossary_1]"} {code}
> Expectation:
> * Keep it consistent with above message
> * convey reason in error message
> Also these are client errors
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4175) [Atlas: Read type auth] [Regression]: User is able to create a sub-type with non-readable super type
[ https://issues.apache.org/jira/browse/ATLAS-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole resolved ATLAS-4175. Resolution: Cannot Reproduce > [Atlas: Read type auth] [Regression]: User is able to create a sub-type with > non-readable super type > > > Key: ATLAS-4175 > URL: https://issues.apache.org/jira/browse/ATLAS-4175 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: chaitali borole >Priority: Major > > hrt_qa doesn't have read permission on classification : PII > hrt_qa has CRUD permission on classification : Confidential > When hrt_qa tries to create a classification `Confidential` with super type > as `PII` , expectation is to deny creation . But tag creation is successful > and has the super tag `PII` > -- 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 ] chaitali borole updated ATLAS-3976: --- Affects Version/s: 2.1.0 > 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 >Affects Versions: 2.1.0, 3.0.0 >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)
[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 ] chaitali borole updated ATLAS-3976: --- Fix Version/s: 2.0.0 3.0.0 > 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 >Affects Versions: 2.0.0, 3.0.0 >Reporter: Dharshana M Krishnamoorthy >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > 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)
[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 ] chaitali borole updated ATLAS-3976: --- Affects Version/s: 3.0.0 > 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 >Affects Versions: 3.0.0 >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)
[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 ] chaitali borole updated ATLAS-3976: --- Affects Version/s: (was: 2.1.0) 2.0.0 > 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 >Affects Versions: 2.0.0, 3.0.0 >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)
[jira] [Commented] (ATLAS-4176) [Atlas: Read type auth] When un-authorised user creates a sub type, incorrect error message is thrown
[
https://issues.apache.org/jira/browse/ATLAS-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293610#comment-17293610
]
chaitali borole commented on ATLAS-4176:
[~dharshmk],
Kindly share your policy details if you are expecting this error
{code:java}
hrt_20 is not authorized to perform read type-def of category ENTITY entity_1
{code}
because here there are two cases either hrt_20 doesn't have any access.
or else hrt_20 doesn't have any access for supertype in specific.
CC:[~nixon]
> [Atlas: Read type auth] When un-authorised user creates a sub type, incorrect
> error message is thrown
> --
>
> Key: ATLAS-4176
> URL: https://issues.apache.org/jira/browse/ATLAS-4176
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
> *hrt_20* is an *unauthorised_user*
> When hrt_20 tries to create an entity_type *sub_entity_1* with super_type as
> "*entity_1*" the following is thrown
> {code:java}
> hrt_20 is not authorized to perform create entity-def sub_entity_1 {code}
> Expectation:
> {code:java}
> hrt_20 is not authorized to perform read type-def of category ENTITY entity_1
> {code}
>
> NOTE:
> This happens only for entity type and not for classification.
> When creating a classification *sub_class_1* with super_type as *class_1* the
> following exception is thrown, which is correct
> {code:java}
> hrt_20 is not authorized to perform read type-def of category CLASSIFICATION
> class_1 {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4176) [Atlas: Read type auth] When un-authorised user creates a sub type, incorrect error message is thrown
[
https://issues.apache.org/jira/browse/ATLAS-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4176:
--
Assignee: chaitali borole
> [Atlas: Read type auth] When un-authorised user creates a sub type, incorrect
> error message is thrown
> --
>
> Key: ATLAS-4176
> URL: https://issues.apache.org/jira/browse/ATLAS-4176
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
> *hrt_20* is an *unauthorised_user*
> When hrt_20 tries to create an entity_type *sub_entity_1* with super_type as
> "*entity_1*" the following is thrown
> {code:java}
> hrt_20 is not authorized to perform create entity-def sub_entity_1 {code}
> Expectation:
> {code:java}
> hrt_20 is not authorized to perform read type-def of category ENTITY entity_1
> {code}
>
> NOTE:
> This happens only for entity type and not for classification.
> When creating a classification *sub_class_1* with super_type as *class_1* the
> following exception is thrown, which is correct
> {code:java}
> hrt_20 is not authorized to perform read type-def of category CLASSIFICATION
> class_1 {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4175) [Atlas: Read type auth] [Regression]: User is able to create a sub-type with non-readable super type
[ https://issues.apache.org/jira/browse/ATLAS-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4175: -- Assignee: chaitali borole > [Atlas: Read type auth] [Regression]: User is able to create a sub-type with > non-readable super type > > > Key: ATLAS-4175 > URL: https://issues.apache.org/jira/browse/ATLAS-4175 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: chaitali borole >Priority: Major > > hrt_qa doesn't have read permission on classification : PII > hrt_qa has CRUD permission on classification : Confidential > When hrt_qa tries to create a classification `Confidential` with super type > as `PII` , expectation is to deny creation . But tag creation is successful > and has the super tag `PII` > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities
[
https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4171:
--
Assignee: chaitali borole (was: Umesh Padashetty)
> Authorisation : Bulk entity DELETE API doesn't delete authorised entities
> -
>
> Key: ATLAS-4171
> URL: https://issues.apache.org/jira/browse/ATLAS-4171
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Assignee: chaitali borole
>Priority: Major
>
> Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised
> entities when the list of authorised and unauthorised entities list is passed.
> Curl:
> {code:java}
> curl --location --request DELETE
> 'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
> \--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
> 'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
> We need to implement one of the flag ignoreUnauthorisedGuids,
> isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
> POST API
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities
[
https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4171:
--
Assignee: Umesh Padashetty (was: chaitali borole)
> Authorisation : Bulk entity DELETE API doesn't delete authorised entities
> -
>
> Key: ATLAS-4171
> URL: https://issues.apache.org/jira/browse/ATLAS-4171
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Major
>
> Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised
> entities when the list of authorised and unauthorised entities list is passed.
> Curl:
> {code:java}
> curl --location --request DELETE
> 'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
> \--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
> 'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
> We need to implement one of the flag ignoreUnauthorisedGuids,
> isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
> POST API
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4172) Authorisation : Bulk create/update entity POST API doesn't create/update authorised entities
[
https://issues.apache.org/jira/browse/ATLAS-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4172:
--
Assignee: chaitali borole
> Authorisation : Bulk create/update entity POST API doesn't create/update
> authorised entities
>
>
> Key: ATLAS-4172
> URL: https://issues.apache.org/jira/browse/ATLAS-4172
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Assignee: chaitali borole
>Priority: Major
>
> API : /api/atlas/v2/entity/bulk
> Body :
> {code:java}
> { "entities":[ {"authorised_1"}, {"unauthorised_1"}, {"authorised_2"} ] }
> {code}
> Consider a user posts the body which contains
> entity1 of type1 he is authorised ,
> entity2 of type2 he is not authorised ,
> entity3 of type3 he is authorised
> The request returns 403 since of the entities is unauthorized.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities
[
https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4171:
--
Assignee: chaitali borole
> Authorisation : Bulk entity DELETE API doesn't delete authorised entities
> -
>
> Key: ATLAS-4171
> URL: https://issues.apache.org/jira/browse/ATLAS-4171
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Assignee: chaitali borole
>Priority: Major
>
> Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised
> entities when the list of authorised and unauthorised entities list is passed.
> Curl:
> {code:java}
> curl --location --request DELETE
> 'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
> \--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
> 'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
> We need to implement one of the flag ignoreUnauthorisedGuids,
> isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
> POST API
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-3975) User is allowed to create an entity with non-readable entity type
[ https://issues.apache.org/jira/browse/ATLAS-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-3975: -- Assignee: chaitali borole > User is allowed to create an entity with non-readable entity type > - > > Key: ATLAS-3975 > URL: https://issues.apache.org/jira/browse/ATLAS-3975 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: chaitali borole >Priority: Major > > When a user tries to create an entity with non-readable entity-type it > succeeds without throwing error -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (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 ] chaitali borole reassigned ATLAS-3976: -- Assignee: chaitali borole (was: Nixon Rodrigues) > 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)
[jira] [Assigned] (ATLAS-4134) [Atlas:Glossary] Update conflict error message for glossary
[
https://issues.apache.org/jira/browse/ATLAS-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4134:
--
Assignee: chaitali borole
> [Atlas:Glossary] Update conflict error message for glossary
> ---
>
> Key: ATLAS-4134
> URL: https://issues.apache.org/jira/browse/ATLAS-4134
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
> Currently we display the following error message for conflicts:
> {code:java}
> {
> "errorCode":"ATLAS-409-00-007",
> "errorMessage":"Glossary with qualifiedName abc already exists"
> }
> {code}
> It will be user friendly if the message is "*Glossary with name abc already
> exists*"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4148) [Atlas: Glossary Term Bulk Import] Incorrect error code displayed when no data found in the uploaded file
[
https://issues.apache.org/jira/browse/ATLAS-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4148:
--
Assignee: chaitali borole
> [Atlas: Glossary Term Bulk Import] Incorrect error code displayed when no
> data found in the uploaded file
> -
>
> Key: ATLAS-4148
> URL: https://issues.apache.org/jira/browse/ATLAS-4148
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
> Steps to repro:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> This file is written for testing supported format with incorrect data format.
> So this file contains some random text.
> {code}
> When this file is used as an input, the error code displayed is incorrect:
> {code:java}
> {
> "errorCode":"ATLAS-404-00-014",
> "errorMessage":"No data found in the uploaded file"
> }{code}
> Expectation:
> Since this is client side error 400 should be displayed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4147) [Atlas: Glossary Term Bulk Import] When un_supported file type is passed error message displays "file type {0}"
[
https://issues.apache.org/jira/browse/ATLAS-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reassigned ATLAS-4147:
--
Assignee: chaitali borole
> [Atlas: Glossary Term Bulk Import] When un_supported file type is passed
> error message displays "file type {0}"
> ---
>
> Key: ATLAS-4147
> URL: https://issues.apache.org/jira/browse/ATLAS-4147
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
>
> Repro steps:
> Pass unsupported file type to the glossary term bulk import
> {code:java}
> curl --request POST -u user:password
> 'https:///api/atlas/v2/glossary/import' \
> -H 'Accept: application/json' \
> -H 'Cache-Control: no-cache' \
> -H 'X-Requested-With: XMLHttpRequest' \
> -H 'X-XSRF-HEADER: ""' \
> -H 'Content-Type: multipart/form-data' \
> -F file=@abc.py \
> --compressed \
> --insecure{code}
> The following error message is displayed
> {code:java}
> {"errorCode":"ATLAS-400-00-098",
> "errorMessage":"The provided file type {0} is not supported."} {code}
> Expectation:
> Instead of "file type \{0}" actual file type should be displayed
> Suggestion:
> Along with the above message, display the supported file format too
> Example:
> {code:java}
> The provided file type .py is not supported. Supported file formats: .csv,
> .xls{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4120) Entities cached in setLabels() don’t have any attributes populated.
chaitali borole created ATLAS-4120: -- Summary: Entities cached in setLabels() don’t have any attributes populated. Key: ATLAS-4120 URL: https://issues.apache.org/jira/browse/ATLAS-4120 Project: Atlas Issue Type: Task Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole setLabels() is called even before entity attributes are written in the graph store i.e. from EntityGraphMapper.createVertexWithGuid() and EntityGraphMapper.updateSystemAttributes(), hence the entities cached don’t have any attributes populated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3973) Inappropriate message on performing create with non-readable super type
[
https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole resolved ATLAS-3973.
Resolution: Cannot Reproduce
> Inappropriate message on performing create with non-readable super type
> ---
>
> Key: ATLAS-3973
> URL: https://issues.apache.org/jira/browse/ATLAS-3973
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
> Received message
> {code:java}
> {u'errorCode': u'ATLAS-403-00-001', u'errorMessage': u'hrt_qa is not
> authorized to perform read type-def of
> categoryCLASSIFICATIONnon_read_classification_ufvQK'}
> {code}
>
> Expected message
> {code:java}
> hrt_qa is not authorized to perform create classification-def
> with non-readable classification
> {code}
> or something similar, that conveys the right message. The current error
> message seems very confusing. It conveys about read when performing a create
> operation
> Also the message has incorrect spacing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-3973) Inappropriate message on performing create with non-readable super type
[
https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole resolved ATLAS-3973.
Resolution: Fixed
> Inappropriate message on performing create with non-readable super type
> ---
>
> Key: ATLAS-3973
> URL: https://issues.apache.org/jira/browse/ATLAS-3973
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
> Received message
> {code:java}
> {u'errorCode': u'ATLAS-403-00-001', u'errorMessage': u'hrt_qa is not
> authorized to perform read type-def of
> categoryCLASSIFICATIONnon_read_classification_ufvQK'}
> {code}
>
> Expected message
> {code:java}
> hrt_qa is not authorized to perform create classification-def
> with non-readable classification
> {code}
> or something similar, that conveys the right message. The current error
> message seems very confusing. It conveys about read when performing a create
> operation
> Also the message has incorrect spacing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (ATLAS-3973) Inappropriate message on performing create with non-readable super type
[
https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole reopened ATLAS-3973:
> Inappropriate message on performing create with non-readable super type
> ---
>
> Key: ATLAS-3973
> URL: https://issues.apache.org/jira/browse/ATLAS-3973
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
> Received message
> {code:java}
> {u'errorCode': u'ATLAS-403-00-001', u'errorMessage': u'hrt_qa is not
> authorized to perform read type-def of
> categoryCLASSIFICATIONnon_read_classification_ufvQK'}
> {code}
>
> Expected message
> {code:java}
> hrt_qa is not authorized to perform create classification-def
> with non-readable classification
> {code}
> or something similar, that conveys the right message. The current error
> message seems very confusing. It conveys about read when performing a create
> operation
> Also the message has incorrect spacing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4104) Throw 400 malformed request error from atlas when the payload is malformed
[
https://issues.apache.org/jira/browse/ATLAS-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole resolved ATLAS-4104.
Resolution: Duplicate
> Throw 400 malformed request error from atlas when the payload is malformed
> --
>
> Key: ATLAS-4104
> URL: https://issues.apache.org/jira/browse/ATLAS-4104
> Project: Atlas
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> There is an additional "," in the below 2 payloads, which make it a client
> side payload error. But when firing such a request 500 internal server error
> is thrown
> *These are client errors that are being thrown as server errors*
> Error handling a request: 31167d3d0dc60f70
> (ExceptionMapperUtil:32)com.fasterxml.jackson.databind.JsonMappingException:
> Unexpected character (']' (code 93)): expected a value at [Source:
> (org.eclipse.jetty.server.HttpInputOverHTTP); line: 6, column: 6] (through
> reference chain:
> org.apache.atlas.model.typedef.AtlasTypesDef["classificationDefs"]) at
> com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:397)
> at
> com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:356)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializerBase.wrapAndThrow(BeanDeserializerBase.java:1719)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:290)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
> at com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1682)
> at
> {code:java|title=Malformed payload for creating a classification}
> {
> "classificationDefs": [
> {
> "name": "tag_1",
> }
> ]
> }
> {code}
> {code:java|title=Malformed payload for creating a classification}
> {
> "classificationDefs": [
> {
> "name": "tag_1"
> },
> ]
> }{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4104) Throw 400 malformed request error from atlas when the payload is malformed
chaitali borole created ATLAS-4104:
--
Summary: Throw 400 malformed request error from atlas when the
payload is malformed
Key: ATLAS-4104
URL: https://issues.apache.org/jira/browse/ATLAS-4104
Project: Atlas
Issue Type: Task
Affects Versions: 3.0.0
Reporter: chaitali borole
Assignee: chaitali borole
There is an additional "," in the below 2 payloads, which make it a client side
payload error. But when firing such a request 500 internal server error is
thrown
*These are client errors that are being thrown as server errors*
Error handling a request: 31167d3d0dc60f70
(ExceptionMapperUtil:32)com.fasterxml.jackson.databind.JsonMappingException:
Unexpected character (']' (code 93)): expected a value at [Source:
(org.eclipse.jetty.server.HttpInputOverHTTP); line: 6, column: 6] (through
reference chain:
org.apache.atlas.model.typedef.AtlasTypesDef["classificationDefs"]) at
com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:397)
at
com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:356)
at
com.fasterxml.jackson.databind.deser.BeanDeserializerBase.wrapAndThrow(BeanDeserializerBase.java:1719)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:290)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
at com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1682)
at
{code:java|title=Malformed payload for creating a classification}
{
"classificationDefs": [
{
"name": "tag_1",
}
]
}
{code}
{code:java|title=Malformed payload for creating a classification}
{
"classificationDefs": [
{
"name": "tag_1"
},
]
}{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-3973) Inappropriate message on performing create with non-readable super type
[
https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264721#comment-17264721
]
chaitali borole edited comment on ATLAS-3973 at 1/14/21, 9:45 AM:
--
[~dharshmk],
I didn't find this issue reproducible here
Kindly resolve the issue.
CC:[~nixon],
was (Author: chaitali):
[~dharshmk],
I didn't find this issue reproducible here
Kindly resolve the issue.
> Inappropriate message on performing create with non-readable super type
> ---
>
> Key: ATLAS-3973
> URL: https://issues.apache.org/jira/browse/ATLAS-3973
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
> Received message
> {code:java}
> {u'errorCode': u'ATLAS-403-00-001', u'errorMessage': u'hrt_qa is not
> authorized to perform read type-def of
> categoryCLASSIFICATIONnon_read_classification_ufvQK'}
> {code}
>
> Expected message
> {code:java}
> hrt_qa is not authorized to perform create classification-def
> with non-readable classification
> {code}
> or something similar, that conveys the right message. The current error
> message seems very confusing. It conveys about read when performing a create
> operation
> Also the message has incorrect spacing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3973) Inappropriate message on performing create with non-readable super type
[
https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264721#comment-17264721
]
chaitali borole commented on ATLAS-3973:
[~dharshmk],
I didn't find this issue reproducible here
Kindly resolve the issue.
> Inappropriate message on performing create with non-readable super type
> ---
>
> Key: ATLAS-3973
> URL: https://issues.apache.org/jira/browse/ATLAS-3973
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: chaitali borole
>Priority: Major
>
> Received message
> {code:java}
> {u'errorCode': u'ATLAS-403-00-001', u'errorMessage': u'hrt_qa is not
> authorized to perform read type-def of
> categoryCLASSIFICATIONnon_read_classification_ufvQK'}
> {code}
>
> Expected message
> {code:java}
> hrt_qa is not authorized to perform create classification-def
> with non-readable classification
> {code}
> or something similar, that conveys the right message. The current error
> message seems very confusing. It conveys about read when performing a create
> operation
> Also the message has incorrect spacing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
