You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/ingestion/src/ingestionClient.ts
+60-2Lines changed: 60 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -97,6 +97,7 @@ import type {
97
97
ListTasksProps,
98
98
ListTasksV1Props,
99
99
ListTransformationsProps,
100
+
PushProps,
100
101
PushTaskProps,
101
102
RunSourceProps,
102
103
RunTaskProps,
@@ -1706,15 +1707,72 @@ export function createIngestionClient({
1706
1707
},
1707
1708
1708
1709
/**
1709
-
* Push a `batch` request payload through the Pipeline. You can check the status of task pushes with the observability endpoints.
1710
+
* Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the [pre-indexing data transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/), this is the recommended way of ingesting your records. This method is similar to `pushTask`, but requires an `indexName` instead of a `taskID`. If zero or many tasks are found, an error will be returned.
1711
+
*
1712
+
* Required API Key ACLs:
1713
+
* - addObject
1714
+
* - deleteIndex
1715
+
* - editSettings
1716
+
* @param push - The push object.
1717
+
* @param push.indexName - Name of the index on which to perform the operation.
1718
+
* @param push.pushTaskPayload - The pushTaskPayload object.
1719
+
* @param push.watch - When provided, the push operation will be synchronous and the API will wait for the ingestion to be finished before responding.
1720
+
* @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions.
* Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the [pre-indexing data transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/), this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.
1710
1768
*
1711
1769
* Required API Key ACLs:
1712
1770
* - addObject
1713
1771
* - deleteIndex
1714
1772
* - editSettings
1715
1773
* @param pushTask - The pushTask object.
1716
1774
* @param pushTask.taskID - Unique identifier of a task.
1717
-
* @param pushTask.pushTaskPayload - Request body of a Search API `batch` request that will be pushed in the Connectors pipeline.
1775
+
* @param pushTask.pushTaskPayload - The pushTaskPayload object.
1718
1776
* @param pushTask.watch - When provided, the push operation will be synchronous and the API will wait for the ingestion to be finished before responding.
1719
1777
* @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions.
0 commit comments