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
// Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the
2576
+
// `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to
2577
+
// 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/),
2578
+
// this is the recommended way of ingesting your records. This method is similar to `pushTask`, but requires an
2579
+
// `indexName` instead of a `taskID`. If zero or many tasks are found, an error will be returned.
2580
+
// Required API Key ACLs:
2581
+
// - addObject
2582
+
// - deleteIndex
2583
+
// - editSettings
2584
+
//
2585
+
// - parameter indexName: (path) Name of the index on which to perform the operation.
2586
+
//
2587
+
// - parameter pushTaskPayload: (body)
2588
+
//
2589
+
// - parameter watch: (query) When provided, the push operation will be synchronous and the API will wait for the
2590
+
// ingestion to be finished before responding. (optional)
/// - parameter taskID: (path) Unique identifier of a task.
2550
-
/// - parameter pushTaskPayload: (body) Request body of a Search API `batch` request that will be pushed in the
2551
-
/// Connectors pipeline.
2636
+
/// - parameter pushTaskPayload: (body)
2552
2637
/// - parameter watch: (query) When provided, the push operation will be synchronous and the API will wait for the
2553
2638
/// ingestion to be finished before responding. (optional)
2554
2639
/// - returns: WatchResponse
@@ -2573,17 +2658,19 @@ open class IngestionClient {
2573
2658
return body
2574
2659
}
2575
2660
2576
-
// Push a `batch` request payload through the Pipeline. You can check the status of task pushes with the
2577
-
// observability endpoints.
2661
+
// Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the
2662
+
// `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to
2663
+
// 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/),
2664
+
// this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID`
2665
+
// instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.
2578
2666
// Required API Key ACLs:
2579
2667
// - addObject
2580
2668
// - deleteIndex
2581
2669
// - editSettings
2582
2670
//
2583
2671
// - parameter taskID: (path) Unique identifier of a task.
2584
2672
//
2585
-
// - parameter pushTaskPayload: (body) Request body of a Search API `batch` request that will be pushed in the
2586
-
// Connectors pipeline.
2673
+
// - parameter pushTaskPayload: (body)
2587
2674
//
2588
2675
// - parameter watch: (query) When provided, the push operation will be synchronous and the API will wait for the
2589
2676
// ingestion to be finished before responding. (optional)
0 commit comments