[
https://issues.apache.org/jira/browse/NIFI-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436266#comment-15436266
]
Joseph Witt commented on NIFI-2608:
-----------------------------------
Have verified that the threads Kafka spawns are seeing the
NarThreadContextClasslaoder as the current context class loader of those
threads. As a result there is nothing for them to bind to in terms of a
specific NarClassloader. Looks like we know precisely which NarClassLoader we
should use when going to a given component so we can be far more precise. Need
to understand why we're not already doing this. But will run some experiments.
> Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients
> -----------------------------------------------------------------------
>
> Key: NIFI-2608
> URL: https://issues.apache.org/jira/browse/NIFI-2608
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Oleg Zhurakousky
> Assignee: Joseph Witt
> Priority: Critical
> Fix For: 1.0.0
>
>
> KafkaConsumer went fro thread-safe in 0.8 to not-thread-safe in 0.9 which was
> overlooked while implementing new ConsumeKafka processor which relied on 0.9
> Client API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
