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: src/protocols/faq.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,6 +162,40 @@ Blocking events within a [Source Schema](/docs/connections/sources/schema/) or [
162
162
163
163
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.
164
164
165
+
### I've blocked events in my Schema Configuration why are they not showing up as blocked in my Source Schema?
166
+
Within your [Schema Configuration](https://segment.com/docs/protocols/enforce/schema-configuration/) you'll notice there are two columns next to the Event Name titled Allowed and Blocked. If you've selected Omit Properties under Unplanned Properties/Traits then the Source Schema will only show a property as block if it is present when the whole event is blocked. This setting will only be enforced if the property is an unplanned name but not an unplanned value.
167
+
168
+
In order to show a blocked value for an property/trait within your Source Schema, you'll need to trigger a violaiton which can only be done using JSON Schema. Once you enforce your Schema Configuration to Omit Properties this will show as blocked.
0 commit comments