[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: --- Attachment: ATLAS-4034-ATLAS-4041.patch > It will be good to have the operation status i

[jira] [Assigned] (ATLAS-4016) Update authorization - "admin-audits" for retrieving admin audits

[ https://issues.apache.org/jira/browse/ATLAS-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane reassigned ATLAS-4016: -- Assignee: Mandar Ambawane > Update authorization - "admin-audits" f

[jira] [Updated] (ATLAS-4016) Update authorization - "admin-audits" for retrieving admin audits

[ https://issues.apache.org/jira/browse/ATLAS-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4016: --- Attachment: ATLAS-4016.patch > Update authorization - "admin-audits" for ret

[jira] [Updated] (ATLAS-3813) Import-.sh script shows wrong message of Import success even when there are no database/table/topic are imported in the System

[ https://issues.apache.org/jira/browse/ATLAS-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-3813: --- Attachment: ATLAS-3813-V4.patch > Import-.sh script shows wrong message of Import succ

[jira] [Updated] (ATLAS-4092) Remove unused attributes and add right attributes to the atlas admin audit api

[ https://issues.apache.org/jira/browse/ATLAS-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4092: --- Attachment: (was: ATLAS-4092.patch) > Remove unused attributes and add right attribu

[jira] [Updated] (ATLAS-4092) Remove unused attributes and add right attributes to the atlas admin audit api

[ https://issues.apache.org/jira/browse/ATLAS-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4092: --- Attachment: ATLAS-4092.patch > Remove unused attributes and add right attribu

[jira] [Assigned] (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 reassigned ATLAS-4103: -- Assignee: Mandar Ambawane > While listing Purge operation records in Administrat

[jira] [Commented] (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:comment-tabpanel=17271420#comment-17271420 ] Mandar Ambawane commented on ATLAS-4105: Hi [~umesh.padashetty], This is the behavior as per

[jira] [Assigned] (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 reassigned ATLAS-4105: -- Assignee: Mandar Ambawane > table details are set to null for a drop

[jira] [Created] (ATLAS-4092) Remove unused attributes and add right attributes to the atlas admin audit api

Mandar Ambawane created ATLAS-4092: -- Summary: Remove unused attributes and add right attributes to the atlas admin audit api Key: ATLAS-4092 URL: https://issues.apache.org/jira/browse/ATLAS-4092

[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

[ https://issues.apache.org/jira/browse/ATLAS-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4124: --- Summary: Restrict user from deleting Business Metadata, if Business Metadata is already

[jira] [Created] (ATLAS-4124) Prevent user from deleting Business Metadata, if Business Metadata is already associated with an entity

Mandar Ambawane created ATLAS-4124: -- Summary: Prevent user from deleting Business Metadata, if Business Metadata is already associated with an entity Key: ATLAS-4124 URL: https://issues.apache.org/jira/browse

[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

[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] Is

[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

[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

[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 Ad

[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 start

[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

[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 Atla

[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_DEL

[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 i

[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

[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

[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

[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

[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

[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

[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

[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 operat

[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 &quo

[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 miss

[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 differ

[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 operat

[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 win

[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 creat

[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 tab

[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 classificat

[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,

[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 ta

[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 wh

[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 ent

[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 defi

[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

[ https://issues.apache.org/jira/browse/ATLAS-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4124: --- Component/s: atlas-core > Restrict user from deleting Business Metadata, if Busin

[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

[ https://issues.apache.org/jira/browse/ATLAS-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4124: --- Affects Version/s: 2.1.0 > Restrict user from deleting Business Metadata, if Busin

[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

[ https://issues.apache.org/jira/browse/ATLAS-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4124: --- Description: We can delete the entire BusinessMetadata TypeDef using the curl command

[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

[ https://issues.apache.org/jira/browse/ATLAS-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4124: --- Fix Version/s: 3.0.0 > Restrict user from deleting Business Metadata, if Business Metad

[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

[ https://issues.apache.org/jira/browse/ATLAS-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4124: --- Labels: BusinessMetadata (was: ) > Restrict user from deleting Business Metad

[jira] [Assigned] (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 reassigned ATLAS-4135: -- Assignee: Mandar Ambawane > [Atlas: Glossary Term Bulk Import] It will be g

[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,

[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 all

[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] W

[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 u

[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 crea

[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 miss

[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 tab

[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 wh

[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)

[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 w

[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 Namespace

[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 ad

[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

[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

[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 t

[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 Administrat

[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

[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

[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

[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

[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

[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 Improvem

[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

[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 w

[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-Ent

[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_fam

[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 entr

[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 entr

[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 For

[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 Imp

[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] W

[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 sta

[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 coun

[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 metr

[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 rela

[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 cr

[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 ex

[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

[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 ex

[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

[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

[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

[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

[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

[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 provi

[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 registe

[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 em

[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

[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 ed

[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

[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/

<    1   2   3   4   5   >