You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Ferenc Gerlits (Jira)" <ji...@apache.org> on 2022/04/21 13:34:00 UTC
[jira] [Assigned] (MINIFICPP-1803) Stop instantiating all classes on the first heartbeat
[ https://issues.apache.org/jira/browse/MINIFICPP-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ferenc Gerlits reassigned MINIFICPP-1803:
-----------------------------------------
Assignee: Ferenc Gerlits
> Stop instantiating all classes on the first heartbeat
> -----------------------------------------------------
>
> Key: MINIFICPP-1803
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1803
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Affects Versions: 0.6.0, 0.9.0, 0.7.0, 0.10.0, 0.11.0
> Reporter: Marton Szasz
> Assignee: Ferenc Gerlits
> Priority: Major
> Labels: MiNiFi-CPP-Hygiene
>
> When producing the first heartbeat, BuildDescription::getClassDescriptions instantiates *every single class* of each loader. In the case of AWS, the processors happen to derive from S3Processor, and they contain a data member of type Aws::Client::ClientConfiguration, whose default constructor makes HTTP calls to AWS.
> The easy fix is to delay the initialization of this particular member to onSchedule.
> The proper fix is to change the class loading and class description generation logic to store more metadata about classes that are collected at registration time, using compile-time introspection, instead of instantiating the classes and using dynamic_cast.
> This issue is about the proper fix. For the easy fix, see MINIFICPP-1802.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)