[
https://issues.apache.org/jira/browse/NIFI-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-7459:
---------------------------------
Resolution: Feedback Received
Status: Resolved (was: Patch Available)
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> confluent schema registry controller service wont initialize in stateless
> runtime
> ---------------------------------------------------------------------------------
>
> Key: NIFI-7459
> URL: https://issues.apache.org/jira/browse/NIFI-7459
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Stateless
> Affects Versions: 1.12.0, 1.11.4
> Environment: Docker container created using
> nifi-docker/dockermaven-stateless on an 1.11.4 codebase with
> https://github.com/apache/nifi/pull/4264 (NIFI-7380)
> This patch is necessary to work around an issue with controller services not
> initializing in the stateless runtime. The reproducer has 2 controller
> services.
> Reporter: Mark Weghorst
> Assignee: Mark Weghorst
> Priority: Minor
> Labels: patch, pull-request-available
> Attachments: confluent-reproducer.xml,
> nifi-7380-confluent-schema-registry-exception.txt, nifi-7459.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The ConfluentSchemaRegistry controller service will not initialize in the
> stateless runtime but works correctly in the server runtime. I've attached a
> template for a flow that reproduces this problem, and the exception generated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
