[ 
https://issues.apache.org/jira/browse/MINIFICPP-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gábor Gyimesi updated MINIFICPP-2295:
-------------------------------------
    Description: 
NiFi python processors support controller service properties, that can be 
retrieved using 
context.getProperty(<property>).asControllerService() and used in the 
processor. Although MiNiFi does not have all controller services that NiFi has, 
we should support the same syntax for the controllers that are available in 
MiNiFi C++ as well. At the moment SSLContextService seems to be the only 
controller that can be useful to be added and does not reside in one of the 
extensions.

  was:
NiFi python processors support controller service properties, that can be 
retrieved using 
context.getProperty(<property>).asControllerService() and used in the 
processor. Although MiNiFi does not have all controller services that NiFi has, 
we should support the same syntax for the controllers that are available in 
MiNiFi C++ as well.


> Add SSLContextService support for NiFi Python processors
> --------------------------------------------------------
>
>                 Key: MINIFICPP-2295
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-2295
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: New Feature
>            Reporter: Gábor Gyimesi
>            Assignee: Gábor Gyimesi
>            Priority: Minor
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> NiFi python processors support controller service properties, that can be 
> retrieved using 
> context.getProperty(<property>).asControllerService() and used in the 
> processor. Although MiNiFi does not have all controller services that NiFi 
> has, we should support the same syntax for the controllers that are available 
> in MiNiFi C++ as well. At the moment SSLContextService seems to be the only 
> controller that can be useful to be added and does not reside in one of the 
> extensions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to