You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2022/09/28 23:03:00 UTC
[jira] [Updated] (NIFI-10560) Exclude Elasticsearch and Solr Auto Configuration from Registry
[ https://issues.apache.org/jira/browse/NIFI-10560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Handermann updated NIFI-10560:
------------------------------------
Status: Patch Available (was: Open)
> Exclude Elasticsearch and Solr Auto Configuration from Registry
> ---------------------------------------------------------------
>
> Key: NIFI-10560
> URL: https://issues.apache.org/jira/browse/NIFI-10560
> Project: Apache NiFi
> Issue Type: Improvement
> Components: NiFi Registry
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Fix For: 1.18.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The NiFi Registry web application uses Spring Boot to load a number of standard configuration objects. The default behavior attempts to configure a Solr Client and an Elasticsearch Client when the corresponding client libraries are on the class path. Although these libraries are not present in that standard NiFi Registry build, the {{include-ranger}} build profile incorporates these libraries as transitive dependencies.
> The Spring Boot configuration for NiFi Registry should be updated to exclude these configuration classes to avoid unexpected runtime behavior when including the Apache Ranger plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)