You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (Jira)" <ji...@apache.org> on 2019/09/30 14:29:00 UTC
[jira] [Created] (CAMEL-14021) HDFS Polling consumer returns
incorrect count of processed messages
James Netherton created CAMEL-14021:
---------------------------------------
Summary: HDFS Polling consumer returns incorrect count of processed messages
Key: CAMEL-14021
URL: https://issues.apache.org/jira/browse/CAMEL-14021
Project: Camel
Issue Type: Improvement
Components: camel-hdfs
Affects Versions: 3.x, 3.0.0.RC2
Reporter: James Netherton
Assignee: James Netherton
Fix For: 3.x, 3.0.0.RC2
Slight problem encountered with the recent hdfs component refactoring.
hasMatchingOwner used as a filter in this lambda expression always returns false and hence the count of polled messages is always 0. It's simple to reproduce by running HdfsConsumerTest.
I think the revised implementation of [hasMatchingOwner|https://github.com/apache/camel/blob/master/components/camel-hdfs/src/main/java/org/apache/camel/component/hdfs/HdfsConsumer.java#L190-L198] is wrong. It should return false when the owner does not match. I think that's more in line with the [previous implementation|https://github.com/apache/camel/blob/camel-3.0.0-RC1/components/camel-hdfs/src/main/java/org/apache/camel/component/hdfs/HdfsConsumer.java#L128-L136].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)