[
https://issues.apache.org/jira/browse/NIFI-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15015644#comment-15015644
]
Joseph Witt commented on NIFI-1192:
-----------------------------------
I think we've learned that having connection pools or sources available as
controller services is generally a good thing. It is an extra step though for
administrators to setup so perhaps it is an additional model we support rather
than an alternative approach. The issue here is say there are 45 properties
for Kafka. We dont' actually want to punt all of those to just seemingly
arbitrary key value pairs. We want to have them available as processor
properties. But not all of them. Just ones we know are of value.
That said we should update this such that the behavior is well defined. Such
as:
- Any dynamic properties are applied first
- Then any processor properties are applied which would override any dynamic
properties that map to the same kafka configuration key
The addition of the dynamic properties means we can now support configs we
didn't previously think would be that valuable.
[~ozhurakousky] Can you clarify the behavior of the patch for dynamic
properties relative to processor properties and if it is that dynamic
properties are set last please consider an updated patch.
Thanks
Joe
> Allow Get/PutKafka to honor dynamic properties
> ----------------------------------------------
>
> Key: NIFI-1192
> URL: https://issues.apache.org/jira/browse/NIFI-1192
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.3.0
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
> Priority: Critical
> Fix For: 0.4.0
>
>
> Currently Kafka does not honor dynamic properties which means aside from 8
> properties exposed none others could be set
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
