Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitf71505f

Browse files
Commit suggestion from code review
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
1 parent4308fd1 commitf71505f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎src/connections/functions/insert-functions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -247,7 +247,7 @@ Consider creating a batch handler if:
247247

248248
-**You have a high-throughput function and want to reduce cost.** When you define a batch handler, Segment invokes the function once per*batch*, rather than once per event. As long as the function’s execution time isn’t adversely affected, the reduction in invocations should lead to a reduction in cost.
249249

250-
-**Your destination supports batching**. When your downstream destination supports sending data downstream in batches you can define a batch handler to avoid throttling. Batching for functions is independent of batch size supported by the destination. Segment automatically handles batch formation for destinations internally.
250+
-**Your destination supports batching**. When your downstream destination supports sending data downstream in batches you can define a batch handler to avoid throttling. Batching for functions is independent of batch size supported by the destination. Segment automatically handles batch formation for destinations.
251251

252252
>info ""
253253
>If a batched function receives too low a volume of events (under one event per second) to be worth batching, Segment may not invoke the batch handler.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp