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: Sources/Ingestion/IngestionClient.swift
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -2665,11 +2665,11 @@ open class IngestionClient {
2665
2665
return body
2666
2666
}
2667
2667
2668
-
// Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the
2669
-
// `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to
2670
-
// 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/),
2671
-
// this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID`
2672
-
// instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.
2668
+
// Pushes records through the pipeline, directly to an index. You can make the call synchronous by providing the
2669
+
// `watch` parameter, for asynchronous calls, you can use the observability endpoints or the debugger dashboard to
2670
+
// see the status of your task. If you want to transform your data before indexing, this is the recommended way of
2671
+
// ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which
2672
+
// is useful when many `destinations` target the same `indexName`.
0 commit comments