[jira] [Updated] (ATLAS-4115) Ranger Tag Sync via ATLAS
[
https://issues.apache.org/jira/browse/ATLAS-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tansheet Izhad updated ATLAS-4115:
--
Summary: Ranger Tag Sync via ATLAS (was: Ranger Tag Sync)
> 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] [Created] (ATLAS-4115) Ranger Tag Sync
Tansheet Izhad created ATLAS-4115:
-
Summary: Ranger Tag Sync
Key: ATLAS-4115
URL: https://issues.apache.org/jira/browse/ATLAS-4115
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Tansheet Izhad
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] [Updated] (ATLAS-4052) Upgrade elasticsearch version
[ https://issues.apache.org/jira/browse/ATLAS-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-4052: --- Description: Currently Atlas is pulling in elasticsearch-rest-client 6.6.0 which is really old. (was: Currently Atlas is pulling in elasticsearch-rest-client 5.6.4 which is really old.) > Upgrade elasticsearch version > - > > Key: ATLAS-4052 > URL: https://issues.apache.org/jira/browse/ATLAS-4052 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > Currently Atlas is pulling in elasticsearch-rest-client 6.6.0 which is really > old. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4074) [UI] Image download in Typesystem and Lineage has issue
[ https://issues.apache.org/jira/browse/ATLAS-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4074: -- Assignee: Prasad P. Pawar > [UI] Image download in Typesystem and Lineage has issue > --- > > Key: ATLAS-4074 > URL: https://issues.apache.org/jira/browse/ATLAS-4074 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > Lineage_issue_shows_black_background_if_downloaded_image_with_search_applied.png, > Typesystem_issue_overlapped_entity_names_in_exported_image.png > > > # In TypeSystem, downloaded image shows overlapped names of hosts/nodes if > the name length is too large. > # When user downloads the lineage with the search result shows highlighted > image with black background, also label is not properly visible due to black > background. > PFA evidence files -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4113) Atlas UI: Entity Lineage Details Box layout rendering and centring issue.
[ https://issues.apache.org/jira/browse/ATLAS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4113: -- Assignee: Prasad P. Pawar > Atlas UI: Entity Lineage Details Box layout rendering and centring issue. > - > > Key: ATLAS-4113 > URL: https://issues.apache.org/jira/browse/ATLAS-4113 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0 > > Attachments: entity-detailpage.png > > > The lineage layout doesn't seem to be centred on the page, also there is an > effect where the lineage appears from top-right. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274045#comment-17274045
]
ASF subversion and git services commented on ATLAS-4107:
Commit 8dd04d27e332b882868e3d5b281ff771f4795862 in atlas's branch
refs/heads/branch-2.0 from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8dd04d2 ]
ATLAS-4107: Atlas not picking the ldap bind password from the correct jceks
file #2 Unit test fix
(cherry picked from commit 39a067a215dc247ff787567e8f25ae52b83e010d)
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Labels: jceks, ldap
> Fix For: 3.0.0, 2.2.0
>
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274044#comment-17274044
]
ASF subversion and git services commented on ATLAS-4107:
Commit 39a067a215dc247ff787567e8f25ae52b83e010d in atlas's branch
refs/heads/master from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=39a067a ]
ATLAS-4107: Atlas not picking the ldap bind password from the correct jceks
file #2 Unit test fix
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Labels: jceks, ldap
> Fix For: 3.0.0, 2.2.0
>
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian resolved ATLAS-4107.
---
Resolution: Fixed
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Labels: jceks, ldap
> Fix For: 3.0.0, 2.2.0
>
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273950#comment-17273950
]
ASF subversion and git services commented on ATLAS-4107:
Commit bb745b9e90c517517f88cd66ccca845bf73dfeca in atlas's branch
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=bb745b9 ]
ATLAS-4107: Atlas not picking the ldap bind password from the correct jceks
file.
Change-Id: I8f457b63f3170c2b1313ab365223d18af6023f87
Signed-off-by: Sarath Subramanian
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Labels: jceks, ldap
> Fix For: 3.0.0, 2.2.0
>
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273952#comment-17273952
]
ASF subversion and git services commented on ATLAS-4107:
Commit 634db601bec844584875350865e61dd010515ebf in atlas's branch
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=634db60 ]
ATLAS-4107: Atlas not picking the ldap bind password from the correct jceks
file.
Change-Id: I8f457b63f3170c2b1313ab365223d18af6023f87
Signed-off-by: Sarath Subramanian
(cherry picked from commit bb745b9e90c517517f88cd66ccca845bf73dfeca)
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Labels: jceks, ldap
> Fix For: 3.0.0, 2.2.0
>
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4107:
--
Labels: jceks ldap (was: )
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Labels: jceks, ldap
> Fix For: 3.0.0, 2.2.0
>
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4107:
--
Fix Version/s: 2.2.0
3.0.0
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4107:
--
Affects Version/s: 2.1.0
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4107:
--
Component/s: atlas-core
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Review Request 73151: ATLAS-4107 :- Atlas not picking the ldap bind password from the correct jceks file.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73151/#review222538 --- Ship it! Ship It! - Sarath Subramanian On Jan. 28, 2021, 7:11 a.m., Nixon Rodrigues wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/73151/ > --- > > (Updated Jan. 28, 2021, 7:11 a.m.) > > > Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, > Nikhil Bonte, and Sarath Subramanian. > > > Bugs: ATLAS-4107 > https://issues.apache.org/jira/browse/ATLAS-4107 > > > Repository: atlas > > > Description > --- > > Atlas not picking the ldap bind password from the correct jceks file. > > There are two jceks file in Atlas configured from CM, ldap bind password > should be retrieved from hadoop.security.credential.provider.path instead > cert.stores.credential.provider.path. > > > Diffs > - > > intg/src/main/java/org/apache/atlas/ApplicationProperties.java e662c8fae > intg/src/main/java/org/apache/atlas/security/SecurityProperties.java > 2147cd17c > intg/src/main/java/org/apache/atlas/security/SecurityUtil.java 082c6378c > > > Diff: https://reviews.apache.org/r/73151/diff/2/ > > > Testing > --- > > Tested on normal cluster with password stored in jceks file and TLS cluster > with password stored in jceks file in Atlas. > > > Thanks, > > Nixon Rodrigues > >
[GitHub] [atlas] sarathsubramanian commented on pull request #118: ATLAS-4111: Add replicationFactor attribute to kafka topic entity
sarathsubramanian commented on pull request #118: URL: https://github.com/apache/atlas/pull/118#issuecomment-769304721 please close the PR. 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
[jira] [Updated] (ATLAS-4111) Add replicationFactor attribute to kafka topic entity
[ https://issues.apache.org/jira/browse/ATLAS-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-4111: -- Affects Version/s: 2.1.0 > Add replicationFactor attribute to kafka topic entity > - > > Key: ATLAS-4111 > URL: https://issues.apache.org/jira/browse/ATLAS-4111 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0 >Reporter: Barnabas Maidics >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Currently, the replicationFactor is missing from kafka topic entities in > Atlas. We should add them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [atlas] sarathsubramanian commented on pull request #118: ATLAS-4111: Add replicationFactor attribute to kafka topic entity
sarathsubramanian commented on pull request #118: URL: https://github.com/apache/atlas/pull/118#issuecomment-769304379 changes looks good. I merged the PR. 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
[jira] [Resolved] (ATLAS-4111) Add replicationFactor attribute to kafka topic entity
[ https://issues.apache.org/jira/browse/ATLAS-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian resolved ATLAS-4111. --- Resolution: Fixed > Add replicationFactor attribute to kafka topic entity > - > > Key: ATLAS-4111 > URL: https://issues.apache.org/jira/browse/ATLAS-4111 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0 >Reporter: Barnabas Maidics >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Currently, the replicationFactor is missing from kafka topic entities in > Atlas. We should add them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4111) Add replicationFactor attribute to kafka topic entity
[ https://issues.apache.org/jira/browse/ATLAS-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-4111: -- Fix Version/s: 2.2.0 3.0.0 > Add replicationFactor attribute to kafka topic entity > - > > Key: ATLAS-4111 > URL: https://issues.apache.org/jira/browse/ATLAS-4111 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0 >Reporter: Barnabas Maidics >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Currently, the replicationFactor is missing from kafka topic entities in > Atlas. We should add them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4111) Add replicationFactor attribute to kafka topic entity
[ https://issues.apache.org/jira/browse/ATLAS-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273943#comment-17273943 ] ASF subversion and git services commented on ATLAS-4111: Commit ade75fe55f88ef3b25be8da18acfbab3a8d293e2 in atlas's branch refs/heads/branch-2.0 from Barnabas Maidics [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ade75fe ] ATLAS-4111: Add 'replicationFactor' attribute to kafka_topic entity type + formatting changes Signed-off-by: Sarath Subramanian (cherry picked from commit ce1342dd6dd7cbc4d1e35bea3b26d08dc24bd67e) > Add replicationFactor attribute to kafka topic entity > - > > Key: ATLAS-4111 > URL: https://issues.apache.org/jira/browse/ATLAS-4111 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Reporter: Barnabas Maidics >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Currently, the replicationFactor is missing from kafka topic entities in > Atlas. We should add them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4111) Add replicationFactor attribute to kafka topic entity
[ https://issues.apache.org/jira/browse/ATLAS-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273942#comment-17273942 ] ASF subversion and git services commented on ATLAS-4111: Commit ce1342dd6dd7cbc4d1e35bea3b26d08dc24bd67e in atlas's branch refs/heads/master from Barnabas Maidics [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ce1342d ] ATLAS-4111: Add 'replicationFactor' attribute to kafka_topic entity type + formatting changes Signed-off-by: Sarath Subramanian > Add replicationFactor attribute to kafka topic entity > - > > Key: ATLAS-4111 > URL: https://issues.apache.org/jira/browse/ATLAS-4111 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Reporter: Barnabas Maidics >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Currently, the replicationFactor is missing from kafka topic entities in > Atlas. We should add them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [atlas] bmaidics commented on pull request #118: ATLAS-4111: Add replicationFactor attribute to kafka topic entity
bmaidics commented on pull request #118: URL: https://github.com/apache/atlas/pull/118#issuecomment-769183849 Thanks @sarathsubramanian for the review, I updated the PR with the changes. 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
Re: Review Request 73151: ATLAS-4107 :- Atlas not picking the ldap bind password from the correct jceks file.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73151/ --- (Updated Jan. 28, 2021, 3:11 p.m.) Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, Nikhil Bonte, and Sarath Subramanian. Changes --- Addressed Review comments from Sarath Bugs: ATLAS-4107 https://issues.apache.org/jira/browse/ATLAS-4107 Repository: atlas Description --- Atlas not picking the ldap bind password from the correct jceks file. There are two jceks file in Atlas configured from CM, ldap bind password should be retrieved from hadoop.security.credential.provider.path instead cert.stores.credential.provider.path. Diffs (updated) - intg/src/main/java/org/apache/atlas/ApplicationProperties.java e662c8fae intg/src/main/java/org/apache/atlas/security/SecurityProperties.java 2147cd17c intg/src/main/java/org/apache/atlas/security/SecurityUtil.java 082c6378c Diff: https://reviews.apache.org/r/73151/diff/2/ Changes: https://reviews.apache.org/r/73151/diff/1-2/ Testing --- Tested on normal cluster with password stored in jceks file and TLS cluster with password stored in jceks file in Atlas. Thanks, Nixon Rodrigues
