Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

REST V2 source properties

REST V2 source properties

The following table describes the REST V2 source properties on the
Source
tab when you define a
streaming ingestion
task:
Property
Description
Connection
Name of the REST V2 source connection.
Connection Type
The REST V2 connection type.
The connection type populates automatically based on the connection that you select.
REST Endpoints
List of REST endpoints specified in the input swagger file.
These endpoints appear based on the chosen REST connection.
Scheme
List of schemes specified in the swagger definition.
The selected scheme is used to create a the URL.
Poll Interval
Interval between two consecutive REST calls.
Default is 10 seconds.
Action on Unsuccessful Response codes
Action required for unsuccessful REST calls.
You can choose of the following actions:
  • Raise Alert
  • Route to Downstream. Route the response to the downstream processors.
  • Route to Reject Directory: Route the response to the reject directory configured in Runtime Options page.
Based on the defined operation ID in the selected
REST Endpoints
property, the dynamic properties such as,
Path
,
Query
, and
Payload
appear at the lower section of the REST V2 source page.
  • Headers
    . Adds header to a REST call.
  • Path
    . Consists of multiple path parameters as specified in swagger definition. You cannot edit the
    Path Key
    . You can only enter corresponding values for the path keys.
  • Query
    . Consists of query parameters. Query parameters are similar to path parameters.
  • Payload
    .
    • Sample Payload
      . A read-only text box that shows schema of request body for a PUT, POST, or PATCH request. For example,
      { "name" : "string", "salary" : "string", "age" : "string" }
      .
    • Body
      . The request body to be sent incase of PUT, POST, or PATCH request. You can copy a sample request body from a sample payload and then can replace the values as appropriate.
You can define any of these properties as mandatory in the swagger specification file. Then the same property is considered mandatory while configuring a
streaming ingestion
REST V2 source. If you do not define a REST endpoint in the swagger specification file, the corresponding section does not appear in the
streaming ingestion
REST V2 page.

0 COMMENTS

We’d like to hear from you!