[jira] [Assigned] (ATLAS-4833) Export/Import : When relationship is updated to block tag , the imported lineage doesn't have the updated relationship

[ https://issues.apache.org/jira/browse/ATLAS-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4833: -- Assignee: chaitali borole > Export/Import : When relationship is updated to block tag

[jira] [Updated] (ATLAS-4802) Atlas 'updateTime' parameter is not updated when business metadata, labels is edited.

[ https://issues.apache.org/jira/browse/ATLAS-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4802: --- Summary: Atlas 'updateTime' parameter is not updated when business metadata, labels is

[jira] [Commented] (ATLAS-4225) Support for Chinese character in entity data.

[ https://issues.apache.org/jira/browse/ATLAS-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823133#comment-17823133 ] chaitali borole commented on ATLAS-4225: creating a new RR with patch which is in sync with

[jira] [Updated] (ATLAS-4788) Encrpytion of clear text kafka password in application.properties

[ https://issues.apache.org/jira/browse/ATLAS-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4788: --- Summary: Encrpytion of clear text kafka password in application.properties (was:

[jira] [Updated] (ATLAS-4788) Encrpytion of kafka password in ap+plication.properties

[ https://issues.apache.org/jira/browse/ATLAS-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4788: --- Summary: Encrpytion of kafka password in ap+plication.properties (was: Kafka password is in

[jira] [Created] (ATLAS-4802) Atlas 'updateTime' parameter is not updated when business metadata is edited.

chaitali borole created ATLAS-4802: -- Summary: Atlas 'updateTime' parameter is not updated when business metadata is edited. Key: ATLAS-4802 URL: https://issues.apache.org/jira/browse/ATLAS-4802

[jira] [Updated] (ATLAS-4788) Kafka password is in clear text in application.properties

[ https://issues.apache.org/jira/browse/ATLAS-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4788: --- Summary: Kafka password is in clear text in application.properties (was: Kafka pass is in

[jira] [Created] (ATLAS-4788) Kafka pass is in clear text in application.properties

chaitali borole created ATLAS-4788: -- Summary: Kafka pass is in clear text in application.properties Key: ATLAS-4788 URL: https://issues.apache.org/jira/browse/ATLAS-4788 Project: Atlas

[jira] [Created] (ATLAS-4757) Regression : DSL queries redirected to passive server fails

chaitali borole created ATLAS-4757: -- Summary: Regression : DSL queries redirected to passive server fails Key: ATLAS-4757 URL: https://issues.apache.org/jira/browse/ATLAS-4757 Project: Atlas

[jira] [Updated] (ATLAS-4756) Entity_update should be sent after classification is deleted and added from ctas and parent

[ https://issues.apache.org/jira/browse/ATLAS-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4756: --- Summary: Entity_update should be sent after classification is deleted and added from ctas

[jira] [Created] (ATLAS-4756) Atlas is not passing ENTITY_UPDATE notification to Tagsync on classification delete

chaitali borole created ATLAS-4756: -- Summary: Atlas is not passing ENTITY_UPDATE notification to Tagsync on classification delete Key: ATLAS-4756 URL: https://issues.apache.org/jira/browse/ATLAS-4756

[jira] [Updated] (ATLAS-4717) When user doesn't have CRUD permission on classification , classification tag is still shown on detailsPage

[ https://issues.apache.org/jira/browse/ATLAS-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4717: --- Description: https://issues.apache.org/jira/browse/ATLAS-4717 Create tag - ptag Associate

[jira] [Updated] (ATLAS-4717) When user doesn't have CRUD permission on classification , classification tag is still shown on detailsPage

[ https://issues.apache.org/jira/browse/ATLAS-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4717: --- Description: Create tag - ptag Create tag - ctag with parent tag as ptag Associate ctag to

[jira] [Created] (ATLAS-4717) When user doesn't have CRUD permission on classification , classification tag is still shown on detailsPage

chaitali borole created ATLAS-4717: -- Summary: When user doesn't have CRUD permission on classification , classification tag is still shown on detailsPage Key: ATLAS-4717 URL:

[jira] [Updated] (ATLAS-3403) Term assigned to historical entity is not visible in Search results page.

[ https://issues.apache.org/jira/browse/ATLAS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3403: --- Fix Version/s: 3.0.0 > Term assigned to historical entity is not visible in Search results

[jira] [Updated] (ATLAS-3403) Term assigned to historical entity is not visible in Search results page.

[ https://issues.apache.org/jira/browse/ATLAS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3403: --- Affects Version/s: 3.0.0 > Term assigned to historical entity is not visible in Search

[jira] [Created] (ATLAS-4697) Upgrade Jackson version to 2.12.7.1

chaitali borole created ATLAS-4697: -- Summary: Upgrade Jackson version to 2.12.7.1 Key: ATLAS-4697 URL: https://issues.apache.org/jira/browse/ATLAS-4697 Project: Atlas Issue Type:

[jira] [Updated] (ATLAS-4688) Atlas - Upgrade Snake-yaml to 1.32

[ https://issues.apache.org/jira/browse/ATLAS-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4688: --- Summary: Atlas - Upgrade Snake-yaml to 1.32 (was: Atlas - Upgrade Snakye-yaml to 1.32) >

[jira] [Created] (ATLAS-4688) Atlas - Upgrade Snakye-yaml to 1.32

chaitali borole created ATLAS-4688: -- Summary: Atlas - Upgrade Snakye-yaml to 1.32 Key: ATLAS-4688 URL: https://issues.apache.org/jira/browse/ATLAS-4688 Project: Atlas Issue Type:

[jira] [Updated] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0

[ https://issues.apache.org/jira/browse/ATLAS-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4677: --- Fix Version/s: 2.0.0 > Atlas - Upgrade commons-configuration to 2.8.0 >

[jira] [Created] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0

chaitali borole created ATLAS-4677: -- Summary: Atlas - Upgrade commons-configuration to 2.8.0 Key: ATLAS-4677 URL: https://issues.apache.org/jira/browse/ATLAS-4677 Project: Atlas Issue Type:

[jira] [Created] (ATLAS-4670) Upgrade Jackson version to 2.13.3

chaitali borole created ATLAS-4670: -- Summary: Upgrade Jackson version to 2.13.3 Key: ATLAS-4670 URL: https://issues.apache.org/jira/browse/ATLAS-4670 Project: Atlas Issue Type: Improvement

[jira] [Assigned] (ATLAS-4669) Atlas - Upgrade Junit to 4.13.2

[ https://issues.apache.org/jira/browse/ATLAS-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4669: -- Assignee: chaitali borole > Atlas - Upgrade Junit to 4.13.2 >

[jira] [Updated] (ATLAS-4669) Atlas - Upgrade Junit to 4.13.2

[ https://issues.apache.org/jira/browse/ATLAS-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4669: --- Description: currently Junit version is 4.13.1 > Atlas - Upgrade Junit to 4.13.2 >

[jira] [Created] (ATLAS-4669) Atlas - Upgrade Junit to 4.13.2

chaitali borole created ATLAS-4669: -- Summary: Atlas - Upgrade Junit to 4.13.2 Key: ATLAS-4669 URL: https://issues.apache.org/jira/browse/ATLAS-4669 Project: Atlas Issue Type: Improvement

[jira] [Updated] (ATLAS-4662) Upgrade POI to 5.2.2

[ https://issues.apache.org/jira/browse/ATLAS-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4662: --- Description: POI and POI-ooxml version is 4.1.1 > Upgrade POI to 5.2.2 >

[jira] [Created] (ATLAS-4662) Upgrade POI to 5.2.2

chaitali borole created ATLAS-4662: -- Summary: Upgrade POI to 5.2.2 Key: ATLAS-4662 URL: https://issues.apache.org/jira/browse/ATLAS-4662 Project: Atlas Issue Type: Improvement Affects

[jira] [Updated] (ATLAS-4647) Upgrade Spring Security to 5.7.2

[ https://issues.apache.org/jira/browse/ATLAS-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4647: --- Fix Version/s: 2.0.0 > Upgrade Spring Security to 5.7.2 > >

[jira] [Updated] (ATLAS-4653) Upgrade Hadoop to 3.3.3

[ https://issues.apache.org/jira/browse/ATLAS-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4653: --- Description: currently Hadoop is using 3.3.0 and 3.0.3 This patch also upgrades

[jira] [Created] (ATLAS-4653) Upgrade Hadoop to 3.3.3

chaitali borole created ATLAS-4653: -- Summary: Upgrade Hadoop to 3.3.3 Key: ATLAS-4653 URL: https://issues.apache.org/jira/browse/ATLAS-4653 Project: Atlas Issue Type: Improvement

[jira] [Created] (ATLAS-4651) Upgrade Apache ZooKeeper to 3.8.0

chaitali borole created ATLAS-4651: -- Summary: Upgrade Apache ZooKeeper to 3.8.0 Key: ATLAS-4651 URL: https://issues.apache.org/jira/browse/ATLAS-4651 Project: Atlas Issue Type: Improvement

[jira] [Created] (ATLAS-4650) Upgrade Apache Commons BeanUtils to 1.9.4

chaitali borole created ATLAS-4650: -- Summary: Upgrade Apache Commons BeanUtils to 1.9.4 Key: ATLAS-4650 URL: https://issues.apache.org/jira/browse/ATLAS-4650 Project: Atlas Issue Type:

[jira] [Created] (ATLAS-4649) Upgrade Spring Framework to 4.3.30.RELEASE/5.3.21

chaitali borole created ATLAS-4649: -- Summary: Upgrade Spring Framework to 4.3.30.RELEASE/5.3.21 Key: ATLAS-4649 URL: https://issues.apache.org/jira/browse/ATLAS-4649 Project: Atlas Issue

[jira] [Updated] (ATLAS-4648) Upgrade Netty version to 4.1.78.Final

[ https://issues.apache.org/jira/browse/ATLAS-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4648: --- Summary: Upgrade Netty version to 4.1.78.Final (was: Upgrade Netty Project to 4.1.78.Final)

[jira] [Created] (ATLAS-4648) Upgrade Netty Project to 4.1.78.Final

chaitali borole created ATLAS-4648: -- Summary: Upgrade Netty Project to 4.1.78.Final Key: ATLAS-4648 URL: https://issues.apache.org/jira/browse/ATLAS-4648 Project: Atlas Issue Type:

[jira] [Updated] (ATLAS-4647) Upgrade Spring Security to 5.7.2

[ https://issues.apache.org/jira/browse/ATLAS-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4647: --- Summary: Upgrade Spring Security to 5.7.2 (was: Atlas - Upgrade Spring Security to 5.7.2)

[jira] [Created] (ATLAS-4647) Atlas - Upgrade Spring Security to 5.7.2

chaitali borole created ATLAS-4647: -- Summary: Atlas - Upgrade Spring Security to 5.7.2 Key: ATLAS-4647 URL: https://issues.apache.org/jira/browse/ATLAS-4647 Project: Atlas Issue Type:

[jira] [Updated] (ATLAS-4507) Atlas - Upgrade testng to 7.0.0

[ https://issues.apache.org/jira/browse/ATLAS-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4507: --- Summary: Atlas - Upgrade testng to 7.0.0 (was: Atlas - Upgrade testng to 6.11 or later) >

[jira] [Updated] (ATLAS-4507) Atlas - Upgrade testng to 7.0.0

[ https://issues.apache.org/jira/browse/ATLAS-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4507: --- Description: Currently Atlas is using 6.9.4 version for testng Upgrading testng to 7.0.0

[jira] [Assigned] (ATLAS-4507) Atlas - Upgrade testng to 6.11 or later

[ https://issues.apache.org/jira/browse/ATLAS-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4507: -- Assignee: chaitali borole > Atlas - Upgrade testng to 6.11 or later >

[jira] [Created] (ATLAS-4507) Atlas - Upgrade testng to 6.11 or later

chaitali borole created ATLAS-4507: -- Summary: Atlas - Upgrade testng to 6.11 or later Key: ATLAS-4507 URL: https://issues.apache.org/jira/browse/ATLAS-4507 Project: Atlas Issue Type:

[jira] [Updated] (ATLAS-4503) Handle cross version messages in Atlas server

[ https://issues.apache.org/jira/browse/ATLAS-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4503: --- Summary: Handle cross version messages in Atlas server (was: SDX Version Compatibility:

[jira] [Created] (ATLAS-4503) SDX Version Compatibility: Handle cross version messages in Atlas server

chaitali borole created ATLAS-4503: -- Summary: SDX Version Compatibility: Handle cross version messages in Atlas server Key: ATLAS-4503 URL: https://issues.apache.org/jira/browse/ATLAS-4503 Project:

[jira] [Created] (ATLAS-4496) Atlas - Upgrade elasticsearch to 7.14.0

chaitali borole created ATLAS-4496: -- Summary: Atlas - Upgrade elasticsearch to 7.14.0 Key: ATLAS-4496 URL: https://issues.apache.org/jira/browse/ATLAS-4496 Project: Atlas Issue Type:

[jira] [Updated] (ATLAS-4493) Upgrade netty to 4.1.69

[ https://issues.apache.org/jira/browse/ATLAS-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4493: --- Summary: Upgrade netty to 4.1.69 (was: Upgrade netty to 4.1.68+) > Upgrade netty to 4.1.69

[jira] [Assigned] (ATLAS-4493) atlas - Upgrade netty to 4.1.68+

[ https://issues.apache.org/jira/browse/ATLAS-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4493: -- Assignee: chaitali borole > atlas - Upgrade netty to 4.1.68+ >

[jira] [Updated] (ATLAS-4493) Upgrade netty to 4.1.68+

[ https://issues.apache.org/jira/browse/ATLAS-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4493: --- Summary: Upgrade netty to 4.1.68+ (was: atlas - Upgrade netty to 4.1.68+) > Upgrade netty

[jira] [Created] (ATLAS-4493) atlas - Upgrade netty to 4.1.68+

chaitali borole created ATLAS-4493: -- Summary: atlas - Upgrade netty to 4.1.68+ Key: ATLAS-4493 URL: https://issues.apache.org/jira/browse/ATLAS-4493 Project: Atlas Issue Type: Improvement

[jira] [Updated] (ATLAS-4079) Atlas-Upgrade jackson to 2.11.0+

[ https://issues.apache.org/jira/browse/ATLAS-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4079: --- Fix Version/s: 2.3.0 > Atlas-Upgrade jackson to 2.11.0+ > >

[jira] [Updated] (ATLAS-4079) Atlas-Upgrade jackson to 2.11.0+

[ https://issues.apache.org/jira/browse/ATLAS-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4079: --- Affects Version/s: 2.3.0 > Atlas-Upgrade jackson to 2.11.0+ >

[jira] [Updated] (ATLAS-4446) Atlas - Upgrade elasticsearch to 7.6.0

[ https://issues.apache.org/jira/browse/ATLAS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4446: --- Summary: Atlas - Upgrade elasticsearch to 7.6.0 (was: Atlas - Upgrade elasticsearch to

[jira] [Created] (ATLAS-4446) Atlas - Upgrade elasticsearch to 7.14.0

chaitali borole created ATLAS-4446: -- Summary: Atlas - Upgrade elasticsearch to 7.14.0 Key: ATLAS-4446 URL: https://issues.apache.org/jira/browse/ATLAS-4446 Project: Atlas Issue Type:

[jira] [Commented] (ATLAS-4440) Upgrade Atlas's Kafka dependency to 2.8

[ https://issues.apache.org/jira/browse/ATLAS-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424001#comment-17424001 ] chaitali borole commented on ATLAS-4440: Hello [~amestry], Patch looks good to me. +1 for the

[jira] [Created] (ATLAS-4428) Enhance Atlas hook messages to capture hook version & message source

chaitali borole created ATLAS-4428: -- Summary: Enhance Atlas hook messages to capture hook version & message source Key: ATLAS-4428 URL: https://issues.apache.org/jira/browse/ATLAS-4428 Project:

[jira] [Created] (ATLAS-4377) Atlas - Upgrade Spring Security to 5.4.4+/5.3.8+/5.2.9+

chaitali borole created ATLAS-4377: -- Summary: Atlas - Upgrade Spring Security to 5.4.4+/5.3.8+/5.2.9+ Key: ATLAS-4377 URL: https://issues.apache.org/jira/browse/ATLAS-4377 Project: Atlas

[jira] [Created] (ATLAS-4376) AtlasClientV2 getRelationshipDefByName does not work

chaitali borole created ATLAS-4376: -- Summary: AtlasClientV2 getRelationshipDefByName does not work Key: ATLAS-4376 URL: https://issues.apache.org/jira/browse/ATLAS-4376 Project: Atlas Issue

[jira] [Resolved] (ATLAS-4208) [Atlas: Audits] 2 audits are created when a label is added and removed in 1 go from an entity

[ https://issues.apache.org/jira/browse/ATLAS-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole resolved ATLAS-4208. Resolution: Not A Bug > [Atlas: Audits] 2 audits are created when a label is added and

[jira] [Commented] (ATLAS-4208) [Atlas: Audits] 2 audits are created when a label is added and removed in 1 go from an entity

[ https://issues.apache.org/jira/browse/ATLAS-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383315#comment-17383315 ] chaitali borole commented on ATLAS-4208: Hello [~dharshmk], I debugged and reproduced the

[jira] [Created] (ATLAS-4351) Maven-jetty throwing warnings when running Integration tests for conflicting jars in classpath

chaitali borole created ATLAS-4351: -- Summary: Maven-jetty throwing warnings when running Integration tests for conflicting jars in classpath Key: ATLAS-4351 URL: https://issues.apache.org/jira/browse/ATLAS-4351

[jira] [Assigned] (ATLAS-4208) [Atlas: Audits] 2 audits are created when a label is added and removed in 1 go from an entity

[ https://issues.apache.org/jira/browse/ATLAS-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4208: -- Assignee: chaitali borole > [Atlas: Audits] 2 audits are created when a label is

[jira] [Assigned] (ATLAS-4317) Atlas should use downstream Curator

[ https://issues.apache.org/jira/browse/ATLAS-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4317: -- Assignee: chaitali borole > Atlas should use downstream Curator >

[jira] [Updated] (ATLAS-4317) Atlas should use downstream Curator

[ https://issues.apache.org/jira/browse/ATLAS-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4317: --- Description: Upgrade curator jar version to 4.3.0 > Atlas should use downstream Curator >

[jira] [Created] (ATLAS-4317) Atlas should use downstream Curator

chaitali borole created ATLAS-4317: -- Summary: Atlas should use downstream Curator Key: ATLAS-4317 URL: https://issues.apache.org/jira/browse/ATLAS-4317 Project: Atlas Issue Type:

[jira] [Assigned] (ATLAS-4174) [Atlas: Glossary Term Bulk Import] When the file size is large (5 mb) bulk import times out

[ https://issues.apache.org/jira/browse/ATLAS-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4174: -- Assignee: chaitali borole (was: Mayank Jain) > [Atlas: Glossary Term Bulk Import]

[jira] [Created] (ATLAS-4255) Atlas - Upgrade netty to 4.1.61

chaitali borole created ATLAS-4255: -- Summary: Atlas - Upgrade netty to 4.1.61 Key: ATLAS-4255 URL: https://issues.apache.org/jira/browse/ATLAS-4255 Project: Atlas Issue Type: Task

[jira] [Assigned] (ATLAS-4179) [Atlas: Glossary Term Bulk Import] Incorrect error message when only dependent term is not present in bulk import

[ https://issues.apache.org/jira/browse/ATLAS-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4179: -- Assignee: chaitali borole > [Atlas: Glossary Term Bulk Import] Incorrect error

[jira] [Resolved] (ATLAS-4228) Kafka topic names should be configurable

[ https://issues.apache.org/jira/browse/ATLAS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole resolved ATLAS-4228. Resolution: Abandoned > Kafka topic names should be configurable >

[jira] [Created] (ATLAS-4228) Kafka topic names should be configurable

chaitali borole created ATLAS-4228: -- Summary: Kafka topic names should be configurable Key: ATLAS-4228 URL: https://issues.apache.org/jira/browse/ATLAS-4228 Project: Atlas Issue Type: Task

[jira] [Updated] (ATLAS-4221) Solr collection names should be configurable

[ https://issues.apache.org/jira/browse/ATLAS-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4221: --- Description: Currently in Atlas, the collection names are not configurable We need to

[jira] [Created] (ATLAS-4221) Solr collection names should be configurable

chaitali borole created ATLAS-4221: -- Summary: Solr collection names should be configurable Key: ATLAS-4221 URL: https://issues.apache.org/jira/browse/ATLAS-4221 Project: Atlas Issue Type:

[jira] [Updated] (ATLAS-4194) [Read Type Auth] Metrics API shows the typecounts for types not readable by user

[ https://issues.apache.org/jira/browse/ATLAS-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4194: --- Affects Version/s: 3.0.0 2.0.0 > [Read Type Auth] Metrics API shows

[jira] [Created] (ATLAS-4194) [Read Type Auth] Metrics API shows the typecounts for types not readable by user

chaitali borole created ATLAS-4194: -- Summary: [Read Type Auth] Metrics API shows the typecounts for types not readable by user Key: ATLAS-4194 URL: https://issues.apache.org/jira/browse/ATLAS-4194

[jira] [Assigned] (ATLAS-4180) [Atlas: Glossary Term Bulk Import] Update error message thrown while using "@" in glossary/term name

[ https://issues.apache.org/jira/browse/ATLAS-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4180: -- Assignee: chaitali borole > [Atlas: Glossary Term Bulk Import] Update error message

[jira] [Resolved] (ATLAS-4175) [Atlas: Read type auth] [Regression]: User is able to create a sub-type with non-readable super type

[ https://issues.apache.org/jira/browse/ATLAS-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole resolved ATLAS-4175. Resolution: Cannot Reproduce > [Atlas: Read type auth] [Regression]: User is able to

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

[ https://issues.apache.org/jira/browse/ATLAS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3976: --- Affects Version/s: 2.1.0 > On creating a type with a type_name that already exists as a

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

[ https://issues.apache.org/jira/browse/ATLAS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3976: --- Fix Version/s: 2.0.0 3.0.0 > On creating a type with a type_name that

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

[ https://issues.apache.org/jira/browse/ATLAS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3976: --- Affects Version/s: 3.0.0 > On creating a type with a type_name that already exists as a

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

[ https://issues.apache.org/jira/browse/ATLAS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3976: --- Affects Version/s: (was: 2.1.0) 2.0.0 > On creating a type with a

[jira] [Commented] (ATLAS-4176) [Atlas: Read type auth] When un-authorised user creates a sub type, incorrect error message is thrown

[ https://issues.apache.org/jira/browse/ATLAS-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293610#comment-17293610 ] chaitali borole commented on ATLAS-4176: [~dharshmk], Kindly share your policy details if you

[jira] [Assigned] (ATLAS-4176) [Atlas: Read type auth] When un-authorised user creates a sub type, incorrect error message is thrown

[ https://issues.apache.org/jira/browse/ATLAS-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4176: -- Assignee: chaitali borole > [Atlas: Read type auth] When un-authorised user creates a

[jira] [Assigned] (ATLAS-4175) [Atlas: Read type auth] [Regression]: User is able to create a sub-type with non-readable super type

[ https://issues.apache.org/jira/browse/ATLAS-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4175: -- Assignee: chaitali borole > [Atlas: Read type auth] [Regression]: User is able to

[jira] [Assigned] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities

[ https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4171: -- Assignee: chaitali borole (was: Umesh Padashetty) > Authorisation : Bulk entity

[jira] [Assigned] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities

[ https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4171: -- Assignee: Umesh Padashetty (was: chaitali borole) > Authorisation : Bulk entity

[jira] [Assigned] (ATLAS-4172) Authorisation : Bulk create/update entity POST API doesn't create/update authorised entities

[ https://issues.apache.org/jira/browse/ATLAS-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4172: -- Assignee: chaitali borole > Authorisation : Bulk create/update entity POST API

[jira] [Assigned] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities

[ https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4171: -- Assignee: chaitali borole > Authorisation : Bulk entity DELETE API doesn't delete

[jira] [Assigned] (ATLAS-3975) User is allowed to create an entity with non-readable entity type

[ https://issues.apache.org/jira/browse/ATLAS-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-3975: -- Assignee: chaitali borole > User is allowed to create an entity with non-readable

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

[ https://issues.apache.org/jira/browse/ATLAS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-3976: -- Assignee: chaitali borole (was: Nixon Rodrigues) > On creating a type with a

[jira] [Assigned] (ATLAS-4134) [Atlas:Glossary] Update conflict error message for glossary

[ https://issues.apache.org/jira/browse/ATLAS-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4134: -- Assignee: chaitali borole > [Atlas:Glossary] Update conflict error message for

[jira] [Assigned] (ATLAS-4148) [Atlas: Glossary Term Bulk Import] Incorrect error code displayed when no data found in the uploaded file

[ https://issues.apache.org/jira/browse/ATLAS-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4148: -- Assignee: chaitali borole > [Atlas: Glossary Term Bulk Import] Incorrect error code

[jira] [Assigned] (ATLAS-4147) [Atlas: Glossary Term Bulk Import] When un_supported file type is passed error message displays "file type {0}"

[ https://issues.apache.org/jira/browse/ATLAS-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4147: -- Assignee: chaitali borole > [Atlas: Glossary Term Bulk Import] When un_supported file

[jira] [Created] (ATLAS-4120) Entities cached in setLabels() don’t have any attributes populated.

chaitali borole created ATLAS-4120: -- Summary: Entities cached in setLabels() don’t have any attributes populated. Key: ATLAS-4120 URL: https://issues.apache.org/jira/browse/ATLAS-4120 Project: Atlas

[jira] [Resolved] (ATLAS-3973) Inappropriate message on performing create with non-readable super type

[ https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole resolved ATLAS-3973. Resolution: Cannot Reproduce > Inappropriate message on performing create with

[jira] [Resolved] (ATLAS-3973) Inappropriate message on performing create with non-readable super type

[ https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole resolved ATLAS-3973. Resolution: Fixed > Inappropriate message on performing create with non-readable super

[jira] [Reopened] (ATLAS-3973) Inappropriate message on performing create with non-readable super type

[ https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reopened ATLAS-3973: > Inappropriate message on performing create with non-readable super type >

[jira] [Resolved] (ATLAS-4104) Throw 400 malformed request error from atlas when the payload is malformed

[ https://issues.apache.org/jira/browse/ATLAS-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole resolved ATLAS-4104. Resolution: Duplicate > Throw 400 malformed request error from atlas when the payload is

[jira] [Created] (ATLAS-4104) Throw 400 malformed request error from atlas when the payload is malformed

chaitali borole created ATLAS-4104: -- Summary: Throw 400 malformed request error from atlas when the payload is malformed Key: ATLAS-4104 URL: https://issues.apache.org/jira/browse/ATLAS-4104

[jira] [Comment Edited] (ATLAS-3973) Inappropriate message on performing create with non-readable super type

[ https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264721#comment-17264721 ] chaitali borole edited comment on ATLAS-3973 at 1/14/21, 9:45 AM: --

[jira] [Commented] (ATLAS-3973) Inappropriate message on performing create with non-readable super type

[ https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264721#comment-17264721 ] chaitali borole commented on ATLAS-3973: [~dharshmk], I didn't find this issue reproducible here

[jira] [Assigned] (ATLAS-3973) Inappropriate message on performing create with non-readable super type

[ https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-3973: -- Assignee: chaitali borole > Inappropriate message on performing create with

[jira] [Created] (ATLAS-4093) "NullPointerException" is thrown when mandatory attribute is missing endDef-name

chaitali borole created ATLAS-4093: -- Summary: "NullPointerException" is thrown when mandatory attribute is missing endDef-name Key: ATLAS-4093 URL: https://issues.apache.org/jira/browse/ATLAS-4093

  1   2   3   >