[
https://issues.apache.org/jira/browse/NIFI-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307825#comment-17307825
]
ASF subversion and git services commented on NIFI-8296:
-------------------------------------------------------
Commit 057b4af48249b8c22f4f914aac4c7ac4c3f5693c in nifi's branch
refs/heads/main from Dmitry Ibragimov
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=057b4af ]
NIFI-8296 - Use API to retrieve all subjects associated with a schema id for
Confluent Schema Registry v5.4.0+
Signed-off-by: Pierre Villard <[email protected]>
This closes #4872.
> Integration with API to retrieve all subjects associated with a schema id for
> Confluent Schema Registry v5.3.1+
> ---------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-8296
> URL: https://issues.apache.org/jira/browse/NIFI-8296
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Dmitry Ibragimov
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Confluent schema registry version 5.3.1+ implements new API for retrieve
> schema name by id:
> [https://github.com/confluentinc/schema-registry/pull/1196]
> Currently NiFi loops over all schemas registered in registry. For registries
> with big count of schemas it can be so long.
> [https://github.com/apache/nifi/blob/e2e137fced39f184e5998f7c4befe03e70f53016/nifi-nar-bundles/nifi-confluent-platform-bundle/nifi-confluent-schema-registry-service/src/main/java/org/apache/nifi/confluent/schemaregistry/client/RestSchemaRegistryClient.java#L111|https://github.com/apache/nifi/blob/ff93ec42c3730f1ba8acc4843e8504f2ff47a5cf/nifi-nar-bundles/nifi-confluent-platform-bundle/nifi-confluent-schema-registry-service/src/main/java/org/apache/nifi/confluent/schemaregistry/client/RestSchemaRegistryClient.java#L111]
> Need to implement this feature - it will gave us a huge increase of
> performance for consuming using registry with large amount of schemas.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
