[
https://issues.apache.org/jira/browse/NIFI-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kell updated NIFI-2179:
---------------------------------
Description:
ExecuteSQL Processor is broken, it is not possible to assignt a neccesary
controllerservice connection.
I created a working SQL Controller , it is not possible to assignt this
controller to created ExecuteSQL Processor , even if i create one
controllerservice out of property page , it is not possible for the processor
to use this service.
It has probably nothing to do with changes in processor code ... it has
probably spomething to do with controller service ... i just tested it with
0.5.0 and it works ... it is broken since 0.5.1
was:
ExecuteSQL Processor is broken, it is not possible to assignt a neccesary
controllerservice connection.
I created a working SQL Controller , it is not possible to assignt this
controller to created ExecuteSQL Processor , even if i create one
controllerservice out of property page , it is not possible for the processor
to use this service.
> ExecuteSQL and PutSQL can't assignt controller service
> ------------------------------------------------------
>
> Key: NIFI-2179
> URL: https://issues.apache.org/jira/browse/NIFI-2179
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.5.1, 0.6.1
> Environment: Windows 7 , Linux Red Hat Enterprise
> Reporter: Alexander Kell
> Priority: Critical
> Labels: ControllerService, SQL
> Attachments: Wrong_controllerservicetype.png
>
>
> ExecuteSQL Processor is broken, it is not possible to assignt a neccesary
> controllerservice connection.
> I created a working SQL Controller , it is not possible to assignt this
> controller to created ExecuteSQL Processor , even if i create one
> controllerservice out of property page , it is not possible for the processor
> to use this service.
> It has probably nothing to do with changes in processor code ... it has
> probably spomething to do with controller service ... i just tested it with
> 0.5.0 and it works ... it is broken since 0.5.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
