Re: Please add me to the Atlas project
Paresh, Thank you for your interest in contributing to Apache Atlas. You now have contributor access in Apache Atlas. Welcome to Apache Atlas. Thanks, Madhan for the Apache Atlas PMC From: Paresh Devalia Date: Tuesday, November 9, 2021 at 8:52 PM To: Madhan Neethiraj Subject: Re: Please add me to the Atlas project Dear Madhan, As requested by you, PFB details for adding Atlas project Userid :- pareshD On Mon, 1 Nov 2021, 8:15 pm Madhan Neethiraj, wrote: Paresh, Thank you for your interest in contributing to Apache Atlas. Can you please create a JIRA account at https://issues.apache.org/jira and send your ID? Thanks, Madhan On 11/1/21, 7:41 AM, "Paresh Devalia" wrote: Hi Team, I would like to contribute to the Atlas project, Can you please add me as contributor. Thanks, Paresh Devalia
Review Request 73700: ATLAS-4473 Glossary Terms Bulk Create Performance Improvement
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73700/ --- Review request for atlas, Ashutosh Mestry, Jayendra Parab, Pinal Shah, and Sarath Subramanian. Bugs: ATLAS-4473 https://issues.apache.org/jira/browse/ATLAS-4473 Repository: atlas Description --- While creating GlossaryTerms we need information about Glossary and GlossaryCategory (if present) As per current design, When every Term is created, respective Glossary and Category objects are fetched from db and they are populated with unwanted information. In case of bulk creation, Even if multiple Terms have same Glossary and Category associated with them, every time these objects are fetched from db and they are populated. This patch stores the optimum information of Glossaries and Categoies in the cache against their respective Guids. This helps in performance improvement of Bulk Term Creation. Diffs - repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java 9c8459874 repository/src/main/java/org/apache/atlas/glossary/GlossaryTermUtils.java d92daeea5 Diff: https://reviews.apache.org/r/73700/diff/1/ Testing --- Earlier, it was taking more than a day to complete the creation process of the Terms. Now with the Performacne optimization, it is taking 5 to 6 minutes to complete. Thanks, Mandar Ambawane
[jira] [Comment Edited] (ATLAS-4246) Make Kafka Interface aware of Kafka Schema Registry
[ https://issues.apache.org/jira/browse/ATLAS-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441381#comment-17441381 ] Sidharth Kumar Mishra edited comment on ATLAS-4246 at 11/10/21, 1:24 AM: - Hi [~aileeen], Please add your email id, Commit Msg etc to the patch and upload again. I will merge once add these details. The header for patch should be like: From: Date: <> Subject: Recent successful CI build - https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/956/ Thanks cc: [~sarath] , [~amestry] was (Author: sidharthkmishra): Hi [~aileeen], Please add your email id, Commit Msg etc to the patch and upload again. I will merge once add these details. The header for patch should be like: From: Date: <> Subject: Thanks cc: [~sarath] , [~amestry] > Make Kafka Interface aware of Kafka Schema Registry > --- > > Key: ATLAS-4246 > URL: https://issues.apache.org/jira/browse/ATLAS-4246 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0, 3.0.0 >Reporter: Aileen Toleikis >Assignee: Viktor Somogyi-Vass >Priority: Major > Labels: Kafka > Fix For: 3.0.0, 2.3.0 > > > Kafka Community is using Schema Registry more and more heavily but as Atlas > is currently unaware of this, this extension helps Atlas make use of the > Schemas. > > We have tested this extension and we have production environments where Atlas > will not be allowed without schema registry access. We have received feedback > that this extension would be sufficient to allow production use. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4473) Glossary Terms Bulk Create Performance Improvement
Mandar Ambawane created ATLAS-4473: -- Summary: Glossary Terms Bulk Create Performance Improvement Key: ATLAS-4473 URL: https://issues.apache.org/jira/browse/ATLAS-4473 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane While creating GlossaryTerms we need information about Glossary and GlossaryCategory (if present) As per current design, When every Term is created, respective Glossary and Category objects are fetched from db and they are populated with unwanted information. In case of bulk creation, Even if multiple Terms have same Glossary and Category associated with them, every time these objects are fetched from db and they are populated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4246) Make Kafka Interface aware of Kafka Schema Registry
[ https://issues.apache.org/jira/browse/ATLAS-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441156#comment-17441156 ] Aileen Toleikis commented on ATLAS-4246: Hi [~amestry] [~sarath] [~sidharthkmishra] We added a new patch, where we hopefully solve the errors. Can you run your CI-build with the new bits again? Kind regards, Aileen > Make Kafka Interface aware of Kafka Schema Registry > --- > > Key: ATLAS-4246 > URL: https://issues.apache.org/jira/browse/ATLAS-4246 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0, 3.0.0 >Reporter: Aileen Toleikis >Assignee: Viktor Somogyi-Vass >Priority: Major > Labels: Kafka > Fix For: 3.0.0, 2.3.0 > > > Kafka Community is using Schema Registry more and more heavily but as Atlas > is currently unaware of this, this extension helps Atlas make use of the > Schemas. > > We have tested this extension and we have production environments where Atlas > will not be allowed without schema registry access. We have received feedback > that this extension would be sufficient to allow production use. -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: Review Request 73286: Initial commit
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73286/ --- (Updated Nov. 9, 2021, 1:02 nachm.) Review request for atlas. Changes --- SchemaRegistryConnector line 50: inserted try/catch for test Repository: atlas Description --- The Kafka Community is using Schema Registry more and more heavily but as Atlas is currently unaware of this, this extension helps Atlas make use of the Schemas. We have tested this extension and we have production environments where Atlas will not be allowed without schema registry access. We have received feedback that this extension would be sufficient to allow production use. Changes: initial commit added schema creation in Atlas added Schema creation, Schema linkage and started to work on versions avro_field creation is working. However, there is no connection to schemas yet smaller refactorings and improved logging added field reference in schemas deleted second README and added gitignore Smaller changes after rebasing on new version moved HTTP REST calls to a separate class (SchemaRegistryConnector.java) added testCreateSchema() as test case added testCreateField() and testUpdateField() as test case added testGetSchemas() and testGetSchemaVersions() as test case added testUpdateSchema() as test case removed unnecessary comments Diffs (updated) - addons/kafka-bridge/pom.xml 2ac19fd20e0c0322b0d104641ddd5a2ef89bf9d0 addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/bridge/KafkaBridge.java f9548244364a8f79f346411739348d0d53298c99 addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/bridge/SchemaRegistryConnector.java PRE-CREATION addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/model/KafkaDataTypes.java 0f81b4c37a1d8f84c587a914eb460b290ae36987 addons/kafka-bridge/src/test/java/org/apache/atlas/kafka/bridge/KafkaBridgeTest.java f86ceb58fd250d80f3ae3c71085c8c0adbc9116b pom.xml 47768e9fa7d8abcfc81cd148917400ac478a333a Diff: https://reviews.apache.org/r/73286/diff/5/ Changes: https://reviews.apache.org/r/73286/diff/4-5/ Testing --- Thanks, Aileen Toleikis
[jira] [Commented] (ATLAS-4246) Make Kafka Interface aware of Kafka Schema Registry
[ https://issues.apache.org/jira/browse/ATLAS-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441268#comment-17441268 ] Ashutosh Mestry commented on ATLAS-4246: Here's the new CI build: [https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/954/] Will proceed with commit if this succeeds. > Make Kafka Interface aware of Kafka Schema Registry > --- > > Key: ATLAS-4246 > URL: https://issues.apache.org/jira/browse/ATLAS-4246 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0, 3.0.0 >Reporter: Aileen Toleikis >Assignee: Viktor Somogyi-Vass >Priority: Major > Labels: Kafka > Fix For: 3.0.0, 2.3.0 > > > Kafka Community is using Schema Registry more and more heavily but as Atlas > is currently unaware of this, this extension helps Atlas make use of the > Schemas. > > We have tested this extension and we have production environments where Atlas > will not be allowed without schema registry access. We have received feedback > that this extension would be sufficient to allow production use. -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: Review Request 73637: ATLAS-4370: Persist Metrics for user to retrieve Metrics info at a past timestamp
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73637/ --- (Updated Nov. 9, 2021, 7:54 p.m.) Review request for atlas, Ashutosh Mestry, Radhika Kundam, Sarath Subramanian, and Sidharth Mishra. Bugs: ATLAS-4370 https://issues.apache.org/jira/browse/ATLAS-4370 Repository: atlas Description --- Rebased patch #73483 (https://reviews.apache.org/r/73483/) against the newest master branch. Diffs (updated) - addons/models/-Area0/0010-base_model.json 769d8859f intg/src/main/java/org/apache/atlas/AtlasConfiguration.java b63fab7cf intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 7d092616d intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMapToChart.java PRE-CREATION intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsStat.java PRE-CREATION intg/src/main/java/org/apache/atlas/utils/AtlasEntityUtil.java 1e78e2550 repository/src/main/java/org/apache/atlas/repository/ogm/metrics/AtlasMetricsStatDTO.java PRE-CREATION repository/src/main/java/org/apache/atlas/services/MetricsService.java ceb252822 repository/src/test/java/org/apache/atlas/TestModules.java 8dda20825 repository/src/test/java/org/apache/atlas/services/MetricsServiceTest.java 040592184 test-tools/src/main/resources/solr/core-template/solrconfig.xml 3341e7199 webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 0580f7f33 Diff: https://reviews.apache.org/r/73637/diff/6/ Changes: https://reviews.apache.org/r/73637/diff/5-6/ Testing --- 1) Tested locally. 2) Patched a cluster. PC build: https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/880/ Thanks, Disha Talreja
Re: Review Request 73637: ATLAS-4370: Persist Metrics for user to retrieve Metrics info at a past timestamp
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73637/#review223719 --- Ship it! Ship It! - Radhika Kundam On Nov. 9, 2021, 11:54 a.m., Disha Talreja wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/73637/ > --- > > (Updated Nov. 9, 2021, 11:54 a.m.) > > > Review request for atlas, Ashutosh Mestry, Radhika Kundam, Sarath > Subramanian, and Sidharth Mishra. > > > Bugs: ATLAS-4370 > https://issues.apache.org/jira/browse/ATLAS-4370 > > > Repository: atlas > > > Description > --- > > Rebased patch #73483 (https://reviews.apache.org/r/73483/) against the newest > master branch. > > > Diffs > - > > addons/models/-Area0/0010-base_model.json 769d8859f > intg/src/main/java/org/apache/atlas/AtlasConfiguration.java b63fab7cf > intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 7d092616d > > intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMapToChart.java > PRE-CREATION > intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsStat.java > PRE-CREATION > intg/src/main/java/org/apache/atlas/utils/AtlasEntityUtil.java 1e78e2550 > > repository/src/main/java/org/apache/atlas/repository/ogm/metrics/AtlasMetricsStatDTO.java > PRE-CREATION > repository/src/main/java/org/apache/atlas/services/MetricsService.java > ceb252822 > repository/src/test/java/org/apache/atlas/TestModules.java 8dda20825 > repository/src/test/java/org/apache/atlas/services/MetricsServiceTest.java > 040592184 > test-tools/src/main/resources/solr/core-template/solrconfig.xml 3341e7199 > webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java > 0580f7f33 > > > Diff: https://reviews.apache.org/r/73637/diff/6/ > > > Testing > --- > > 1) Tested locally. > 2) Patched a cluster. > > PC build: > https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/880/ > > > Thanks, > > Disha Talreja > >
Re: Review Request 73286: Initial commit
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73286/#review223720 --- Ship it! Ship It! - Sidharth Mishra On Nov. 9, 2021, 1:02 p.m., Aileen Toleikis wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/73286/ > --- > > (Updated Nov. 9, 2021, 1:02 p.m.) > > > Review request for atlas. > > > Repository: atlas > > > Description > --- > > The Kafka Community is using Schema Registry more and more heavily but as > Atlas is currently unaware of this, this extension helps Atlas make use of > the Schemas. > > We have tested this extension and we have production environments where Atlas > will not be allowed without schema registry access. We have received feedback > that this extension would be sufficient to allow production use. > > Changes: > > initial commit > > > added schema creation in Atlas > > > added Schema creation, Schema linkage and started to work on versions > > > avro_field creation is working. However, there is no connection to schemas yet > > > smaller refactorings and improved logging > > > added field reference in schemas > > > deleted second README and added gitignore > > > Smaller changes after rebasing on new version > > > moved HTTP REST calls to a separate class (SchemaRegistryConnector.java) > > > added testCreateSchema() as test case > > > added testCreateField() and testUpdateField() as test case > > > added testGetSchemas() and testGetSchemaVersions() as test case > > > added testUpdateSchema() as test case > > > removed unnecessary comments > > > Diffs > - > > addons/kafka-bridge/pom.xml 2ac19fd20e0c0322b0d104641ddd5a2ef89bf9d0 > > addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/bridge/KafkaBridge.java > f9548244364a8f79f346411739348d0d53298c99 > > addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/bridge/SchemaRegistryConnector.java > PRE-CREATION > > addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/model/KafkaDataTypes.java > 0f81b4c37a1d8f84c587a914eb460b290ae36987 > > addons/kafka-bridge/src/test/java/org/apache/atlas/kafka/bridge/KafkaBridgeTest.java > f86ceb58fd250d80f3ae3c71085c8c0adbc9116b > pom.xml 47768e9fa7d8abcfc81cd148917400ac478a333a > > > Diff: https://reviews.apache.org/r/73286/diff/5/ > > > Testing > --- > > > Thanks, > > Aileen Toleikis > >
[jira] [Commented] (ATLAS-4470) Creating Hive_Process entity is getting failed due to null startTime
[ https://issues.apache.org/jira/browse/ATLAS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441357#comment-17441357 ] ASF subversion and git services commented on ATLAS-4470: Commit e4cfb57d4324079af51c488cae28353689a25f1b in atlas's branch refs/heads/branch-2.0 from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e4cfb57 ] ATLAS-4470: Creating Hive_Process entity is getting failed due to empty/null startTime Signed-off-by: Sidharth Mishra (cherry picked from commit 10a7c76c8e07a60c65109391e76970714f2122e2) > Creating Hive_Process entity is getting failed due to null startTime > > > Key: ATLAS-4470 > URL: https://issues.apache.org/jira/browse/ATLAS-4470 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > > tIn few scenarios of creation Hive_process entity is failed with below error > and this is expected because startTime is mandatory attribute for > hive_process entity. This issue is mainly because Hive is not sending > startTime in few scenarios and since this issue is inconsistent and not sure > of the pattern when Hive is sending empty startTime. > While processing Hive context Atlas initially assign currentTimeStamp to > startTime and then further it proceeds to get startTime from Hive Context and > if that value is empty the mentioned issue is occurring. So to avoid that we > can have extra check at Atlas to consider StartTime from Hive Context only if > it's not empty. > 2021-10-13 14:40:00,503 ERROR - [NotificationHookConsumer thread-0:] ~ graph > rollback due to exception AtlasBaseException:Invalid instance > creation/updation parameters passed : hive_process.startTime: mandatory > attribute value missing in type hive_process > (GraphTransactionInterceptor:169)2021-10-13 14:40:00,504 WARN - > [NotificationHookConsumer thread-0:] ~ Error handling message > (NotificationHookConsumer:752)org.apache.atlas.exception.AtlasBaseException: > Invalid instance creation/updation parameters passed : > hive_process.startTime: mandatory attribute value missing in type > hive_process at > org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.validateAndNormalize(AtlasEntityGraphDiscoveryV2.java:97) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.preCreateOrUpdate(AtlasEntityStoreV2.java:899) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:744) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:275) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > at > org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) > at > org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) > at > org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$ff9731b1.createOrUpdate() > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.createOrUpdate(NotificationHookConsumer.java:822) > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:671) > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.doWork(NotificationHookConsumer.java:524) > at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:82) > at -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4470) Creating Hive_Process entity is getting failed due to null startTime
[ https://issues.apache.org/jira/browse/ATLAS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441356#comment-17441356 ] ASF subversion and git services commented on ATLAS-4470: Commit 10a7c76c8e07a60c65109391e76970714f2122e2 in atlas's branch refs/heads/master from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=10a7c76 ] ATLAS-4470: Creating Hive_Process entity is getting failed due to empty/null startTime Signed-off-by: Sidharth Mishra > Creating Hive_Process entity is getting failed due to null startTime > > > Key: ATLAS-4470 > URL: https://issues.apache.org/jira/browse/ATLAS-4470 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > > tIn few scenarios of creation Hive_process entity is failed with below error > and this is expected because startTime is mandatory attribute for > hive_process entity. This issue is mainly because Hive is not sending > startTime in few scenarios and since this issue is inconsistent and not sure > of the pattern when Hive is sending empty startTime. > While processing Hive context Atlas initially assign currentTimeStamp to > startTime and then further it proceeds to get startTime from Hive Context and > if that value is empty the mentioned issue is occurring. So to avoid that we > can have extra check at Atlas to consider StartTime from Hive Context only if > it's not empty. > 2021-10-13 14:40:00,503 ERROR - [NotificationHookConsumer thread-0:] ~ graph > rollback due to exception AtlasBaseException:Invalid instance > creation/updation parameters passed : hive_process.startTime: mandatory > attribute value missing in type hive_process > (GraphTransactionInterceptor:169)2021-10-13 14:40:00,504 WARN - > [NotificationHookConsumer thread-0:] ~ Error handling message > (NotificationHookConsumer:752)org.apache.atlas.exception.AtlasBaseException: > Invalid instance creation/updation parameters passed : > hive_process.startTime: mandatory attribute value missing in type > hive_process at > org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.validateAndNormalize(AtlasEntityGraphDiscoveryV2.java:97) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.preCreateOrUpdate(AtlasEntityStoreV2.java:899) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:744) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:275) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > at > org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) > at > org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) > at > org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671) > at > org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$ff9731b1.createOrUpdate() > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.createOrUpdate(NotificationHookConsumer.java:822) > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:671) > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.doWork(NotificationHookConsumer.java:524) > at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:82) > at -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4246) Make Kafka Interface aware of Kafka Schema Registry
[ https://issues.apache.org/jira/browse/ATLAS-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441381#comment-17441381 ] Sidharth Kumar Mishra commented on ATLAS-4246: -- Hi [~aileeen], Please add your email id, Commit Msg etc to the patch and upload again. I will merge once add these details. The header for patch should be like: From: Date: <> Subject: Thanks cc: [~sarath] , [~amestry] > Make Kafka Interface aware of Kafka Schema Registry > --- > > Key: ATLAS-4246 > URL: https://issues.apache.org/jira/browse/ATLAS-4246 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0, 3.0.0 >Reporter: Aileen Toleikis >Assignee: Viktor Somogyi-Vass >Priority: Major > Labels: Kafka > Fix For: 3.0.0, 2.3.0 > > > Kafka Community is using Schema Registry more and more heavily but as Atlas > is currently unaware of this, this extension helps Atlas make use of the > Schemas. > > We have tested this extension and we have production environments where Atlas > will not be allowed without schema registry access. We have received feedback > that this extension would be sufficient to allow production use. -- This message was sent by Atlassian Jira (v8.20.1#820001)
