[jira] [Updated] (ATLAS-4855) Atlas - Upgrade Nimbus-JOSE-JWT to 9.37.3
[ https://issues.apache.org/jira/browse/ATLAS-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4855: --- Description: Atlas is currently pulling in nimbus-jose-jwt 9.8.1. Upgrate it to 9.37.3 > Atlas - Upgrade Nimbus-JOSE-JWT to 9.37.3 > - > > Key: ATLAS-4855 > URL: https://issues.apache.org/jira/browse/ATLAS-4855 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Atlas is currently pulling in nimbus-jose-jwt 9.8.1. Upgrate it to 9.37.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4855) Atlas - Upgrade Nimbus-JOSE-JWT to 9.37.3
Mandar Ambawane created ATLAS-4855: -- Summary: Atlas - Upgrade Nimbus-JOSE-JWT to 9.37.3 Key: ATLAS-4855 URL: https://issues.apache.org/jira/browse/ATLAS-4855 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4754) Download Search with Basic Search gives java.io.FileNotFoundException
[
https://issues.apache.org/jira/browse/ATLAS-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-4754.
Resolution: Fixed
Default value for the download directory will be read from system property
"user.dir" instead of property "atlas.home"
> Download Search with Basic Search gives java.io.FileNotFoundException
> -
>
> Key: ATLAS-4754
> URL: https://issues.apache.org/jira/browse/ATLAS-4754
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Abhishek Pal
>Assignee: Mandar Ambawane
>Priority: Major
>
> Currently when trying to download search results, the download task is stuck
> on pending.
> Upon checking the logs the following error is being seen:
> {code:java|title=application.log}
> 2023-05-17 22:09:47,321 INFO - [etp1158258131-199 -
> a6302f98-7e3d-4cbc-bd06-883fbfa21d11:] ~ TaskManagement: Processing stats:
> total=1, sinceLastStatsReport=2 completedWithErrors=1, succeded=0
> (TaskExecutor$TaskLogger:166)
> 2023-05-17 22:09:47,330 ERROR - [atlas-task-0-etp1158258131-282 -
> b9a5a4ef-6e3f-440c-9f65-d446a6da9720:] ~ Task:
> f4e26459-746f-4f31-90db-144c31a9696f: Error performing task!
> (SearchResultDownloadTask:126)
> java.io.FileNotFoundException:
> /search_result_downloads//.csv (No such file
> or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:237)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:187)
> at java.base/java.io.FileWriter.(FileWriter.java:96)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.generateCSVFileFromSearchResult(SearchResultDownloadTask.java:185)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.run(SearchResultDownloadTask.java:163)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.perform(SearchResultDownloadTask.java:122)
> at org.apache.atlas.tasks.AbstractTask.run(AbstractTask.java:33)
> at
> org.apache.atlas.tasks.TaskExecutor$TaskConsumer.performTask(TaskExecutor.java:150)
> at org.apache.atlas.tasks.TaskExecutor$TaskConsumer.run(TaskExecutor.java:109)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834){code}
> h2. Steps to Reproduce:
> h4. Create type: test_download_entity
> {code:java|title=/api/atlas/v2/types/typedefs}
> {
> "enumDefs": [],
> "structDefs": [],
> "classificationDefs": [],
> "entityDefs": [
> {
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name": "type_str",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> }
> ],
> "description": "description",
> "name": "test_download_entity",
> "guid": "-32062751815011",
> "category": "ENTITY",
> "superTypes": []
> }
> ],
> "relationshipDefs": [],
> "businessMetadataDefs": []
> }
> {code}
> h4. Create entity of type: test_download_entity
> {code:java|title=/api/atlas/v2/entity/bulk}
> {
> "entities": [{
> "typeName": "test_download_entity",
> "attributes": {
> "name": "downloadable_entity_1",
> "type_str": "str1"
> },
> "guid": "-08727943682221"
> },
> {
> "typeName": "test_download_entity",
> "attributes": {
> "name": "downloadable_entity_2",
> "type_str": "str2"
> },
>
[jira] [Created] (ATLAS-4819) Get default relationship-type of an entity-type which has relationships with different entity-types on same attribute
Mandar Ambawane created ATLAS-4819: -- Summary: Get default relationship-type of an entity-type which has relationships with different entity-types on same attribute Key: ATLAS-4819 URL: https://issues.apache.org/jira/browse/ATLAS-4819 Project: Atlas Issue Type: Bug Components: atlas-core, atlas-intg Reporter: Mandar Ambawane Assignee: Mandar Ambawane When an entity-type has relationships with other entity-types on same attribute and when the relationship type information is not provided. This might result in Atlas picking the random relationship-type for the current entity type. Which may lead to "Invalid relationshipDef" exceptions while creating entities / updating entities / migration import. This patch allows user to provide the default value for the relationship-type for particular entity-type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4666) Intermittently, the audits for creation of hive_db registered are different than expected.
[ https://issues.apache.org/jira/browse/ATLAS-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4666. Resolution: Fixed > Intermittently, the audits for creation of hive_db registered are different > than expected. > -- > > Key: ATLAS-4666 > URL: https://issues.apache.org/jira/browse/ATLAS-4666 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Mandar Ambawane >Priority: Major > > Sometimes, when I create a hive database and then check for the same in > Atlas, the audits tab shows unexpected audit entries: it shows two audit > entries both marked as 'Entity Updated' rather than showing a 'Entity > Created' audit entry anywhere. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4678) Restrict Relationship Typedef creation if "relationshipCategory" value is not provided
[ https://issues.apache.org/jira/browse/ATLAS-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4678. Resolution: Fixed > Restrict Relationship Typedef creation if "relationshipCategory" value is not > provided > -- > > Key: ATLAS-4678 > URL: https://issues.apache.org/jira/browse/ATLAS-4678 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4678) Restrict Relationship Typedef creation if "relationshipCategory" value is not provided
[ https://issues.apache.org/jira/browse/ATLAS-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4678: -- Assignee: Mandar Ambawane > Restrict Relationship Typedef creation if "relationshipCategory" value is not > provided > -- > > Key: ATLAS-4678 > URL: https://issues.apache.org/jira/browse/ATLAS-4678 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4754) Download Search with Basic Search gives java.io.FileNotFoundException
[
https://issues.apache.org/jira/browse/ATLAS-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4754:
---
Component/s: atlas-core
(was: atlas-webui)
> Download Search with Basic Search gives java.io.FileNotFoundException
> -
>
> Key: ATLAS-4754
> URL: https://issues.apache.org/jira/browse/ATLAS-4754
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Abhishek Pal
>Assignee: Mandar Ambawane
>Priority: Major
>
> Currently when trying to download search results, the download task is stuck
> on pending.
> Upon checking the logs the following error is being seen:
> {code:java|title=application.log}
> 2023-05-17 22:09:47,321 INFO - [etp1158258131-199 -
> a6302f98-7e3d-4cbc-bd06-883fbfa21d11:] ~ TaskManagement: Processing stats:
> total=1, sinceLastStatsReport=2 completedWithErrors=1, succeded=0
> (TaskExecutor$TaskLogger:166)
> 2023-05-17 22:09:47,330 ERROR - [atlas-task-0-etp1158258131-282 -
> b9a5a4ef-6e3f-440c-9f65-d446a6da9720:] ~ Task:
> f4e26459-746f-4f31-90db-144c31a9696f: Error performing task!
> (SearchResultDownloadTask:126)
> java.io.FileNotFoundException:
> /search_result_downloads//.csv (No such file
> or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:237)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:187)
> at java.base/java.io.FileWriter.(FileWriter.java:96)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.generateCSVFileFromSearchResult(SearchResultDownloadTask.java:185)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.run(SearchResultDownloadTask.java:163)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.perform(SearchResultDownloadTask.java:122)
> at org.apache.atlas.tasks.AbstractTask.run(AbstractTask.java:33)
> at
> org.apache.atlas.tasks.TaskExecutor$TaskConsumer.performTask(TaskExecutor.java:150)
> at org.apache.atlas.tasks.TaskExecutor$TaskConsumer.run(TaskExecutor.java:109)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834){code}
> h2. Steps to Reproduce:
> h4. Create type: test_download_entity
> {code:java|title=/api/atlas/v2/types/typedefs}
> {
> "enumDefs": [],
> "structDefs": [],
> "classificationDefs": [],
> "entityDefs": [
> {
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name": "type_str",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> }
> ],
> "description": "description",
> "name": "test_download_entity",
> "guid": "-32062751815011",
> "category": "ENTITY",
> "superTypes": []
> }
> ],
> "relationshipDefs": [],
> "businessMetadataDefs": []
> }
> {code}
> h4. Create entity of type: test_download_entity
> {code:java|title=/api/atlas/v2/entity/bulk}
> {
> "entities": [{
> "typeName": "test_download_entity",
> "attributes": {
> "name": "downloadable_entity_1",
> "type_str": "str1"
> },
> "guid": "-08727943682221"
> },
> {
> "typeName": "test_download_entity",
> "attributes": {
> "name": "downloadable_entity_2",
> "type_str": "str2"
> },
> "guid": "-0872794368"
> }
> ]
>
[jira] [Assigned] (ATLAS-4754) Download Search with Basic Search gives java.io.FileNotFoundException
[
https://issues.apache.org/jira/browse/ATLAS-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-4754:
--
Assignee: Mandar Ambawane
> Download Search with Basic Search gives java.io.FileNotFoundException
> -
>
> Key: ATLAS-4754
> URL: https://issues.apache.org/jira/browse/ATLAS-4754
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Abhishek Pal
>Assignee: Mandar Ambawane
>Priority: Major
>
> Currently when trying to download search results, the download task is stuck
> on pending.
> Upon checking the logs the following error is being seen:
> {code:java|title=application.log}
> 2023-05-17 22:09:47,321 INFO - [etp1158258131-199 -
> a6302f98-7e3d-4cbc-bd06-883fbfa21d11:] ~ TaskManagement: Processing stats:
> total=1, sinceLastStatsReport=2 completedWithErrors=1, succeded=0
> (TaskExecutor$TaskLogger:166)
> 2023-05-17 22:09:47,330 ERROR - [atlas-task-0-etp1158258131-282 -
> b9a5a4ef-6e3f-440c-9f65-d446a6da9720:] ~ Task:
> f4e26459-746f-4f31-90db-144c31a9696f: Error performing task!
> (SearchResultDownloadTask:126)
> java.io.FileNotFoundException:
> /search_result_downloads//.csv (No such file
> or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:237)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:187)
> at java.base/java.io.FileWriter.(FileWriter.java:96)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.generateCSVFileFromSearchResult(SearchResultDownloadTask.java:185)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.run(SearchResultDownloadTask.java:163)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.perform(SearchResultDownloadTask.java:122)
> at org.apache.atlas.tasks.AbstractTask.run(AbstractTask.java:33)
> at
> org.apache.atlas.tasks.TaskExecutor$TaskConsumer.performTask(TaskExecutor.java:150)
> at org.apache.atlas.tasks.TaskExecutor$TaskConsumer.run(TaskExecutor.java:109)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834){code}
> h2. Steps to Reproduce:
> h4. Create type: test_download_entity
> {code:java|title=/api/atlas/v2/types/typedefs}
> {
> "enumDefs": [],
> "structDefs": [],
> "classificationDefs": [],
> "entityDefs": [
> {
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name": "type_str",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> }
> ],
> "description": "description",
> "name": "test_download_entity",
> "guid": "-32062751815011",
> "category": "ENTITY",
> "superTypes": []
> }
> ],
> "relationshipDefs": [],
> "businessMetadataDefs": []
> }
> {code}
> h4. Create entity of type: test_download_entity
> {code:java|title=/api/atlas/v2/entity/bulk}
> {
> "entities": [{
> "typeName": "test_download_entity",
> "attributes": {
> "name": "downloadable_entity_1",
> "type_str": "str1"
> },
> "guid": "-08727943682221"
> },
> {
> "typeName": "test_download_entity",
> "attributes": {
> "name": "downloadable_entity_2",
> "type_str": "str2"
> },
> "guid": "-0872794368"
> }
> ]
> }{code}
> h4. Search for type
[jira] [Resolved] (ATLAS-4733) Download Basic and DSL search results
[ https://issues.apache.org/jira/browse/ATLAS-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4733. Resolution: Fixed > Download Basic and DSL search results > - > > Key: ATLAS-4733 > URL: https://issues.apache.org/jira/browse/ATLAS-4733 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > This ticket tracks the Server side changes required for the Search result > download task. > From server side, each download request is considered as a separate thread > which will run in the background and will generate the csv file according to > the inputs provided. > The generated files will be stored in the specific location (which is > configurable). > A scheduler will be run to delete the old files. In this case, the scheduler > interval and file expiry time is also configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4733) Download Basic and DSL search results
Mandar Ambawane created ATLAS-4733: -- Summary: Download Basic and DSL search results Key: ATLAS-4733 URL: https://issues.apache.org/jira/browse/ATLAS-4733 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane This ticket tracks the Server side changes required for the Search result download task. >From server side, each download request is considered as a separate thread >which will run in the background and will generate the csv file according to >the inputs provided. The generated files will be stored in the specific location (which is configurable). A scheduler will be run to delete the old files. In this case, the scheduler interval and file expiry time is also configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4576) Backward compatibility for check provided for AttributeName in Parent and Child TypeDef
[ https://issues.apache.org/jira/browse/ATLAS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4576. Resolution: Fixed > Backward compatibility for check provided for AttributeName in Parent and > Child TypeDef > --- > > Key: ATLAS-4576 > URL: https://issues.apache.org/jira/browse/ATLAS-4576 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Currently we have provided 2 checks for the Attribute Name: > [ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872] > Restrict typedef creation when a child type attribute conflicts with parent > type attribute of same name > [ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522] > Updating typedef with new supertype should be allowed only if attributes are > unique compared to other existing supertypes > But in the earlier versions these checks were not there. So there may be a > chance of Atlas environment having such data where these checks can cause > problems at the time: > 1. Atlas Startup. > 2. Creating new typedefs > This patch handles these scenarios and provides backward compatibility for > these 2 changes mentioned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4495) Glossary section takes longer time to load when Glossaries have large number of Categories and Terms associated with them
[ https://issues.apache.org/jira/browse/ATLAS-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4495. Resolution: Fixed > Glossary section takes longer time to load when Glossaries have large number > of Categories and Terms associated with them > - > > Key: ATLAS-4495 > URL: https://issues.apache.org/jira/browse/ATLAS-4495 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4678) Restrict Relationship Typedef creation if "relationshipCategory" value is not provided
Mandar Ambawane created ATLAS-4678: -- Summary: Restrict Relationship Typedef creation if "relationshipCategory" value is not provided Key: ATLAS-4678 URL: https://issues.apache.org/jira/browse/ATLAS-4678 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4668) When classification is created with multiple super types having same attributes , Atlas doesn't throw an exception
Mandar Ambawane created ATLAS-4668: -- Summary: When classification is created with multiple super types having same attributes , Atlas doesn't throw an exception Key: ATLAS-4668 URL: https://issues.apache.org/jira/browse/ATLAS-4668 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane When an entity type is created with multiple super types having same attribute name, Atlas throws exception. Ex: if there are 2 types: type1 - attr1, attr2 type2- attr1, attr2 Both types cant be added to super type to type3 since both type1 and type2 have same attribute - attr1 But it is not the case with classification. Atlas allows to create a classification with multiple super types having same attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4668) When classification is created with multiple super types having same attributes , Atlas doesn't throw an exception
[ https://issues.apache.org/jira/browse/ATLAS-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4668: --- Issue Type: Bug (was: Improvement) > When classification is created with multiple super types having same > attributes , Atlas doesn't throw an exception > -- > > Key: ATLAS-4668 > URL: https://issues.apache.org/jira/browse/ATLAS-4668 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > When an entity type is created with multiple super types having same > attribute name, Atlas throws exception. > Ex: > if there are 2 types: > type1 - attr1, attr2 > type2- attr1, attr2 > Both types cant be added to super type to type3 since both type1 and type2 > have same attribute - attr1 > > But it is not the case with classification. Atlas allows to create a > classification with multiple super types having same attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4666) Intermittently, the audits for creation of hive_db registered are different than expected.
[ https://issues.apache.org/jira/browse/ATLAS-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4666: -- Assignee: Mandar Ambawane > Intermittently, the audits for creation of hive_db registered are different > than expected. > -- > > Key: ATLAS-4666 > URL: https://issues.apache.org/jira/browse/ATLAS-4666 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Mandar Ambawane >Priority: Major > > Sometimes, when I create a hive database and then check for the same in > Atlas, the audits tab shows unexpected audit entries: it shows two audit > entries both marked as 'Entity Updated' rather than showing a 'Entity > Created' audit entry anywhere. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4655) Add Glossary details in Entity - Term Relationship attribute
[
https://issues.apache.org/jira/browse/ATLAS-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4655:
---
Component/s: atlas-core
> Add Glossary details in Entity - Term Relationship attribute
>
>
> Key: ATLAS-4655
> URL: https://issues.apache.org/jira/browse/ATLAS-4655
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Add "{*}glossaryDetails{*}" attribute in RelationshipTypeDef
> "{*}AtlasGlossarySemanticAssignment{*}".
> This will help in showing the Glossary details of the associated Term in the
> Entity details page on UI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4655) Add Glossary details in Entity - Term Relationship attribute
[
https://issues.apache.org/jira/browse/ATLAS-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4655:
---
Description:
Add "{*}glossaryDetails{*}" attribute in RelationshipTypeDef
"{*}AtlasGlossarySemanticAssignment{*}".
This will help in showing the Glossary details of the associated Term in the
Entity details page on UI.
> Add Glossary details in Entity - Term Relationship attribute
>
>
> Key: ATLAS-4655
> URL: https://issues.apache.org/jira/browse/ATLAS-4655
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Add "{*}glossaryDetails{*}" attribute in RelationshipTypeDef
> "{*}AtlasGlossarySemanticAssignment{*}".
> This will help in showing the Glossary details of the associated Term in the
> Entity details page on UI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4655) Add Glossary details in Entity - Term Relationship attribute
Mandar Ambawane created ATLAS-4655: -- Summary: Add Glossary details in Entity - Term Relationship attribute Key: ATLAS-4655 URL: https://issues.apache.org/jira/browse/ATLAS-4655 Project: Atlas Issue Type: Improvement Reporter: Mandar Ambawane -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4655) Add Glossary details in Entity - Term Relationship attribute
[ https://issues.apache.org/jira/browse/ATLAS-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4655: -- Assignee: Mandar Ambawane > Add Glossary details in Entity - Term Relationship attribute > > > Key: ATLAS-4655 > URL: https://issues.apache.org/jira/browse/ATLAS-4655 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4605) Prevent NullPointerException when Atlas Vertex is empty because of corrupted data.
[ https://issues.apache.org/jira/browse/ATLAS-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4605: --- Attachment: ATLAS-4605.patch > Prevent NullPointerException when Atlas Vertex is empty because of corrupted > data. > -- > > Key: ATLAS-4605 > URL: https://issues.apache.org/jira/browse/ATLAS-4605 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Attachments: ATLAS-4605.patch > > > Because of corrupted data, there may be a chance of having AtlasVertex as an > empty, which means AtlasVertex does not have any property present in it. > This can cause NullPointerException while populating System attributes as > well Normal attributes for AtlasEntity object. > To avoid NullPointerException we need to skip such vertices, so that they > cannot be used to populate system attributes and normal attributes. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ATLAS-4605) Prevent NullPointerException when Atlas Vertex is empty because of corrupted data.
Mandar Ambawane created ATLAS-4605: -- Summary: Prevent NullPointerException when Atlas Vertex is empty because of corrupted data. Key: ATLAS-4605 URL: https://issues.apache.org/jira/browse/ATLAS-4605 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane Because of corrupted data, there may be a chance of having AtlasVertex as an empty, which means AtlasVertex does not have any property present in it. This can cause NullPointerException while populating System attributes as well Normal attributes for AtlasEntity object. To avoid NullPointerException we need to skip such vertices, so that they cannot be used to populate system attributes and normal attributes. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (ATLAS-4572) Improved Soft Delete behaviour for relationships edges
[ https://issues.apache.org/jira/browse/ATLAS-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4572. Resolution: Fixed > Improved Soft Delete behaviour for relationships edges > -- > > Key: ATLAS-4572 > URL: https://issues.apache.org/jira/browse/ATLAS-4572 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Earlier the process for soft deleting relationships involved unnecessary > invocation of delete methods on already deleted Relationship edges. > This would consume a lot of time on an entity which has a long list of soft > deleted relationships. > This changes implements a check on relationship edges, identifying already > deleted relationship edges and avoiding invocation of delete method on them. > Thus only allowing deletion of active relationship edges. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (ATLAS-4572) Improved Soft Delete behaviour for relationships edges
[ https://issues.apache.org/jira/browse/ATLAS-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4572: --- Summary: Improved Soft Delete behaviour for relationships edges (was: Improved Soft Delete behavior for relationships edges) > Improved Soft Delete behaviour for relationships edges > -- > > Key: ATLAS-4572 > URL: https://issues.apache.org/jira/browse/ATLAS-4572 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Earlier the process for soft deleting relationships involved unnecessary > invocation of delete methods on already deleted Relationship edges. > This would consume a lot of time on an entity which has a long list of soft > deleted relationships. > This changes implements a check on relationship edges, identifying already > deleted relationship edges and avoiding invocation of delete method on them. > Thus only allowing deletion of active relationship edges. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (ATLAS-4576) Backward compatibility for check provided for AttributeName in Parent and Child TypeDef
[ https://issues.apache.org/jira/browse/ATLAS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4576: -- Assignee: Mandar Ambawane > Backward compatibility for check provided for AttributeName in Parent and > Child TypeDef > --- > > Key: ATLAS-4576 > URL: https://issues.apache.org/jira/browse/ATLAS-4576 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Currently we have provided 2 checks for the Attribute Name: > [ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872] > Restrict typedef creation when a child type attribute conflicts with parent > type attribute of same name > [ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522] > Updating typedef with new supertype should be allowed only if attributes are > unique compared to other existing supertypes > But in the earlier versions these checks were not there. So there may be a > chance of Atlas environment having such data where these checks can cause > problems at the time: > 1. Atlas Startup. > 2. Creating new typedefs > This patch handles these scenarios and provides backward compatibility for > these 2 changes mentioned. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4576) Backward compatibility for check provided for AttributeName in Parent and Child TypeDef
[ https://issues.apache.org/jira/browse/ATLAS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4576: --- Summary: Backward compatibility for check provided for AttributeName in Parent and Child TypeDef (was: Backward compatibility for check provided for AttributeName in Parent and Child Type) > Backward compatibility for check provided for AttributeName in Parent and > Child TypeDef > --- > > Key: ATLAS-4576 > URL: https://issues.apache.org/jira/browse/ATLAS-4576 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Priority: Major > > Currently we have provided 2 checks for the Attribute Name: > [ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872] > Restrict typedef creation when a child type attribute conflicts with parent > type attribute of same name > [ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522] > Updating typedef with new supertype should be allowed only if attributes are > unique compared to other existing supertypes > But in the earlier versions these checks were not there. So there may be a > chance of Atlas environment having such data where these checks can cause > problems at the time: > 1. Atlas Startup. > 2. Creating new typedefs > This patch handles these scenarios and provides backward compatibility for > these 2 changes mentioned. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4576) Backward compatibility for check provided for AttributeName in Parent and Child Type
[ https://issues.apache.org/jira/browse/ATLAS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4576: --- Summary: Backward compatibility for check provided for AttributeName in Parent and Child Type (was: Backward compatibility for check provided for Attribute Name in Parent and Child Type) > Backward compatibility for check provided for AttributeName in Parent and > Child Type > > > Key: ATLAS-4576 > URL: https://issues.apache.org/jira/browse/ATLAS-4576 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Priority: Major > > Currently we have provided 2 checks for the Attribute Name: > [ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872] > Restrict typedef creation when a child type attribute conflicts with parent > type attribute of same name > [ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522] > Updating typedef with new supertype should be allowed only if attributes are > unique compared to other existing supertypes > But in the earlier versions these checks were not there. So there may be a > chance of Atlas environment having such data where these checks can cause > problems at the time: > 1. Atlas Startup. > 2. Creating new typedefs > This patch handles these scenarios and provides backward compatibility for > these 2 changes mentioned. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4576) Backward compatibility for check provided for Attribute Name in Parent and Child Type
Mandar Ambawane created ATLAS-4576: -- Summary: Backward compatibility for check provided for Attribute Name in Parent and Child Type Key: ATLAS-4576 URL: https://issues.apache.org/jira/browse/ATLAS-4576 Project: Atlas Issue Type: Improvement Reporter: Mandar Ambawane Currently we have provided 2 checks for the Attribute Name: [ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872] Restrict typedef creation when a child type attribute conflicts with parent type attribute of same name [ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522] Updating typedef with new supertype should be allowed only if attributes are unique compared to other existing supertypes But in the earlier versions these checks were not there. So there may be a chance of Atlas environment having such data where these checks can cause problems at the time: 1. Atlas Startup. 2. Creating new typedefs This patch handles these scenarios and provides backward compatibility for these 2 changes mentioned. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4572) Improved Soft Delete behavior for relationships edges
Mandar Ambawane created ATLAS-4572: -- Summary: Improved Soft Delete behavior for relationships edges Key: ATLAS-4572 URL: https://issues.apache.org/jira/browse/ATLAS-4572 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane Earlier the process for soft deleting relationships involved unnecessary invocation of delete methods on already deleted Relationship edges. This would consume a lot of time on an entity which has a long list of soft deleted relationships. This changes implements a check on relationship edges, identifying already deleted relationship edges and avoiding invocation of delete method on them. Thus only allowing deletion of active relationship edges. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4556) Add Ozone "ofs" scheme support for external tables created through hive.
[ https://issues.apache.org/jira/browse/ATLAS-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4556: --- Issue Type: Bug (was: Improvement) > Add Ozone "ofs" scheme support for external tables created through hive. > > > Key: ATLAS-4556 > URL: https://issues.apache.org/jira/browse/ATLAS-4556 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > When we provide ozone key as a path for an external table in hive, > corresponding Ozone entities of type "Ozone_Volume", "Ozone_Bucket", > "Ozone_Key" etc. get created. > Currently in Atlas, code supports the above in "o3fs" ozone scheme. > Need to provide improved support in "ofs" scheme, same as that of "o3fs". -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (ATLAS-4556) Add Ozone "ofs" scheme support for external tables created through hive.
[ https://issues.apache.org/jira/browse/ATLAS-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4556. Resolution: Fixed > Add Ozone "ofs" scheme support for external tables created through hive. > > > Key: ATLAS-4556 > URL: https://issues.apache.org/jira/browse/ATLAS-4556 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > When we provide ozone key as a path for an external table in hive, > corresponding Ozone entities of type "Ozone_Volume", "Ozone_Bucket", > "Ozone_Key" etc. get created. > Currently in Atlas, code supports the above in "o3fs" ozone scheme. > Need to provide improved support in "ofs" scheme, same as that of "o3fs". -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4556) Add Ozone "ofs" scheme support for external tables created through hive.
Mandar Ambawane created ATLAS-4556: -- Summary: Add Ozone "ofs" scheme support for external tables created through hive. Key: ATLAS-4556 URL: https://issues.apache.org/jira/browse/ATLAS-4556 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane When we provide ozone key as a path for an external table in hive, corresponding Ozone entities of type "Ozone_Volume", "Ozone_Bucket", "Ozone_Key" etc. get created. Currently in Atlas, code supports the above in "o3fs" ozone scheme. Need to provide improved support in "ofs" scheme, same as that of "o3fs". -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (ATLAS-4556) Add Ozone "ofs" scheme support for external tables created through hive.
[ https://issues.apache.org/jira/browse/ATLAS-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4556: -- Assignee: Mandar Ambawane > Add Ozone "ofs" scheme support for external tables created through hive. > > > Key: ATLAS-4556 > URL: https://issues.apache.org/jira/browse/ATLAS-4556 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > When we provide ozone key as a path for an external table in hive, > corresponding Ozone entities of type "Ozone_Volume", "Ozone_Bucket", > "Ozone_Key" etc. get created. > Currently in Atlas, code supports the above in "o3fs" ozone scheme. > Need to provide improved support in "ofs" scheme, same as that of "o3fs". -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4473) Glossary Terms Bulk Create Performance Improvement
[ https://issues.apache.org/jira/browse/ATLAS-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4473: --- Attachment: ATLAS-4473-V2.patch > Glossary Terms Bulk Create Performance Improvement > -- > > Key: ATLAS-4473 > URL: https://issues.apache.org/jira/browse/ATLAS-4473 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Attachments: ATLAS-4473-V2.patch, ATLAS-4473.patch > > > While creating GlossaryTerms we need information about Glossary and > GlossaryCategory (if present) > As per current design, > When every Term is created, respective Glossary and Category objects are > fetched from db and they are populated with unwanted information. > In case of bulk creation, > Even if multiple Terms have same Glossary and Category associated with them, > every time these objects are fetched from db and they are populated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (ATLAS-4495) Glossary section takes longer time to load when Glossaries have large number of Categories and Terms associated with them
[ https://issues.apache.org/jira/browse/ATLAS-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4495: -- Assignee: Mandar Ambawane > Glossary section takes longer time to load when Glossaries have large number > of Categories and Terms associated with them > - > > Key: ATLAS-4495 > URL: https://issues.apache.org/jira/browse/ATLAS-4495 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4495) Glossary section takes longer time to load when Glossaries have large number of Categories and Terms associated with them
Mandar Ambawane created ATLAS-4495: -- Summary: Glossary section takes longer time to load when Glossaries have large number of Categories and Terms associated with them Key: ATLAS-4495 URL: https://issues.apache.org/jira/browse/ATLAS-4495 Project: Atlas Issue Type: Improvement Reporter: Mandar Ambawane -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4473) Glossary Terms Bulk Create Performance Improvement
Mandar Ambawane created ATLAS-4473: -- Summary: Glossary Terms Bulk Create Performance Improvement Key: ATLAS-4473 URL: https://issues.apache.org/jira/browse/ATLAS-4473 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane While creating GlossaryTerms we need information about Glossary and GlossaryCategory (if present) As per current design, When every Term is created, respective Glossary and Category objects are fetched from db and they are populated with unwanted information. In case of bulk creation, Even if multiple Terms have same Glossary and Category associated with them, every time these objects are fetched from db and they are populated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (ATLAS-3694) [Business Metadata] Max length defined for attributes of string type is not getting enforced
[
https://issues.apache.org/jira/browse/ATLAS-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-3694.
Resolution: Fixed
> [Business Metadata] Max length defined for attributes of string type is not
> getting enforced
>
>
> Key: ATLAS-3694
> URL: https://issues.apache.org/jira/browse/ATLAS-3694
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 7.49.51 PM.png, Screenshot
> 2020-03-26 at 7.51.13 PM.png
>
>
> Even when the max length applicable to an attribute is defined as 10, I was
> able to add all the alphabets of an english language i.e. a-z, 26 in length,
> as the attribute value.
> This is reproducible both from API as well as UI.
> {code:java}
> curl -X POST \
>
> 'https://:31443/api/atlas/v2/entity/guid/ab29815d-6d20-44ee-b426-8fba946b72a5/businessmetata?isOverwrite=true'
> \
> -H 'cache-control: no-cache' \
> -H 'content-type: application/json' \
> -H 'postman-token: 6c5a0476-ac64-57c9-5845-cbea945fdf99' \
> -H 'x-xsrf-header: \"\"' \
> -d '{"String Length":{"Name":"abcdefghijklmnopqrstuvwxyz"}}' {code}
> Screenshots attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4392) The displayed names in a relationship should be sorted
[ https://issues.apache.org/jira/browse/ATLAS-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17396038#comment-17396038 ] Mandar Ambawane commented on ATLAS-4392: When we have a 1:N relationship then we able to see the list of connected entities in the Atlas UI. These entities don't seem to be sorted in a meaningful way. The correct way would be if they are sorted in alphabetical order. > The displayed names in a relationship should be sorted > -- > > Key: ATLAS-4392 > URL: https://issues.apache.org/jira/browse/ATLAS-4392 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4392) The displayed names in a relationship should be sorted
Mandar Ambawane created ATLAS-4392: -- Summary: The displayed names in a relationship should be sorted Key: ATLAS-4392 URL: https://issues.apache.org/jira/browse/ATLAS-4392 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-3881) Relationships reflect only on one end
[ https://issues.apache.org/jira/browse/ATLAS-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17393205#comment-17393205 ] Mandar Ambawane edited comment on ATLAS-3881 at 8/6/21, 12:03 PM: -- *isLegacyAttribute* flag and *relationshipLabel* plays important role in deciding the direction of the Relationship Edge. In this case: In Relationship Typedef, Both the EndDefs have *isLegacyAttribute* *=* *true*. Also, in Relationship Typedef, we are not providing any *relationshipLabel*. Because of above reasons, Relationship Edge is created in *opposite direction*. For reference: [https://github.com/apache/atlas/blob/master/intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java#L181] Hence we are not able to see Relationship attributes in *"File"* entity page. This is working as per current design. If you provide *relationshipLabel* while creating Relationship Type. Then this issue will not occur. CC: [~sarath] [~jayendrap] was (Author: mandar_va): *isLegacyAttribute* flag and *relationshipLabel* plays important role in deciding the direction of the Relationship Edge. In this case: In Relationship Typedef, Both the EndDefs have *isLegacyAttribute* *=* *true*. Also, in Relationship Typedef, we are not providing any *relationshipLabel*. Because of above reasons, Relationship Edge is created in *opposite direction*. For reference: [https://github.com/apache/atlas/blob/master/intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java#L181] Hence we are not able to see Relationship attributes in *"File"* entity page. This is working as per current design. If you provide *relationshipLabel* while creating Relationship Type. Then this issue will not occur. > Relationships reflect only on one end > - > > Key: ATLAS-3881 > URL: https://issues.apache.org/jira/browse/ATLAS-3881 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 2.0.0 >Reporter: Farida Shafik >Assignee: Mandar Ambawane >Priority: Major > Attachments: FileFieldJSON.json > > > Have two entities: file and field > Trying to link both with a relationship called file_field > Set file_field as a COMPOSITION relationship with file containing field > Created file, then while creating field, set the created file as its file. > However, when opening the file's page, did not find the relationship set with > the above field. Instead have to update the file manually to add the field. > Attached below is the json body sent when creating the types and definitions > at "/api/atlas/v2/types/typedefs" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3881) Relationships reflect only on one end
[ https://issues.apache.org/jira/browse/ATLAS-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-3881. Resolution: Not A Bug > Relationships reflect only on one end > - > > Key: ATLAS-3881 > URL: https://issues.apache.org/jira/browse/ATLAS-3881 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 2.0.0 >Reporter: Farida Shafik >Assignee: Mandar Ambawane >Priority: Major > Attachments: FileFieldJSON.json > > > Have two entities: file and field > Trying to link both with a relationship called file_field > Set file_field as a COMPOSITION relationship with file containing field > Created file, then while creating field, set the created file as its file. > However, when opening the file's page, did not find the relationship set with > the above field. Instead have to update the file manually to add the field. > Attached below is the json body sent when creating the types and definitions > at "/api/atlas/v2/types/typedefs" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3881) Relationships reflect only on one end
[ https://issues.apache.org/jira/browse/ATLAS-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17393205#comment-17393205 ] Mandar Ambawane commented on ATLAS-3881: *isLegacyAttribute* flag and *relationshipLabel* plays important role in deciding the direction of the Relationship Edge. In this case: In Relationship Typedef, Both the EndDefs have *isLegacyAttribute* *=* *true*. Also, in Relationship Typedef, we are not providing any *relationshipLabel*. Because of above reasons, Relationship Edge is created in *opposite direction*. For reference: [https://github.com/apache/atlas/blob/master/intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java#L181] Hence we are not able to see Relationship attributes in *"File"* entity page. This is working as per current design. If you provide *relationshipLabel* while creating Relationship Type. Then this issue will not occur. > Relationships reflect only on one end > - > > Key: ATLAS-3881 > URL: https://issues.apache.org/jira/browse/ATLAS-3881 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 2.0.0 >Reporter: Farida Shafik >Assignee: Mandar Ambawane >Priority: Major > Attachments: FileFieldJSON.json > > > Have two entities: file and field > Trying to link both with a relationship called file_field > Set file_field as a COMPOSITION relationship with file containing field > Created file, then while creating field, set the created file as its file. > However, when opening the file's page, did not find the relationship set with > the above field. Instead have to update the file manually to add the field. > Attached below is the json body sent when creating the types and definitions > at "/api/atlas/v2/types/typedefs" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3881) Relationships reflect only on one end
[ https://issues.apache.org/jira/browse/ATLAS-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-3881: -- Assignee: Mandar Ambawane > Relationships reflect only on one end > - > > Key: ATLAS-3881 > URL: https://issues.apache.org/jira/browse/ATLAS-3881 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 2.0.0 >Reporter: Farida Shafik >Assignee: Mandar Ambawane >Priority: Major > Attachments: FileFieldJSON.json > > > Have two entities: file and field > Trying to link both with a relationship called file_field > Set file_field as a COMPOSITION relationship with file containing field > Created file, then while creating field, set the created file as its file. > However, when opening the file's page, did not find the relationship set with > the above field. Instead have to update the file manually to add the field. > Attached below is the json body sent when creating the types and definitions > at "/api/atlas/v2/types/typedefs" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4103) While listing Purge operation records in Administration-Audits, shows 'Something went wrong' message
[ https://issues.apache.org/jira/browse/ATLAS-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4103. Resolution: Cannot Reproduce > While listing Purge operation records in Administration-Audits, shows > 'Something went wrong' message > > > Key: ATLAS-4103 > URL: https://issues.apache.org/jira/browse/ATLAS-4103 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Mandar Ambawane >Priority: Major > Attachments: Something_went_wrong_for_purge_operation_listing.png > > > Steps to Reproduce :: > # Soft delete/Purge any entity (purged through postman) > # Go to Administration-Audits tab to see the above record > # In Filter select Operation(atlas_operation)=Purge > Expected: The deleted entity details should have listed > Actual: Shows 'Something went wrong' message on UI and console shows '500 > Internal Server Error' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3935) Use Audit framework to capture audit entries for Import/Export operations
[ https://issues.apache.org/jira/browse/ATLAS-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-3935: --- Fix Version/s: 2.2.0 3.0.0 > Use Audit framework to capture audit entries for Import/Export operations > - > > Key: ATLAS-3935 > URL: https://issues.apache.org/jira/browse/ATLAS-3935 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3935-V2.patch, ATLAS-3935-V3.patch > > > By using Audit Framework, capture audit entries for Import/Export operations. > These audit entries can be seen under the "Audits" tab of Admin section. > *Add Import and Export specific information in Audit entry* > * Total no. of entities imported/ exported > * Total no. of entities imported/ exported of specific TypeDef > * Export operation Fetch Type -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3957) Use Audit framework to capture audit entries for "Server Start" and "Server In Active mode" (HA)
[ https://issues.apache.org/jira/browse/ATLAS-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-3957: --- Fix Version/s: 2.2.0 3.0.0 > Use Audit framework to capture audit entries for "Server Start" and "Server > In Active mode" (HA) > > > Key: ATLAS-3957 > URL: https://issues.apache.org/jira/browse/ATLAS-3957 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3957-V3.patch, ATLAS-3957.patch > > > By using Audit Framework, capture audit entries for "Server Start" and > "Server In Active mode" (HA) > These audit entries can be seen under the "Audits" tab of Admin section. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3984) Add UI Date Timezone and UI Date Format in Session api
[ https://issues.apache.org/jira/browse/ATLAS-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-3984: --- Fix Version/s: 2.2.0 3.0.0 > Add UI Date Timezone and UI Date Format in Session api > -- > > Key: ATLAS-3984 > URL: https://issues.apache.org/jira/browse/ATLAS-3984 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3984-V2.patch > > > Add UI Date Timezone and UI Date Format in Session api. > Provide a way to user to read these "UI Date Timezone" and "UI Date Format" > values from property file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4034) Export operation audit with result count 0 for empty exports is inconsistent
[
https://issues.apache.org/jira/browse/ATLAS-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4034:
---
Fix Version/s: 2.2.0
3.0.0
> Export operation audit with result count 0 for empty exports is inconsistent
>
>
> Key: ATLAS-4034
> URL: https://issues.apache.org/jira/browse/ATLAS-4034
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4034-ATLAS-4041.patch
>
>
> Export operation creates an audit with *count 0* for the following request:
> {code:java}
> {
> "itemsToExport": [
>
> ]
> }
> {code}
> But the following input does not create any audit entry : Please note the
> *{}* in the *itemsToExport* array
> {code:java}
> {
> "itemsToExport": [
> {}
> ]
> }
> {code}
> We need to keep the result consistent. Either create entry for the later with
> result count 0 or do not create an entry for the former
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4041) It will be good to have the operation status info of EXPORT operation in the Admin export audits
[
https://issues.apache.org/jira/browse/ATLAS-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4041:
---
Fix Version/s: 2.2.0
3.0.0
> It will be good to have the operation status info of EXPORT operation in the
> Admin export audits
>
>
> Key: ATLAS-4041
> URL: https://issues.apache.org/jira/browse/ATLAS-4041
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4034-ATLAS-4041.patch
>
>
> Currently we do not have information if the export operation is "PASS" or
> "FAIL" or "PARTIAL_PASS"
> It will be good to have this information
> Current output:
> {code}
> {
> "guid": "",
> "userName": "",
> "operation": "EXPORT",
> "params": "\{\"fetchType\":\"FULL\",\"matchType\":\"startsWith\"}",
> "startTime": 1605089955917,
> "endTime": 1605089957959,
> "clientId": "",
> "result": "\{\"hdfs_path\":1,\"dharshana\":1,\"hive_db\":1}",
> "resultCount": 3
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4135) [Atlas: Glossary Term Bulk Import] It will be good to ignore the glossaries and terms that are already present instead of failing the bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4135:
---
Fix Version/s: 2.2.0
3.0.0
> [Atlas: Glossary Term Bulk Import] It will be good to ignore the glossaries
> and terms that are already present instead of failing the bulk import
> -
>
> Key: ATLAS-4135
> URL: https://issues.apache.org/jira/browse/ATLAS-4135
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4135-ATLAS-4139.patch, Screenshot 2021-02-04 at
> 7.06.56 PM.png
>
>
> Consider the following scenario:
> Already available glossaries and terms:
> glossary_1 ==> term_1
> glossary_1 ==> term_2
> glossary_2 ==> term_1
> glossary_2 ==> term_2
>
> Now if the user is performing a bulk import and if glossary_1 ==> term_1 is
> part of the input, currently the call fails.
> {code:java}
> {errorCode: "ATLAS-500-00-016", errorMessage: "Error occurred while creating
> glossary term: {0}",…}errorCause: "Glossary term with qualifiedName
> term_1@aglossary_01 already exists"errorCode: "ATLAS-500-00-016"errorMessage:
> "Error occurred while creating glossary term: {0}" {code}
> Expectation:
> If it already exists, then just update the other field values eg, long
> description and the linked terms and do not fail
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4139) [Atlas: Glossary Term Bulk Import] When AdditionalAttributes is not provided in key:value format, the error message does not convey that
[
https://issues.apache.org/jira/browse/ATLAS-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4139:
---
Fix Version/s: 2.2.0
3.0.0
> [Atlas: Glossary Term Bulk Import] When AdditionalAttributes is not provided
> in key:value format, the error message does not convey that
>
>
> Key: ATLAS-4139
> URL: https://issues.apache.org/jira/browse/ATLAS-4139
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4139.patch, Screenshot 2021-02-05 at 4.07.46 PM.png
>
>
> Consider the following input for bulk import term_glossary
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1, "glossary_1 term_1 short description", "glossary_1 term_1
> long description", "Examples", "AB", "glossary_1 term_1 Usage", "random_key"
> {code}
> Here *AdditionalAttributes* is *random_key*
> When this is imported we get
> {code:java}
> errorCode: "ATLAS-500-00-001"errorMessage: "The uploaded file has not been
> processed due to the following errors : ↵[↵The Data in the uploaded file is
> incorrectly specified : random_key]" {code}
> It mentions The Data in the uploaded file is incorrectly specified :
> random_key
> It would be good to convey as "AdditionalAttributes has to a key:value pair"
> or something similar
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4146) [Atlas: Glossary] On updating the related terms, UI allows the user to add the already added term
[ https://issues.apache.org/jira/browse/ATLAS-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4146: --- Fix Version/s: 2.2.0 3.0.0 > [Atlas: Glossary] On updating the related terms, UI allows the user to add > the already added term > - > > Key: ATLAS-4146 > URL: https://issues.apache.org/jira/browse/ATLAS-4146 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-4146.patch, Screen Recording 2021-02-05 at 6.50.31 > PM.mov > > > Steps to repro: > # Create a glossary(glossary_1) and a few terms (term_1, term_2, term_3, > term_4, term_5) > # Click on term_1 and add related terms "alsoSee" > # Choose term_5 of glossary_1 > # Provide inputs and assign > # term_5 will be added as a related term > # Now, add one more related term and choose the same term_5 of glossary_1 > [UI allows this] > # Provide new input and assign > # The assignment will be successful > This makes the user think, that term_5 with new data is saved. But that is > not the case, only old data is present > Expectation: > Do not allow the user to assign the same term again. > If allowed, update the data with the new data > [^Screen Recording 2021-02-05 at 6.50.31 PM.mov] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4150) UI : __AtlasAuditEntry appearing in metrics window
[ https://issues.apache.org/jira/browse/ATLAS-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4150: --- Fix Version/s: 2.2.0 3.0.0 > UI : __AtlasAuditEntry appearing in metrics window > -- > > Key: ATLAS-4150 > URL: https://issues.apache.org/jira/browse/ATLAS-4150 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Mandar Ambawane >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-4150.patch, Screenshot from 2021-02-09 10-38-46.png > > > !Screenshot from 2021-02-09 10-38-46.png|width=584,height=432! > As seen in the above screenshot, entries for AtlasAuditEntry are visible. > That is an system internal entity and should ideally not be visible in the > metrics UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3625) Add Test cases for Namespace type creation and Namespace-Entity association
[ https://issues.apache.org/jira/browse/ATLAS-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-3625. Resolution: Fixed > Add Test cases for Namespace type creation and Namespace-Entity association > --- > > Key: ATLAS-3625 > URL: https://issues.apache.org/jira/browse/ATLAS-3625 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4105) table details are set to null for a dropped hbase_column_family
[ https://issues.apache.org/jira/browse/ATLAS-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4105. Resolution: Not A Bug > table details are set to null for a dropped hbase_column_family > --- > > Key: ATLAS-4105 > URL: https://issues.apache.org/jira/browse/ATLAS-4105 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Umesh Padashetty >Assignee: Mandar Ambawane >Priority: Minor > Attachments: Screenshot 2021-01-20 at 12.19.22 AM.png, Screenshot > 2021-01-20 at 12.21.50 AM.png, Screenshot 2021-01-20 at 12.22.01 AM.png > > > Table hbase_table_endlu has 2 column families, col_fam_kpgfu_2 is ACTIVE > whereas col_fam_kpgfu_1 is DELETED. > On clicking the entities, it can be seen that for col_fam_kpgfu_2 which is > ACTIVE, the table info is set to hbase_table_endlu > whereas for col_fam_kpgfu_1 which is DELETED, it is set to N/A (UI displays > null values as N/A) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4150) UI : __AtlasAuditEntry appearing in metrics window
[ https://issues.apache.org/jira/browse/ATLAS-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4150: -- Assignee: Mandar Ambawane > UI : __AtlasAuditEntry appearing in metrics window > -- > > Key: ATLAS-4150 > URL: https://issues.apache.org/jira/browse/ATLAS-4150 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Mandar Ambawane >Priority: Minor > Attachments: Screenshot from 2021-02-09 10-38-46.png > > > !Screenshot from 2021-02-09 10-38-46.png|width=584,height=432! > As seen in the above screenshot, entries for AtlasAuditEntry are visible. > That is an system internal entity and should ideally not be visible in the > metrics UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4039) Audit entry for export operation displays param information which is incorrect
[
https://issues.apache.org/jira/browse/ATLAS-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-4039:
--
Assignee: Prasad P. Pawar (was: Mandar Ambawane)
> Audit entry for export operation displays param information which is incorrect
> --
>
> Key: ATLAS-4039
> URL: https://issues.apache.org/jira/browse/ATLAS-4039
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments: Screenshot 2020-11-18 at 6.21.04 PM.png,
> image-2020-11-18-18-35-32-867.png
>
>
> On expanding the audit report of EXPORT operation *params(1)* is being
> displayed for all the exports irrespective of no/many options used in the
> exporting
> This is a UI issue and the response via rest call works fine.
> !image-2020-11-18-18-35-32-867.png|width=756,height=216!
> Sample payload that can be used to test
> {code}
> |{
> "itemsToExport": [
> \{ "typeName": "hive_db", "uniqueAttributes": { "qualifiedName":
> "" } },
> \{ "typeName": "hdfs_path", "uniqueAttributes": { "qualifiedName":
> "" } }
> ]
> }|
> |{
> "itemsToExport": [
> \{ "typeName": "hive_db", "uniqueAttributes": { "qualifiedName":
> "" } },
> \{ "typeName": "hdfs_path", "uniqueAttributes": { "qualifiedName":
> "" } }
> ],
> "options": {
> "fetchType": "FULL",
> "matchType": "startsWith"
> }
> }|
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4196) [Atlas: Audits] Audits are created for the (n-1) th operation in atlas while performing an insert operation
[ https://issues.apache.org/jira/browse/ATLAS-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4196. Resolution: Resolved > [Atlas: Audits] Audits are created for the (n-1) th operation in atlas while > performing an insert operation > --- > > Key: ATLAS-4196 > URL: https://issues.apache.org/jira/browse/ATLAS-4196 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > Attachments: Screenshot 2021-03-12 at 11.26.45 AM.png, Screenshot > 2021-03-12 at 11.27.04 AM.png > > > While inserting data into table, an audit entry is created but it displays > info of the n-1 th operation. > Eg: When the first insert operation is performed with 3 rows of data, the > audit entry shows 0 rows . > Now insert 2 more rows in 1 go, the audit data displays 3 rows instead of 5 > Latest audit and latest data in the tabled are shared > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4220) [Atlas: Audits] When business metadata attribute from different business metadata is added multiple audits are created
[
https://issues.apache.org/jira/browse/ATLAS-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-4220.
Resolution: Not A Bug
> [Atlas: Audits] When business metadata attribute from different business
> metadata is added multiple audits are created
> --
>
> Key: ATLAS-4220
> URL: https://issues.apache.org/jira/browse/ATLAS-4220
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
> Attachments: Screenshot 2021-03-20 at 4.35.39 PM.png, Screenshot
> 2021-03-20 at 4.52.56 PM.png
>
>
> Scenario:
> {code:java}
> Add multiple business metadata attribute to an entity
> {code}
> Add 2 attributes of 2 different business metadata
> !Screenshot 2021-03-20 at 4.52.56 PM.png|width=606,height=222!
> Sample Custom attribute update: Only one audit is created in case of custom
> defined attributes.
> !Screenshot 2021-03-20 at 4.35.39 PM.png|width=829,height=474!
> *Current output:*
> {code:java}
> {
> "entityId": "269582c2-9b05-4abf-9abb-71f587c465e0",
> "timestamp": 1616239355837,
> "user": "hrt_qa",
> "action": "BUSINESS_ATTRIBUTE_UPDATE",
> "details": "Updated business attributes:
> {\"typeName\":\"bm_dharsh_type\",\"attributes\":{\"attrib_1\":\"bbb\"}}",
> "eventKey":
> "269582c2-9b05-4abf-9abb-71f587c465e0:1616239355837:1:1616239355872",
> "entity": None,
> "type": None
> },
> {
> "entityId": "269582c2-9b05-4abf-9abb-71f587c465e0",
> "timestamp": 1616239355837,
> "user": "hrt_qa",
> "action": "BUSINESS_ATTRIBUTE_UPDATE",
> "details": "Updated business attributes:
> {\"typeName\":\"bm_dharsh_2\",\"attributes\":{\"attr_1\":\"aaa\"}}",
> "eventKey":
> "269582c2-9b05-4abf-9abb-71f587c465e0:1616239355837:0:1616239355872",
> "entity": None,
> "type": None
> } {code}
> *Expectation:*
> Only one audit entry has to be created when business metadata attributes are
> updated, even when they belong to different metadata. Expecting an update
> similar to the above shown used defined attribute update
> {code:java}
> {
> "entityId": "269582c2-9b05-4abf-9abb-71f587c465e0",
> "timestamp": 1616239355837,
> "user": "hrt_qa",
> "action": "BUSINESS_ATTRIBUTE_UPDATE",
> "details": "Updated business attributes:
> [{\"typeName\":\"bm_dharsh_type\",\"attributes\":{\"attrib_1\":\"bbb\"}},{\"typeName\":\"bm_dharsh_2\",\"attributes\":{\"attr_1\":\"aaa\"}}]",
> "eventKey":
> "269582c2-9b05-4abf-9abb-71f587c465e0:1616239355837:1:1616239355872",
> "entity": None,
> "type": None
> }{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4210) [Atlas: Audits] All data are being populated for event "Entity Created by import" when differential audit is enabled
[ https://issues.apache.org/jira/browse/ATLAS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4210. Resolution: Not A Bug > [Atlas: Audits] All data are being populated for event "Entity Created by > import" when differential audit is enabled > > > Key: ATLAS-4210 > URL: https://issues.apache.org/jira/browse/ATLAS-4210 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Priority: Major > Attachments: Screenshot 2021-03-16 at 7.03.46 PM.png > > > To enable differential audit "atlas.entity.audit.differential=true" has to be > set. Once enabled, for event "Entity Created by import" all the data are > being populated in audit entry instead of the differential change. > *Steps to reproduce:* > # Create a table in hive > # Export the table > # Delete the table in hive > # Import the table > !Screenshot 2021-03-16 at 7.03.46 PM.png|width=526,height=318! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4200) [Atlas: Audits] Relationship property is missing in the differential audit when the column name or column type is updated
[ https://issues.apache.org/jira/browse/ATLAS-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4200. Resolution: Not A Bug > [Atlas: Audits] Relationship property is missing in the differential audit > when the column name or column type is updated > - > > Key: ATLAS-4200 > URL: https://issues.apache.org/jira/browse/ATLAS-4200 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > Attachments: Screenshot 2021-03-12 at 4.04.01 PM.png, Screenshot > 2021-03-12 at 4.10.33 PM.png > > > When a column name or column type is updated, audit is created. When > differential audit is enabled only the modified part is updated in audit > *atlas.entity.audit.differential=true* > In this case the relationship property of the change is missing in the audit > Added screenshots of the same -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4235) [Atlas: Audits] When business metadata attribute or user defined attribute of an entity is updated, action is appearing as "Entity updated" in v1 api response
[
https://issues.apache.org/jira/browse/ATLAS-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-4235.
Resolution: Resolved
> [Atlas: Audits] When business metadata attribute or user defined attribute of
> an entity is updated, action is appearing as "Entity updated" in v1 api
> response
> --
>
> Key: ATLAS-4235
> URL: https://issues.apache.org/jira/browse/ATLAS-4235
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> Case 1:
> When business metadata attribute of an entity is updated, action is appearing
> as "Entity updated" in v1 api response
> {code:java}
> {u'action': u'ENTITY_UPDATE',
> u'details': u'Updated business attributes:
> {"typeName":"eibqk_bm","attributes":{"attrib_1":"111kezor","attrib_2":"222kezor"}}',
> u'entityId': u'29068c0c-8573-4cf2-bddc-ddefd4d38281',
> u'eventKey':
> u'29068c0c-8573-4cf2-bddc-ddefd4d38281:1617296650400:0:1617296650414',
> u'timestamp': 1617296650400,
> u'user': u'hrt_qa'} {code}
> As seen in the response, the *details* displays the right data "*Updated
> business attributes*" but *action* displays "*ENTITY_UPDATE*"
> Case 2:
> When user-defined attribute of an entity is updated, action is appearing as
> "Entity updated" in v1 api response
> {code:java}
> {u'action': u'ENTITY_UPDATE',
> u'details': u'Updated custom attribute:
> {"typeName":"entity_type_jmgur","guid":"a5770082-21b5-48ad-9540-0b2b7073359d","isIncomplete":false,"provenanceType":0,"version":0,"customAttributes":{"obtsv":"test
> value 2","mjfid":"test value 3","qlomc":"test value 1"},"proxy":false}',
> u'entityId': u'a5770082-21b5-48ad-9540-0b2b7073359d',
> u'eventKey':
> u'a5770082-21b5-48ad-9540-0b2b7073359d:1617297493442:0:1617297493450',
> u'timestamp': 1617297493442,
> u'user': u'hrt_qa'} {code}
> As seen in the response, the *details* displays the right data "*Updated
> custom attribute*" but *action* displays "*ENTITY_UPDATE*"
> *Minor:*
> Also it will be better if
> *"Updated custom attribute"* is updated as **
> *"**Updated custom attributes"* **
> Please not the 's' at the end to keep it consistent
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4222) [Atlas: Audits] When custom attributes are updated for an entity, additional information is present in the audits
[
https://issues.apache.org/jira/browse/ATLAS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-4222.
Resolution: Resolved
> [Atlas: Audits] When custom attributes are updated for an entity, additional
> information is present in the audits
> -
>
> Key: ATLAS-4222
> URL: https://issues.apache.org/jira/browse/ATLAS-4222
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
> Attachments: Screenshot 2021-03-22 at 11.10.54 PM.png
>
>
> *Scenario:*
> * Add user defined properties to an entity
> * Update user defined properties to an entity
> * Remove user defined properties from an entity
> Expectation:
> 1 audit entry with what is the update/action
>
> Additional information like current entity type_name, guid, and other
> information are present
> *Audit for: Add user-defined property :*
> {code:java}
> {
> "entityId": "269582c2-9b05-4abf-9abb-71f587c465e0",
> "timestamp": 1616237977768,
> "user": "hrt_qa",
> "action": "CUSTOM_ATTRIBUTE_UPDATE",
> "details": "Updated custom attribute:
> {\"typeName\":\"hbase_table\",\"guid\":\"269582c2-9b05-4abf-9abb-71f587c465e0\",\"isIncomplete\":false,\"provenanceType\":0,\"version\":0,\"customAttributes\":{\"a\":\"1\",\"b\":\"2\",\"c\":\"3\"},\"proxy\":false}",
> "eventKey":
> "269582c2-9b05-4abf-9abb-71f587c465e0:1616237977768:0:1616237977821",
> "entity": None,
> "type": None
> }{code}
> Only the *customAttributes* has to be updated
> *Audit for: Update user-defined property :*
> {code:java}
> {
> "entityId": "269582c2-9b05-4abf-9abb-71f587c465e0",
> "timestamp": 1616238083948,
> "user": "hrt_qa",
> "action": "CUSTOM_ATTRIBUTE_UPDATE",
> "details": "Updated custom attribute:
> {\"typeName\":\"hbase_table\",\"guid\":\"269582c2-9b05-4abf-9abb-71f587c465e0\",\"isIncomplete\":false,\"provenanceType\":0,\"version\":0,\"customAttributes\":{\"a\":\"2\",\"b\":\"2\",\"d\":\"5\"},\"proxy\":false}",
> "eventKey":
> "269582c2-9b05-4abf-9abb-71f587c465e0:1616238083948:0:1616238083988",
> "entity": None,
> "type": None
> }{code}
> *Audit for: remove user-defined property :***
> {code:java}
> {
> "entityId": "269582c2-9b05-4abf-9abb-71f587c465e0",
> "timestamp": 1616238309523,
> "user": "hrt_qa",
> "action": "CUSTOM_ATTRIBUTE_UPDATE",
> "details": "Updated custom attribute:
> {\"typeName\":\"hbase_table\",\"guid\":\"269582c2-9b05-4abf-9abb-71f587c465e0\",\"isIncomplete\":false,\"provenanceType\":0,\"version\":0,\"customAttributes\":{},\"proxy\":false}",
> "eventKey":
> "269582c2-9b05-4abf-9abb-71f587c465e0:1616238309523:0:1616238309558",
> "entity": None,
> "type": None
> } {code}
> UI operation screen shot is added for reference:
> !Screenshot 2021-03-22 at 11.10.54 PM.png|width=917,height=478!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4165) [Atlas: Spooling] There is no create audit for a table that is spooled but instead creates several update audits for a create operation
[ https://issues.apache.org/jira/browse/ATLAS-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4165. Resolution: Resolved > [Atlas: Spooling] There is no create audit for a table that is spooled but > instead creates several update audits for a create operation > --- > > Key: ATLAS-4165 > URL: https://issues.apache.org/jira/browse/ATLAS-4165 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Ashutosh Mestry >Priority: Major > Attachments: Screenshot 2021-02-18 at 4.20.15 PM.png, Screenshot > 2021-02-18 at 4.59.45 PM.png, Screenshot 2021-02-18 at 5.00.13 PM.png > > > When a table is spooled and created in atlas, it has no create audit entry. > Steps to repro: > # Bring Kafka down > # Create a table > # Wait for it to spool > # Start the kafka brokers > # Wait for the table to be created in atlas > Now check the audit tab of that entity > !Screenshot 2021-02-18 at 4.20.15 PM.png|width=679,height=277! > NOTE: > It creates several update audit entries for just 1 create operation > This is observed for the *very first table* that is created via *Impala* > *!Screenshot 2021-02-18 at 4.59.45 PM.png|width=431,height=175!* > !Screenshot 2021-02-18 at 5.00.13 PM.png|width=369,height=100! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4198) [Atlas: Audits][Regression] No audits should be created while inserting data into table
[
https://issues.apache.org/jira/browse/ATLAS-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-4198.
Resolution: Resolved
> [Atlas: Audits][Regression] No audits should be created while inserting data
> into table
> ---
>
> Key: ATLAS-4198
> URL: https://issues.apache.org/jira/browse/ATLAS-4198
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 12.42.50 PM.png
>
>
> As per ATLAS-3198, no audit entry should be created for insert operation. In
> the latest code we are able to see audit entries for insert operation
> Steps to repro:
> # Create a table
> # Insert data into table
> *Create table:*
> {code:java}
> CREATE TABLE IF NOT EXISTS dharsh_test_1 ( eid int, name String, salary
> String, designation String);{code}
> *Insert data into table:*
> {code:java}
> insert into dharsh_test_1 (eid, name, salary, designation) values
> (1001, "Gopal", "45000", "Technical manager"),
> (1002, "Manish", "45000", "Proof reader"),
> (1003, "Masthanvali" , "4", "Technical writer"); {code}
> The above insert operation should not create any audit entry according to
> ATLAS-3198,, but it now creates
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4237) [Atlas: Audits] When user defined attributes are updated, all the attributes are appearing in the update audit
[
https://issues.apache.org/jira/browse/ATLAS-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-4237.
Resolution: Resolved
> [Atlas: Audits] When user defined attributes are updated, all the attributes
> are appearing in the update audit
> --
>
> Key: ATLAS-4237
> URL: https://issues.apache.org/jira/browse/ATLAS-4237
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
>
> Add a few user-defined attributes to an entity
> Now add 1 more attribute
> Expectation is that only the newly added attribute should appear, but all the
> attributes are present in the update audit
> Here is an example of n-1 and nth audit update
> {code:java}
> {
> "entityId": "aa9134fa-96f0-4b8e-80b7-d8d8c4fb0232",
> "timestamp": 1617372357199,
> "user": "hrt_qa",
> "action": "CUSTOM_ATTRIBUTE_UPDATE",
> "details": "Updated custom attribute:
> {\"typeName\":\"entity_type_rvlum\",\"guid\":\"aa9134fa-96f0-4b8e-80b7-d8d8c4fb0232\",\"isIncomplete\":false,\"provenanceType\":0,\"version\":0,\"customAttributes\":{\"jej\":\"\",\"efef\":\"fefsef\",\"ggg\":\"huhu\"},\"proxy\":false}",
> "eventKey":
> "aa9134fa-96f0-4b8e-80b7-d8d8c4fb0232:1617372357199:0:1617372357214",
> "entity": null,
> "type": null
> },
> {
> "entityId": "aa9134fa-96f0-4b8e-80b7-d8d8c4fb0232",
> "timestamp": 1617372250220,
> "user": "hrt_qa",
> "action": "CUSTOM_ATTRIBUTE_UPDATE",
> "details": "Updated custom attribute:
> {\"typeName\":\"entity_type_rvlum\",\"guid\":\"aa9134fa-96f0-4b8e-80b7-d8d8c4fb0232\",\"isIncomplete\":false,\"provenanceType\":0,\"version\":0,\"customAttributes\":{\"jej\":\"\",\"efef\":\"fefsef\"},\"proxy\":false}",
> "eventKey":
> "aa9134fa-96f0-4b8e-80b7-d8d8c4fb0232:1617372250220:0:1617372250250",
> "entity": null,
> "type": null
> }{code}
> n-1 custom attribute :
> "customAttributes\":\{\"jej\":\"\",\"efef\":\"fefsef\"}
> n th custom attribute :
> "customAttributes\":\{\"jej\":\"\",\"efef\":\"fefsef\",\"ggg\":\"huhu\"}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4216) [Atlas: Audits] When an entity is imported with classification, multiple audits are created
[
https://issues.apache.org/jira/browse/ATLAS-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-4216.
Resolution: Resolved
> [Atlas: Audits] When an entity is imported with classification, multiple
> audits are created
> ---
>
> Key: ATLAS-4216
> URL: https://issues.apache.org/jira/browse/ATLAS-4216
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
> Attachments: Screenshot 2021-03-19 at 12.08.41 PM.png, Screenshot
> 2021-03-19 at 12.10.34 PM.png, Screenshot 2021-03-19 at 12.10.45 PM.png
>
>
> *Scenario:*
> In Cluster1:
> {code:java}
> Create a tag
> Create an entity and associate the tag to an entity
> Export the entity {code}
> *In Cluster2:*
> {code:java}
> Import the exported entity {code}
> In Cluster1:
> {code:java}
> Update the classification by adding an attrib
> Update the attrib value in entity
> Update the entity
> Export the entity{code}
> *In Cluster2:*
> {code:java}
> Import the entity {code}
> In Cluster1:
> {code:java}
> Delete the entity
> Export the entity{code}
> *In Cluster2:*
> {code:java}
> Import the entity {code}
> Observation:
> *Multiple* audits are created for an import operation
> !Screenshot 2021-03-19 at 12.08.41 PM.png|width=1485,height=105!
> This is observed when the imported entity is updated or deleted as well
> Update:
> !Screenshot 2021-03-19 at 12.10.34 PM.png|width=1598,height=151!
> Delete:
> !Screenshot 2021-03-19 at 12.10.45 PM.png|width=1375,height=161!
> For every operation information related to classification are appearing as a
> new update.
> And the update comes as deleted and added classification instead of
> classification updated
> 1) For am imported entity, if the entity is updated should it display the
> classification related information in a new audit
> 2) If at all a new audit is still ok should we display it as tag deleted and
> tag added instead of tag updated.
> IMHO, the tag information should be a part of the imported entity update
> information itself
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4199) [Atlas: Audits] 3 audit entries are created when a tables is created using ctas
[
https://issues.apache.org/jira/browse/ATLAS-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-4199.
Resolution: Resolved
> [Atlas: Audits] 3 audit entries are created when a tables is created using
> ctas
> ---
>
> Key: ATLAS-4199
> URL: https://issues.apache.org/jira/browse/ATLAS-4199
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 3.27.19 PM.png, Screenshot
> 2021-03-12 at 3.34.25 PM.png
>
>
> *Steps to repro:*
> # Create a table;
> # Create a new table using ctas;
> {code:java}
> create table random_table;
> create table ctas_table as select * from random_table;{code}
>
> *Expectation:*
> 1 audit entry for the creation of the new table and 1 audit for the
> relationship with the old table
> *Current observation:*
> * 3 audits are generated
> * 1 audit as test user (hrt_qa)
> * 2 audits as hive user
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4197) [Atlas: Audits] [Regression] 2 entries are created while creating a new database in atlas audits
[
https://issues.apache.org/jira/browse/ATLAS-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-4197.
Resolution: Not A Bug
> [Atlas: Audits] [Regression] 2 entries are created while creating a new
> database in atlas audits
>
>
> Key: ATLAS-4197
> URL: https://issues.apache.org/jira/browse/ATLAS-4197
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 11.43.19 AM.png
>
>
> Steps to repro:
> {code:java}
> create database db_1;{code}
> Expecting 1 entry but 2 entries are created for the same
> 1 create audit as *hive* user and 1 update audit audit as *hrt_qa* user
> Looks like a possible regression of ATLAS-3360
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4343) [Entity Audits] 'Propagated Classification Added' Timestamp is < 'Entity Created' Timestamp
[ https://issues.apache.org/jira/browse/ATLAS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4343: -- Assignee: Mandar Ambawane > [Entity Audits] 'Propagated Classification Added' Timestamp is < 'Entity > Created' Timestamp > --- > > Key: ATLAS-4343 > URL: https://issues.apache.org/jira/browse/ATLAS-4343 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Umesh Padashetty >Assignee: Mandar Ambawane >Priority: Major > > The 'Propagated Classification Added' Timestamp is < 'Entity Created' > Timestamp. This is invalid since the classificiation is propagated once the > entity is created > For instance > # Created an external table with ozone path location > # This creates ozone_key and hive_table entity > # Entity Created TImestamp is shown correctly for both the entities > # Applied a tag to ozone_key with propagate classification set to true > # Classification propagates to hive_table entity, but the Timestamp shown is > in past > # For ozone_key: > ## Entity created: 06/24/2021 08:44:33 PM (IST) > ## Classification added: 06/24/2021 08:44:51 PM (IST) > # Whereas hive_table: > ## Entity created: 06/24/2021 08:44:33 PM (IST) > ## Propagated Classification Added: 06/24/2021 *08:37:06 PM* (IST) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3411) Relationships : Having multiple relationships on the same attribute
[ https://issues.apache.org/jira/browse/ATLAS-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-3411: --- Description: 1.Created 2 association relationships between 2 types using the same attribute "rel_attribute". 2.Created entities with the first relationship . Relationship is created successfully. 3. In the entitydef of entity1 , "rel_attribute" is not found in both relatedAttributes / attributes. But in entitydef of entity2 "rel_attribute" is found which contains entity1 information. This happens only when multiple relations are created on the same attribute. Repro steps : 1. Create types by posting multi_entity_types.json (to create entity types) and multi_relationships.json (to create relationship typedefs) to v2/types/typedefs 2. Create entities by POSTing multi_entities.json to /v2/entity/bulk 3.Create relationship between the entities by POSTing the multi_relationship_instance.json to /v2/relationship (entity guids to be modified) In entity1's entitydef, it can be seen that "rel_attirbute" is not present at all though the relationship guid is defined between entity1 and entity2. was: 1.Created 2 association relationships between 2 types using the same attribute "rel_attribute". 2.Created entities with the first relationship . Relationship is created successfully. 3. In the entitydef of entity1 , "rel_attribute" is not found in both relatedAttributes / attributes. But in entitydef of entity2 "rel_attribute" is found which contains entity1 information. This happens only when multiple relations are created on the same attribute. Repro steps (Attached the payloads) : 1. Create types by posting multi_entity_types.json (to create entity types) and multi_relationships.json (to create relationship typedefs) to v2/types/typedefs 2. Create entities by POSTing multi_entities.json to /v2/entity/bulk 3.Create relationship between the entities by POSTing the multi_relationship_instance.json to /v2/relationship (entity guids to be modified) In entity1's entitydef, it can be seen that "rel_attirbute" is not present at all though the relationship guid is defined between entity1 and entity2. > Relationships : Having multiple relationships on the same attribute > --- > > Key: ATLAS-3411 > URL: https://issues.apache.org/jira/browse/ATLAS-3411 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > 1.Created 2 association relationships between 2 types using the same > attribute "rel_attribute". > 2.Created entities with the first relationship . Relationship is created > successfully. > 3. In the entitydef of entity1 , "rel_attribute" is not found in both > relatedAttributes / attributes. But in entitydef of entity2 "rel_attribute" > is found which contains entity1 information. > This happens only when multiple relations are created on the same attribute. > Repro steps : > 1. Create types by posting multi_entity_types.json (to create entity types) > and multi_relationships.json (to create relationship typedefs) to > v2/types/typedefs > 2. Create entities by POSTing multi_entities.json to /v2/entity/bulk > 3.Create relationship between the entities by POSTing the > multi_relationship_instance.json to /v2/relationship (entity guids to be > modified) > In entity1's entitydef, it can be seen that "rel_attirbute" is not present at > all though the relationship guid is defined between entity1 and entity2. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4203) [Business Metadata] Issue with saving floating point numbers in case of attributes of 'float' type
[ https://issues.apache.org/jira/browse/ATLAS-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4203. Assignee: Mandar Ambawane Resolution: Won't Fix > [Business Metadata] Issue with saving floating point numbers in case of > attributes of 'float' type > --- > > Key: ATLAS-4203 > URL: https://issues.apache.org/jira/browse/ATLAS-4203 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Umesh Padashetty >Assignee: Mandar Ambawane >Priority: Major > Attachments: After save.png, Before save.png > > > A value entered as -234567890123456.12 gets saved as -23456789400 > A value entered as 234567890123456.12 gets saved as 23456789400 > Screenshots attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4203) [Business Metadata] Issue with saving floating point numbers in case of attributes of 'float' type
[ https://issues.apache.org/jira/browse/ATLAS-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364271#comment-17364271 ] Mandar Ambawane commented on ATLAS-4203: Hi [~umesh.padashetty] This behavior is not specific to Business Metadata attributes. This can be seen in all over the application where Floating point Data type is used. As Floating point numbers have a limited number of digits, they cannot represent all real numbers accurately. When there are more digits than the format allows, the number is rounded. > [Business Metadata] Issue with saving floating point numbers in case of > attributes of 'float' type > --- > > Key: ATLAS-4203 > URL: https://issues.apache.org/jira/browse/ATLAS-4203 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Umesh Padashetty >Priority: Major > Attachments: After save.png, Before save.png > > > A value entered as -234567890123456.12 gets saved as -23456789400 > A value entered as 234567890123456.12 gets saved as 23456789400 > Screenshots attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4336) Restrict attributes of type to be created starting with double underscore
[ https://issues.apache.org/jira/browse/ATLAS-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4336: -- Assignee: Mandar Ambawane > Restrict attributes of type to be created starting with double underscore > - > > Key: ATLAS-4336 > URL: https://issues.apache.org/jira/browse/ATLAS-4336 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha S >Assignee: Mandar Ambawane >Priority: Major > > Currently type can be updated with an attribute whose name starts with "__" > like __guid. > This gets mixed up with system attributes. > Hence attribute names should not be allowed to be started with double > underscore or following attribute names (system attribute names) should be > restricted when a type is created or updated : > __classificationNames > __modifiedBy > __createdBy > __state > __typeName > __modificationTimestamp > __propagatedClassificationNames > __customAttributes > __isIncomplete > __guid > __timestamp > __labels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4038) Client ID field in the Admin audit result captures the Server/Host IP instead of the Client IP
[ https://issues.apache.org/jira/browse/ATLAS-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4038. Resolution: Fixed > Client ID field in the Admin audit result captures the Server/Host IP instead > of the Client IP > -- > > Key: ATLAS-4038 > URL: https://issues.apache.org/jira/browse/ATLAS-4038 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > > The Client ID field is supposed to capture the Client address from which the > request is made, but it captures the server address on which this request > lands instead. > This incorrect behaviour is observed in all the operations audits except > SERVER_START and SERVER_STATE_ACTIVE -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4301) Handle Test Case Failure on Pre-commit environment
[
https://issues.apache.org/jira/browse/ATLAS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4301:
---
Description:
Getting following error on Pre-commit build due to change in the file path
hive-bridge/target/logs/application.log
{code:java}
Wrong FS:
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
expected: file:///
{code}
Also,
There is Enum "Type" in the "Entity"
{code:java}
Class: org.apache.hadoop.hive.ql.hooks.Entity
Enum: Type{code}
Enum "Type" has one constant "LOCAL_DIR"
Due to recent changes, we need to provide support for this constant "LOCAL_DIR"
in Testing Environment.
Without which following issues occuring on Testing Environment:
# While creating "hive_process" entity, The "outputs" attribute is not getting
set (Which is of type "hdfs_path").
# While setting the "qualifiedName" of "hive_process" entity, File path is not
getting appended.
This causing Failure of some Test cases.
was:
Getting following error on Pre-commit build due to change in the file path
hive-bridge/target/logs/application.log
{code:java}
Wrong FS:
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
expected: file:///
{code}
> Handle Test Case Failure on Pre-commit environment
> --
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> hive-bridge/target/logs/application.log
> {code:java}
> Wrong FS:
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
> expected: file:///
> {code}
>
> Also,
> There is Enum "Type" in the "Entity"
> {code:java}
> Class: org.apache.hadoop.hive.ql.hooks.Entity
> Enum: Type{code}
> Enum "Type" has one constant "LOCAL_DIR"
> Due to recent changes, we need to provide support for this constant
> "LOCAL_DIR" in Testing Environment.
> Without which following issues occuring on Testing Environment:
> # While creating "hive_process" entity, The "outputs" attribute is not
> getting set (Which is of type "hdfs_path").
> # While setting the "qualifiedName" of "hive_process" entity, File path is
> not getting appended.
> This causing Failure of some Test cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4290) [Atlas: Glossary Term Bulk Import] There is not much info available in logs importing terms in bulk
[ https://issues.apache.org/jira/browse/ATLAS-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4290: -- Assignee: Mandar Ambawane > [Atlas: Glossary Term Bulk Import] There is not much info available in logs > importing terms in bulk > --- > > Key: ATLAS-4290 > URL: https://issues.apache.org/jira/browse/ATLAS-4290 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > > While creating a term there is a statement "GraphTransaction intercept for > org.apache.atlas.glossary.GlossaryService.createTerm" in logs, but while > performing bulk import, there are no information logs available. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4301) Handle Test Case Failure on Pre-commit environment
[
https://issues.apache.org/jira/browse/ATLAS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4301:
---
Summary: Handle Test Case Failure on Pre-commit environment (was: Resolve
Test Case Failure on Pre-commit environment)
> Handle Test Case Failure on Pre-commit environment
> --
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> hive-bridge/target/logs/application.log
> {code:java}
> Wrong FS:
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
> expected: file:///
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment
[
https://issues.apache.org/jira/browse/ATLAS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4301:
---
Description:
Getting following error on Pre-commit build due to change in the file path
hive-bridge/target/logs/application.log
{code:java}
Wrong FS:
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
expected: file:///
{code}
was:
Getting following error on Pre-commit build due to change in the file path
+
hive-bridge/target/logs/application.log
+
{code:java}
Wrong FS:
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
expected: file:///
{code}
> Resolve Test Case Failure on Pre-commit environment
> ---
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> hive-bridge/target/logs/application.log
> {code:java}
> Wrong FS:
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
> expected: file:///
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment
[
https://issues.apache.org/jira/browse/ATLAS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4301:
---
Description:
Getting following error on Pre-commit build due to change in the file path
+
hive-bridge/target/logs/application.log
+
{code:java}
Wrong FS:
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
expected: file:///
{code}
was:
Getting following error on Pre-commit build due to change in the file path
[hive-bridge/target/logs/application.log|https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/562/artifact/addons/hive-bridge/target/logs/application.log]
{code:java}
Wrong FS:
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
expected: file:///
{code}
> Resolve Test Case Failure on Pre-commit environment
> ---
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> +
> hive-bridge/target/logs/application.log
> +
> {code:java}
> Wrong FS:
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
> expected: file:///
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment
[
https://issues.apache.org/jira/browse/ATLAS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4301:
---
Description:
Getting following error on Pre-commit build due to change in the file path
[hive-bridge/target/logs/application.log|https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/562/artifact/addons/hive-bridge/target/logs/application.log]
{code:java}
Wrong FS:
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
expected: file:///
{code}
was:
Getting following error on Pre-commit build due to change in the file path
{code:java}
Wrong FS:
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
expected: file:///
{code}
> Resolve Test Case Failure on Pre-commit environment
> ---
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> [hive-bridge/target/logs/application.log|https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/562/artifact/addons/hive-bridge/target/logs/application.log]
> {code:java}
> Wrong FS:
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
> expected: file:///
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment
Mandar Ambawane created ATLAS-4301: -- Summary: Resolve Test Case Failure on Pre-commit environment Key: ATLAS-4301 URL: https://issues.apache.org/jira/browse/ATLAS-4301 Project: Atlas Issue Type: Improvement Reporter: Mandar Ambawane Assignee: Mandar Ambawane -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment
[
https://issues.apache.org/jira/browse/ATLAS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane updated ATLAS-4301:
---
Description:
Getting following error on Pre-commit build due to change in the file path
{code:java}
Wrong FS:
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
expected: file:///
{code}
> Resolve Test Case Failure on Pre-commit environment
> ---
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> {code:java}
> Wrong FS:
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
> expected: file:///
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4040) Remove the result count field or update to N/A for TYPE_DEF_DELETE audit entry
[ https://issues.apache.org/jira/browse/ATLAS-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4040. Resolution: Not A Bug > Remove the result count field or update to N/A for TYPE_DEF_DELETE audit entry > -- > > Key: ATLAS-4040 > URL: https://issues.apache.org/jira/browse/ATLAS-4040 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > > Delete call will always have result count as 1 > It will be good to remove the Result count field for this operation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3763) Add "serviceType" in AtlasEntityHeader
[ https://issues.apache.org/jira/browse/ATLAS-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-3763. Resolution: Invalid > Add "serviceType" in AtlasEntityHeader > -- > > Key: ATLAS-3763 > URL: https://issues.apache.org/jira/browse/ATLAS-3763 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3619) Allow to create a namespace typedef without specifying any "applicableEntityTypes"
[ https://issues.apache.org/jira/browse/ATLAS-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-3619. Resolution: Fixed > Allow to create a namespace typedef without specifying any > "applicableEntityTypes" > -- > > Key: ATLAS-3619 > URL: https://issues.apache.org/jira/browse/ATLAS-3619 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4235) [Atlas: Audits] When business metadata attribute or user defined attribute of an entity is updated, action is appearing as "Entity updated" in v1 api response
[
https://issues.apache.org/jira/browse/ATLAS-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-4235:
--
Assignee: Mandar Ambawane
> [Atlas: Audits] When business metadata attribute or user defined attribute of
> an entity is updated, action is appearing as "Entity updated" in v1 api
> response
> --
>
> Key: ATLAS-4235
> URL: https://issues.apache.org/jira/browse/ATLAS-4235
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> Case 1:
> When business metadata attribute of an entity is updated, action is appearing
> as "Entity updated" in v1 api response
> {code:java}
> {u'action': u'ENTITY_UPDATE',
> u'details': u'Updated business attributes:
> {"typeName":"eibqk_bm","attributes":{"attrib_1":"111kezor","attrib_2":"222kezor"}}',
> u'entityId': u'29068c0c-8573-4cf2-bddc-ddefd4d38281',
> u'eventKey':
> u'29068c0c-8573-4cf2-bddc-ddefd4d38281:1617296650400:0:1617296650414',
> u'timestamp': 1617296650400,
> u'user': u'hrt_qa'} {code}
> As seen in the response, the *details* displays the right data "*Updated
> business attributes*" but *action* displays "*ENTITY_UPDATE*"
> Case 2:
> When user-defined attribute of an entity is updated, action is appearing as
> "Entity updated" in v1 api response
> {code:java}
> {u'action': u'ENTITY_UPDATE',
> u'details': u'Updated custom attribute:
> {"typeName":"entity_type_jmgur","guid":"a5770082-21b5-48ad-9540-0b2b7073359d","isIncomplete":false,"provenanceType":0,"version":0,"customAttributes":{"obtsv":"test
> value 2","mjfid":"test value 3","qlomc":"test value 1"},"proxy":false}',
> u'entityId': u'a5770082-21b5-48ad-9540-0b2b7073359d',
> u'eventKey':
> u'a5770082-21b5-48ad-9540-0b2b7073359d:1617297493442:0:1617297493450',
> u'timestamp': 1617297493442,
> u'user': u'hrt_qa'} {code}
> As seen in the response, the *details* displays the right data "*Updated
> custom attribute*" but *action* displays "*ENTITY_UPDATE*"
> *Minor:*
> Also it will be better if
> *"Updated custom attribute"* is updated as **
> *"**Updated custom attributes"* **
> Please not the 's' at the end to keep it consistent
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4196) [Atlas: Audits] Audits are created for the (n-1) th operation in atlas while performing an insert operation
[ https://issues.apache.org/jira/browse/ATLAS-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4196: -- Assignee: Mandar Ambawane > [Atlas: Audits] Audits are created for the (n-1) th operation in atlas while > performing an insert operation > --- > > Key: ATLAS-4196 > URL: https://issues.apache.org/jira/browse/ATLAS-4196 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > Attachments: Screenshot 2021-03-12 at 11.26.45 AM.png, Screenshot > 2021-03-12 at 11.27.04 AM.png > > > While inserting data into table, an audit entry is created but it displays > info of the n-1 th operation. > Eg: When the first insert operation is performed with 3 rows of data, the > audit entry shows 0 rows . > Now insert 2 more rows in 1 go, the audit data displays 3 rows instead of 5 > Latest audit and latest data in the tabled are shared > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4195) [Atlas: Audits] 2 entries are created in audits when "replace columns" command is executed in hive
[
https://issues.apache.org/jira/browse/ATLAS-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-4195:
--
Assignee: Mandar Ambawane
> [Atlas: Audits] 2 entries are created in audits when "replace columns"
> command is executed in hive
> --
>
> Key: ATLAS-4195
> URL: https://issues.apache.org/jira/browse/ATLAS-4195
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 10.31.13 AM.png
>
>
> While performing an update operation "replace columns" 2 entries are created
> in atlas
> *Steps to repro:*
> {code:java}
> create table test_table_1(name string, eid int);
> alter table test_table_1 replace columns(ename string, eid int, dept string);
> {code}
> 1 entry is created a hive user and the other entry is created as test user
> !Screenshot 2021-03-12 at 10.31.13 AM.png|width=671,height=166!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4197) [Atlas: Audits] [Regression] 2 entries are created while creating a new database in atlas audits
[
https://issues.apache.org/jira/browse/ATLAS-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-4197:
--
Assignee: Mandar Ambawane
> [Atlas: Audits] [Regression] 2 entries are created while creating a new
> database in atlas audits
>
>
> Key: ATLAS-4197
> URL: https://issues.apache.org/jira/browse/ATLAS-4197
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 11.43.19 AM.png
>
>
> Steps to repro:
> {code:java}
> create database db_1;{code}
> Expecting 1 entry but 2 entries are created for the same
> 1 create audit as *hive* user and 1 update audit audit as *hrt_qa* user
> Looks like a possible regression of ATLAS-3360
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4199) [Atlas: Audits] 3 audit entries are created when a tables is created using ctas
[
https://issues.apache.org/jira/browse/ATLAS-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-4199:
--
Assignee: Mandar Ambawane
> [Atlas: Audits] 3 audit entries are created when a tables is created using
> ctas
> ---
>
> Key: ATLAS-4199
> URL: https://issues.apache.org/jira/browse/ATLAS-4199
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 3.27.19 PM.png, Screenshot
> 2021-03-12 at 3.34.25 PM.png
>
>
> *Steps to repro:*
> # Create a table;
> # Create a new table using ctas;
> {code:java}
> create table random_table;
> create table ctas_table as select * from random_table;{code}
>
> *Expectation:*
> 1 audit entry for the creation of the new table and 1 audit for the
> relationship with the old table
> *Current observation:*
> * 3 audits are generated
> * 1 audit as test user (hrt_qa)
> * 2 audits as hive user
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4200) [Atlas: Audits] Relationship property is missing in the differential audit when the column name or column type is updated
[ https://issues.apache.org/jira/browse/ATLAS-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4200: -- Assignee: Mandar Ambawane > [Atlas: Audits] Relationship property is missing in the differential audit > when the column name or column type is updated > - > > Key: ATLAS-4200 > URL: https://issues.apache.org/jira/browse/ATLAS-4200 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > Attachments: Screenshot 2021-03-12 at 4.04.01 PM.png, Screenshot > 2021-03-12 at 4.10.33 PM.png > > > When a column name or column type is updated, audit is created. When > differential audit is enabled only the modified part is updated in audit > *atlas.entity.audit.differential=true* > In this case the relationship property of the change is missing in the audit > Added screenshots of the same -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4198) [Atlas: Audits][Regression] No audits should be created while inserting data into table
[
https://issues.apache.org/jira/browse/ATLAS-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-4198:
--
Assignee: Mandar Ambawane
> [Atlas: Audits][Regression] No audits should be created while inserting data
> into table
> ---
>
> Key: ATLAS-4198
> URL: https://issues.apache.org/jira/browse/ATLAS-4198
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 12.42.50 PM.png
>
>
> As per ATLAS-3198, no audit entry should be created for insert operation. In
> the latest code we are able to see audit entries for insert operation
> Steps to repro:
> # Create a table
> # Insert data into table
> *Create table:*
> {code:java}
> CREATE TABLE IF NOT EXISTS dharsh_test_1 ( eid int, name String, salary
> String, designation String);{code}
> *Insert data into table:*
> {code:java}
> insert into dharsh_test_1 (eid, name, salary, designation) values
> (1001, "Gopal", "45000", "Technical manager"),
> (1002, "Manish", "45000", "Proof reader"),
> (1003, "Masthanvali" , "4", "Technical writer"); {code}
> The above insert operation should not create any audit entry according to
> ATLAS-3198,, but it now creates
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-3597) Incorrect error message when attempting to update Namespacedef
[
https://issues.apache.org/jira/browse/ATLAS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane resolved ATLAS-3597.
Resolution: Fixed
> Incorrect error message when attempting to update Namespacedef
> --
>
> Key: ATLAS-3597
> URL: https://issues.apache.org/jira/browse/ATLAS-3597
> Project: Atlas
> Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> # Create a new namespaceDef:
>
> {code:java}
> curl --location --request POST
> 'http://localhost:21000/api/atlas/v2/types/typedefs' \
> --header 'Content-Type: application/json' \
> --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
> --data-raw '{
> "namespaceDefs": [
> {
> "name": "namespace1",
> "description": "Sample namespace1",
> "serviceType": "NAMESPACES",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "namespaceAttr1",
> "typeName": "string",
> "options": {
> "applicableEntityTypes": "[\"hive_db\",
> \"hive_table\"]",
> "maxStrLength": "50"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> },
> {
> "name": "namespaceAttr2",
> "typeName": "int",
> "options": {
> "applicableEntityTypes": "[\"hive_db\",
> \"hive_column\"]"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> }
> ]
> }
> ]
> }'{code}
>
> 2. Update the namespaceDef to remove an entry from applicable entityTypes in
> 'namespaceAttr1':
>
> {code:java}
> curl --location --request PUT
> 'http://localhost:21000/api/atlas/v2/types/typedefs' \
> --header 'Content-Type: application/json' \
> --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
> --data-raw '{
> "namespaceDefs": [
> {
> "name": "namespace1",
> "description": "Sample namespace1",
> "serviceType": "NAMESPACES",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "namespaceAttr1",
> "typeName": "string",
> "options": {
> "applicableEntityTypes": "[\"hive_db\"]",
> "maxStrLength": "50"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> },
> {
> "name": "namespaceAttr2",
> "typeName": "int",
> "options": {
> "applicableEntityTypes": "[\"hive_db\",
> \"hive_column\"]"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> }
> ]
> }
> ]
> }'{code}
>
>
> The following error message is thrown:
>
> {code:java}
> { "errorCode": "ATLAS-400-00-095", "errorMessage": "Cannot remove
> applicableEntityTypes in Attribute Def: namespace1, defined in namespace:
> {2}" }{code}
> error message should be: "Updating '*applicableEntityTypes*' in namespace:
> \{namespace_name}, attribute: \{namespace_attribute} is not allowed."
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-3534) EntityREST changes to allow namespace attributes to be added to an entity instance
[ https://issues.apache.org/jira/browse/ATLAS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-3534. Resolution: Fixed > EntityREST changes to allow namespace attributes to be added to an entity > instance > -- > > Key: ATLAS-3534 > URL: https://issues.apache.org/jira/browse/ATLAS-3534 > Project: Atlas > Issue Type: New Feature >Reporter: Aadarsh Jajodia >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4139) [Atlas: Glossary Term Bulk Import] When AdditionalAttributes is not provided in key:value format, the error message does not convey that
[
https://issues.apache.org/jira/browse/ATLAS-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-4139:
--
Assignee: Mandar Ambawane
> [Atlas: Glossary Term Bulk Import] When AdditionalAttributes is not provided
> in key:value format, the error message does not convey that
>
>
> Key: ATLAS-4139
> URL: https://issues.apache.org/jira/browse/ATLAS-4139
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-02-05 at 4.07.46 PM.png
>
>
> Consider the following input for bulk import term_glossary
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1, "glossary_1 term_1 short description", "glossary_1 term_1
> long description", "Examples", "AB", "glossary_1 term_1 Usage", "random_key"
> {code}
> Here *AdditionalAttributes* is *random_key*
> When this is imported we get
> {code:java}
> errorCode: "ATLAS-500-00-001"errorMessage: "The uploaded file has not been
> processed due to the following errors : ↵[↵The Data in the uploaded file is
> incorrectly specified : random_key]" {code}
> It mentions The Data in the uploaded file is incorrectly specified :
> random_key
> It would be good to convey as "AdditionalAttributes has to a key:value pair"
> or something similar
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4146) [Atlas: Glossary] On updating the related terms, UI allows the user to add the already added term
[ https://issues.apache.org/jira/browse/ATLAS-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4146: --- Component/s: atlas-core > [Atlas: Glossary] On updating the related terms, UI allows the user to add > the already added term > - > > Key: ATLAS-4146 > URL: https://issues.apache.org/jira/browse/ATLAS-4146 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > Attachments: Screen Recording 2021-02-05 at 6.50.31 PM.mov > > > Steps to repro: > # Create a glossary(glossary_1) and a few terms (term_1, term_2, term_3, > term_4, term_5) > # Click on term_1 and add related terms "alsoSee" > # Choose term_5 of glossary_1 > # Provide inputs and assign > # term_5 will be added as a related term > # Now, add one more related term and choose the same term_5 of glossary_1 > [UI allows this] > # Provide new input and assign > # The assignment will be successful > This makes the user think, that term_5 with new data is saved. But that is > not the case, only old data is present > Expectation: > Do not allow the user to assign the same term again. > If allowed, update the data with the new data > [^Screen Recording 2021-02-05 at 6.50.31 PM.mov] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4146) [Atlas: Glossary] On updating the related terms, UI allows the user to add the already added term
[ https://issues.apache.org/jira/browse/ATLAS-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4146: -- Assignee: Mandar Ambawane > [Atlas: Glossary] On updating the related terms, UI allows the user to add > the already added term > - > > Key: ATLAS-4146 > URL: https://issues.apache.org/jira/browse/ATLAS-4146 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Mandar Ambawane >Priority: Major > Attachments: Screen Recording 2021-02-05 at 6.50.31 PM.mov > > > Steps to repro: > # Create a glossary(glossary_1) and a few terms (term_1, term_2, term_3, > term_4, term_5) > # Click on term_1 and add related terms "alsoSee" > # Choose term_5 of glossary_1 > # Provide inputs and assign > # term_5 will be added as a related term > # Now, add one more related term and choose the same term_5 of glossary_1 > [UI allows this] > # Provide new input and assign > # The assignment will be successful > This makes the user think, that term_5 with new data is saved. But that is > not the case, only old data is present > Expectation: > Do not allow the user to assign the same term again. > If allowed, update the data with the new data > [^Screen Recording 2021-02-05 at 6.50.31 PM.mov] -- This message was sent by Atlassian Jira (v8.3.4#803005)
