[
https://issues.apache.org/jira/browse/NIFI-10560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610747#comment-17610747
]
ASF subversion and git services commented on NIFI-10560:
--------------------------------------------------------
Commit 0dec6bfbe13cabca1bdfc8fddec06d0a264dc29b in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0dec6bfbe1 ]
NIFI-10560 This closes #6459. Excluded Elasticsearch and Solr Auto
Configuration from Registry
- Excluding these configurations avoids unexpected runtime behavior when
running Registry with the Apache Ranger plugin
Signed-off-by: Joe Witt <[email protected]>
> 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)
