[jira] [Updated] (ATLAS-4117) Rename hive_db relationship attributes location
[ https://issues.apache.org/jira/browse/ATLAS-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Kundam updated ATLAS-4117: -- Summary: Rename hive_db relationship attributes location (was: Rename hive_db relationship attributes location and managedLocation) > Rename hive_db relationship attributes location > --- > > Key: ATLAS-4117 > URL: https://issues.apache.org/jira/browse/ATLAS-4117 > Project: Atlas > Issue Type: Task >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > > Rename hive_db relationship attributes as below to make differentiation > between attributes & relationship attributes. > Rename "location" to "locationPath" > Rename "managedLocation" to "managedLocationPath" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4117) Rename hive_db relationship attributes location
[ https://issues.apache.org/jira/browse/ATLAS-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Kundam updated ATLAS-4117: -- Description: Rename hive_db relationship attributes as below to make differentiation between attributes & relationship attributes. Rename "location" to "locationPath" was: Rename hive_db relationship attributes as below to make differentiation between attributes & relationship attributes. Rename "location" to "locationPath" Rename "managedLocation" to "managedLocationPath" > Rename hive_db relationship attributes location > --- > > Key: ATLAS-4117 > URL: https://issues.apache.org/jira/browse/ATLAS-4117 > Project: Atlas > Issue Type: Task >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > > Rename hive_db relationship attributes as below to make differentiation > between attributes & relationship attributes. > Rename "location" to "locationPath" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4117) Rename hive_db relationship attributes location and managedLocation
Radhika Kundam created ATLAS-4117: - Summary: Rename hive_db relationship attributes location and managedLocation Key: ATLAS-4117 URL: https://issues.apache.org/jira/browse/ATLAS-4117 Project: Atlas Issue Type: Task Reporter: Radhika Kundam Assignee: Radhika Kundam Rename hive_db relationship attributes as below to make differentiation between attributes & relationship attributes. Rename "location" to "locationPath" Rename "managedLocation" to "managedLocationPath" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4115) Ranger Tag Sync via ATLAS
[ https://issues.apache.org/jira/browse/ATLAS-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275227#comment-17275227 ] Sarath Subramanian commented on ATLAS-4115: --- [https://github.com/apache/atlas/blob/master/addons/models/-Area0/0011-glossary_model.json#L228] AtlasGlossaryCategory is a valid type within Atlas. Can you check with Ranger team if the types has been initialized completely within Ranger > Ranger Tag Sync via ATLAS > - > > Key: ATLAS-4115 > URL: https://issues.apache.org/jira/browse/ATLAS-4115 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Tansheet Izhad >Priority: Major > > Currently trying to do ranger tag sync with a new in-build apache Atlas. > Using the ATLAS_REST_ENDPOINT for the tag sync. > But getting the following error: > > {code:java} > 28 Jan 2021 17:17:57 ERROR AtlasRESTTagSource [Thread-7] - 287 failed to > download tags from Atlas > org.apache.atlas.exception.AtlasBaseException: Given typename > AtlasGlossaryCategory was invalid > at > org.apache.atlas.type.AtlasTypeRegistry.getType(AtlasTypeRegistry.java:108) > at > org.apache.atlas.type.AtlasRelationshipType.resolveReferences(AtlasRelationshipType.java:94) > at > org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.resolveReferences(AtlasTypeRegistry.java:373) > at > org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypes(AtlasTypeRegistry.java:445) > at > org.apache.ranger.tagsync.source.atlasrest.AtlasRESTTagSource.getAtlasActiveEntities(AtlasRESTTagSource.java:284) > at > org.apache.ranger.tagsync.source.atlasrest.AtlasRESTTagSource.synchUp(AtlasRESTTagSource.java:217) > at > org.apache.ranger.tagsync.source.atlasrest.AtlasRESTTagSource.run(AtlasRESTTagSource.java:200) > {code} > Looks like it's failing because of invalid Type. But not able to find > AtlasGlossaryCategory type on the atlas UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[ https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274449#comment-17274449 ] Keval Bhatt commented on ATLAS-4116: Example: https://github.com/apache/atlas/blob/master/dashboardv3/public/js/utils/Helper.js#L121 > UI should not allow the user to create a glossary with blank(" ") name > -- > > Key: ATLAS-4116 > URL: https://issues.apache.org/jira/browse/ATLAS-4116 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch, > Atlas-4116Fix.png > > > When just space is input the "Create" button is not enabled, but when the > space is selected, then the "Create" button is enabled and User is allowed to > click on "*Create*". > This results in un-necessary failures > * > {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and > name are missing. Failed to derive a unique name for Glossary"} > * > It is better to not allow clicking on "Create" for such an input via UI -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[ https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274448#comment-17274448 ] Keval Bhatt commented on ATLAS-4116: [~prasadpp13] is it possible to keep all the "keyup" event in once place? > UI should not allow the user to create a glossary with blank(" ") name > -- > > Key: ATLAS-4116 > URL: https://issues.apache.org/jira/browse/ATLAS-4116 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch, > Atlas-4116Fix.png > > > When just space is input the "Create" button is not enabled, but when the > space is selected, then the "Create" button is enabled and User is allowed to > click on "*Create*". > This results in un-necessary failures > * > {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and > name are missing. Failed to derive a unique name for Glossary"} > * > It is better to not allow clicking on "Create" for such an input via UI -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[ https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274410#comment-17274410 ] Durga Kadam commented on ATLAS-4116: +1 given patch is working fine > UI should not allow the user to create a glossary with blank(" ") name > -- > > Key: ATLAS-4116 > URL: https://issues.apache.org/jira/browse/ATLAS-4116 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch, > Atlas-4116Fix.png > > > When just space is input the "Create" button is not enabled, but when the > space is selected, then the "Create" button is enabled and User is allowed to > click on "*Create*". > This results in un-necessary failures > * > {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and > name are missing. Failed to derive a unique name for Glossary"} > * > It is better to not allow clicking on "Create" for such an input via UI -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[ https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274404#comment-17274404 ] Prasad P. Pawar commented on ATLAS-4116: Hi, This fix is provided on the available patch, also include a fix on creating/edit glossary/term/classification, create an entity, detail page label, create business metadata, save search input. > UI should not allow the user to create a glossary with blank(" ") name > -- > > Key: ATLAS-4116 > URL: https://issues.apache.org/jira/browse/ATLAS-4116 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch, > Atlas-4116Fix.png > > > When just space is input the "Create" button is not enabled, but when the > space is selected, then the "Create" button is enabled and User is allowed to > click on "*Create*". > This results in un-necessary failures > * > {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and > name are missing. Failed to derive a unique name for Glossary"} > * > It is better to not allow clicking on "Create" for such an input via UI -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[ https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4116: --- Attachment: Atlas-4116Fix.png > UI should not allow the user to create a glossary with blank(" ") name > -- > > Key: ATLAS-4116 > URL: https://issues.apache.org/jira/browse/ATLAS-4116 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Attachments: Atlas-4116Fix.png > > > When just space is input the "Create" button is not enabled, but when the > space is selected, then the "Create" button is enabled and User is allowed to > click on "*Create*". > This results in un-necessary failures > * > {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and > name are missing. Failed to derive a unique name for Glossary"} > * > It is better to not allow clicking on "Create" for such an input via UI -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
Nixon Rodrigues created ATLAS-4116: -- Summary: UI should not allow the user to create a glossary with blank(" ") name Key: ATLAS-4116 URL: https://issues.apache.org/jira/browse/ATLAS-4116 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues Assignee: Prasad P. Pawar When just space is input the "Create" button is not enabled, but when the space is selected, then the "Create" button is enabled and User is allowed to click on "*Create*". This results in un-necessary failures * {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and name are missing. Failed to derive a unique name for Glossary"} * It is better to not allow clicking on "Create" for such an input via UI -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [atlas] bmaidics closed pull request #118: ATLAS-4111: Add replicationFactor attribute to kafka topic entity
bmaidics closed pull request #118: URL: https://github.com/apache/atlas/pull/118 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org