Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-14021

HDFS Polling consumer returns incorrect count of processed messages

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 3.0.0.RC2, 3.x
    • 3.0.0.RC2, 3.x
    • camel-hdfs
    • None
    • Unknown

    Description

      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 is wrong. It should return false when the owner does not match. I think that's more in line with the previous implementation.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jamesnetherton James Netherton
            jamesnetherton James Netherton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 20m
                20m

                Slack

                  Issue deployment