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

Splitter - Should skip null messages if iterator returns null

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.16.2
    • Fix Version/s: 2.16.3, 2.17.1, 2.18.0
    • Component/s: camel-core
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      When splitting and using an iterator the usually hasNext -> next is paired so if hasNext returns true, then next returns data. But there can be situations where this is tricky to determine up front, and therefore a hasNext may return true, and then next() return null if there was no data really. Then the splitter should just skip that null and continue.

        Attachments

          Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. CAMEL-9735 camel-tarfile throws OutOfMemoryError when splitting large files

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CAMEL-9375 camel-tarfile - TarSplitter includes one extra empty entry at the end

          • Major - Major loss of function.
          • Resolved

            Activity

              People

              • Assignee:
                davsclaus Claus Ibsen
                Reporter:
                davsclaus Claus Ibsen
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: