Skip to content

Add FAQ on blocking forwarded blocked events #7367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 8, 2025
Merged

Add FAQ on blocking forwarded blocked events #7367

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
50e2972
Add FAQ on blocking forwarded blocked events
ashton-huxtable Dec 30, 2024
d0714b3
Apply suggestions from code review
forstisabella Jan 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions src/protocols/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,6 +177,10 @@ Blocking events within a [Source Schema](/docs/connections/sources/schema/) or [

Warehouse connectors don't use data type definitions for schema creation. The [data types](/docs/connections/storage/warehouses/schema/#data-types) for columns are inferred from the first event that comes in from the source.

### Can I use schema controls to block events that have been blocked from another source and forwarded to a new one?

Schema controls can only be used to block events as they are ingested into Segment. When you forward a blocked event from another source, that event has already been ingested into Segment. Thus, as it enters the second source, it bypasses the pipeline that would be used to block the event a second time.

## Protocols Transformations

### Do transformations work with Segment replays?
Expand Down