Get the Routing Object Between Two Nodes

get

/v1/nodes/{srcNodeId}/route/{destNodeId}

Returns the routing object between two specific nodes.

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

The routing object has been returned successfully.
Body ()
Root Schema : RouteResponse
Type: object
The response schema to get a route's information.
Show Source
Nested Schema : routingAttrs
Match All
The attributes against which routing fields are compared using various operations.
Show Source
  • RoutingAttributes
    The schema defining routing attributes for a route.
  • The attributes against which routing fields are compared using various operations.
Nested Schema : routingFunction
Match All
The routing function used for the channel.
Show Source
  • Allowed Values: [ "DIRECTED", "MODULUS", "MULTICAST", "ROUND_ROBIN" ]
  • The routing function used for the channel.
    Example: DIRECTED
Nested Schema : RoutingAttributes
Type: object
The schema defining routing attributes for a route.
Show Source
Nested Schema : operand1
Type: array
The values against which the operator acts on the routing field.
Show Source
Nested Schema : operand2
Type: array
The values against which operator acts on the routing field, two operands are required when an operator is used which requires 3 variables. For example, IN_BETWEEN operator.
Show Source
Nested Schema : operator
Match All
The expression representing action to be performed on routing field.
Show Source
  • Allowed Values: [ "EQUALS", "GREATER_THAN", "IN_BETWEEN", "LESS_THAN", "LIST_EQUALS", "LIST_NOT_EQUALS", "NOT_EQUALS", "NOT_SUBSET_OF", "SUBSET_OF" ]
  • The expression representing action to be performed on routing field.
    Example: EQUALS

400 Response

The request cannot be processed due to a client error.
Body ()
Root Schema : Error
Type: object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source

401 Response

The client does not have the corrrect privileges.
Body ()
Root Schema : Error
Type: object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source

403 Response

The request was not authorized.
Body ()
Root Schema : Error
Type: object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source

404 Response

The requested resource cannot be found.
Body ()
Root Schema : Error
Type: object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source

405 Response

This method is not allowed.
Body ()
Root Schema : Error
Type: object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source

409 Response

The request cannot be processed due to a conflict in the existing state of the resource.
Body ()
Root Schema : Error
Type: object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source

500 Response

The system has encountered an internal server error.
Body ()
Root Schema : Error
Type: object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source
Back to Top

Examples

The following example shows how to get the routing object between a source node and a destination node by submitting a GET request on the REST resource using cURL. For more information about cURL, see Use cURL.

curl -X GET 'http://hostname:port/nodes/31eoef-otm-lna51qht/route/31eoef-otm-lna53s09'

Example of the Response Body

If successful, the response code 200 is returned with the following response body.

{
  "destinationNodeID": "31eoef-otm-lna53s09",
  "routingAttrs": {
    "operand1": [
      ""
    ],
    "operand2": [
      ""
    ]
  },
  "routingField": "",
  "routingFunction": "MULTICAST",
  "sourceNodeID": "31eoef-otm-lna51qht"
}
Back to Top