<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: async call using InvokeHTTP in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/async-call-using-InvokeHTTP/m-p/321349#M228364</link>
    <description>&lt;P&gt;It seems that you were able to split the problem in the two key steps:&lt;/P&gt;&lt;P&gt;1. Define the attribute&lt;/P&gt;&lt;P&gt;2. Route on the attribute&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First question: Is defining the attribute succesful? Please check your message in the queue directly after doing this evaluatejsonpath. Look carefully (not sure if it is case sensitive/what it does with quotes).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Second question: Are you able to make any attribute based routing work? Perhaps just try some things till anything works and see what the difference is with your flow. The only thing I could think of are trivial points such as case sentivity (maybe), or extra quotes/spaces. You may try something even simpler like route if it contains the letter c, for your first test.&lt;/P&gt;</description>
    <pubDate>Thu, 22 Jul 2021 14:43:49 GMT</pubDate>
    <dc:creator>DennisJaheruddi</dc:creator>
    <dc:date>2021-07-22T14:43:49Z</dc:date>
  </channel>
</rss>

