Forum Discussion

darshthakkar's avatar
darshthakkar
Valued Contributor
4 years ago
Solved

Understanding router snap's functionality

Hi Team, I wanted to understand more about Router snap as I was stuck routing data today. Let’s assume I’m reading a flat file with 100 records and the file has 3 columns, ID (can have duplicates),...
  • darshthakkar's avatar
    darshthakkar
    4 years ago

    Wanted to share the solution here. The query was right, no need to change the “Fetch-size” as well.
    The only thing that was missing was ’ ’ for the IDs that we were passing in the query. Thus, the query would look like -
    WHERE NAME IN (‘102345’, ‘1701’, ‘5604878’)

  • Supratim's avatar
    Supratim
    Contributor III
    4 years ago
    Copy LinkReport

    @rmedeiros Looks like it’s syntax issue (count not found). In your error pipeline you don’t need to explicitly map each and every attribute. Rather have one open/unlinked input view mapper and use pass through option. Just add one/two fields in mapper (name of error pipeline name/ execution time etc.) and use the pass through.
    If you don’t want to change your logic then select null safe option in your mapper in error pipeline.

    • rmedeiros's avatar
      rmedeiros
      New Contributor III
      4 years ago
      Copy LinkReport

      Well, i tried turning on the Null Safe and Pass Through options. But some pipelines kept throwing this error on the Error Pipeline. Despite throwing this error, the error pipeline is kind of working, it saves an error log and creates a ticket, as intended, but the error log is an empty JSON, with only the empty brackets. Seems like no error info is being sent to the error pipeline.

      • Supratim's avatar
        Supratim
        Contributor III
        4 years ago
        Copy LinkReport

        @rmedeiros Is it possible to share your error pipeline ? you can remove your endpoint details before sharing.