IS-17798: Added support for the parse_response_as operations property

hub/changelog.rst

@@ -8,6 +8,12 @@ Changelog
 * Extended Integrated Search to allow using a well-defined :ref:`query syntax <integrated_search_query_syntax>`. Improvements have been made to the search results for namespaced identifiers that have been merged. They now have the same query result page.
 * Added the ``trigger_on`` property to the :ref:`http transform <http_transform>`.
 
+.. _changelog_2024_09_17:
+
+2024-09-17
+----------
+* Added support for the ``parse_response_as`` property to the :ref:`operation properties <rest_operations>`. It can be specified in the ``operations`` property of both the :ref:`REST systems <rest_system>` and the :ref:`REST transform <rest_transform>`. It is not supported by the :ref:`REST source <rest_source>` or :ref:`REST sink <rest_sink>`.
+
 .. _changelog_2024_05_21:
 
 2024-05-21

hub/documentation/service-configuration/systems/configuration-systems-rest.rst

@@ -259,6 +259,18 @@ A operation configuration looks like:
      -
      -
 
+   * - ``parse_response_as``
+     - Enum<String>
+     - This property controls how the response body is parsed on the client-side. Allowed values are ``entities``, ``json``, ``text`` and ``bytes``.
+
+       - ``entities`` is the default and parses the response body as a stream of entities, i.e. JSON objects and arrays of JSON objects.
+       - ``json`` parses the response body as any JSON object including primitive types like numbers and strings.
+       - ``text`` parses the response body as a UTF-8 encoded string.
+       - ``bytes`` parses the response body as bytes.
+
+     - ``entities``
+     -
+
    * - ``response_property``
      - String
      - The name of the property to put the response in when emitting entities. Note that this property can be defined