Camel
  1. Camel
  2. CAMEL-2830

camel-bindy - Add option to allow bindy to collect failed mapping so end users can decide what to do

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.3.0
    • Fix Version/s: Future
    • Component/s: camel-bindy
    • Labels:
      None

      Description

      Suppose you are processing a big file with many CSV rows.
      And you map those using bindy to objects. Now some of the CSV rows is invalid, which would cause Bindy to thrown an exception.

      We should add an option so end user can suppress this and let bindy continue and collect those failed rows.
      Then those rows could be set as a header on the message.

      You may need some container object to store the validation errors, or offer a interface for callbacks when a validation error was found.
      For example like the org.xml.sax.ErrorHandler interface which is callback based.

        Activity

        Hide
        Charles Moulliard added a comment -

        That means that we should create a specific error for that case to avoid that IllegalArgumentException (used for the moment) or FormatNumberException will be by passed.

        Show
        Charles Moulliard added a comment - That means that we should create a specific error for that case to avoid that IllegalArgumentException (used for the moment) or FormatNumberException will be by passed.
        Show
        Claus Ibsen added a comment - See nabble http://camel.465427.n5.nabble.com/Bindy-CsvRecord-handling-bad-records-on-batch-processing-tp473119p473119.html

          People

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

            Dates

            • Created:
              Updated:

              Development