Struct nakadi_types::event_type::EventTypeInputBuilder [−][src]
pub struct EventTypeInputBuilder {}Show fields
pub name: Option<EventTypeName>, pub owning_application: Option<OwningApplication>, pub category: Option<Category>, pub enrichment_strategies: Option<Vec<EnrichmentStrategy>>, pub partition_strategy: Option<PartitionStrategy>, pub partition_key_fields: Option<PartitionKeyFields>, pub compatibility_mode: Option<CompatibilityMode>, pub schema: Option<EventTypeSchemaInput>, pub cleanup_policy: Option<CleanupPolicy>, pub default_statistic: Option<EventTypeStatistics>, pub options: Option<EventTypeOptions>, pub authorization: Option<EventTypeAuthorization>, pub audience: Option<EventTypeAudience>,
Fields
name: Option<EventTypeName>
Name of this EventType. The name is constrained by a regular expression.
Note: the name can encode the owner/responsible for this EventType and ideally should follow a common pattern that makes it easy to read and understand, but this level of structure is not enforced. For example a team name and data type can be used such as ‘acme-team.price-change’.
owning_application: Option<OwningApplication>
Indicator of the application owning this EventType.
category: Option<Category>
Defines the category of this EventType.
The value set will influence, if not set otherwise, the default set of validations, enrichment-strategies, and the effective schema for validation.
enrichment_strategies: Option<Vec<EnrichmentStrategy>>
Determines the enrichment to be performed on an Event upon reception. Enrichment is performed once upon reception (and after validation) of an Event and is only possible on fields that are not defined on the incoming Event.
For event types in categories ‘business’ or ‘data’ it’s mandatory to use metadata_enrichment strategy. For ‘undefined’ event types it’s not possible to use this strategy, since metadata field is not required.
See documentation for the write operation for details on behaviour in case of unsuccessful enrichment.
partition_strategy: Option<PartitionStrategy>
Determines how the assignment of the event to a partition should be handled.
partition_key_fields: Option<PartitionKeyFields>
Required when ‘partition_resolution_strategy’ is set to ‘hash’. Must be absent otherwise. Indicates the fields used for evaluation the partition of Events of this type.
If this is set it MUST be a valid required field as defined in the schema.
compatibility_mode: Option<CompatibilityMode>
Compatibility mode provides a mean for event owners to evolve their schema, given changes respect the semantics defined by this field.
It’s designed to be flexible enough so that producers can evolve their schemas while not inadvertently breaking existent consumers.
Once defined, the compatibility mode is fixed, since otherwise it would break a predefined contract, declared by the producer.
schema: Option<EventTypeSchemaInput>
cleanup_policy: Option<CleanupPolicy>
Event type cleanup policy. There are two possible values:
default_statistic: Option<EventTypeStatistics>
options: Option<EventTypeOptions>
audience: Option<EventTypeAudience>
Implementations
Name of this EventType. The name is constrained by a regular expression.
Note: the name can encode the owner/responsible for this EventType and ideally should follow a common pattern that makes it easy to read and understand, but this level of structure is not enforced. For example a team name and data type can be used such as ‘acme-team.price-change’.
Indicator of the application owning this EventType.
Defines the category of this EventType.
The value set will influence, if not set otherwise, the default set of validations, enrichment-strategies, and the effective schema for validation.
Determines the enrichment to be performed on an Event upon reception. Enrichment is performed once upon reception (and after validation) of an Event and is only possible on fields that are not defined on the incoming Event.
For event types in categories ‘business’ or ‘data’ it’s mandatory to use metadata_enrichment strategy. For ‘undefined’ event types it’s not possible to use this strategy, since metadata field is not required.
See documentation for the write operation for details on behaviour in case of unsuccessful enrichment.
Determines how the assignment of the event to a partition should be handled.
Required when ‘partition_resolution_strategy’ is set to ‘hash’. Must be absent otherwise. Indicates the fields used for evaluation the partition of Events of this type.
If this is set it MUST be a valid required field as defined in the schema.
Compatibility mode provides a mean for event owners to evolve their schema, given changes respect the semantics defined by this field.
It’s designed to be flexible enough so that producers can evolve their schemas while not inadvertently breaking existent consumers.
Once defined, the compatibility mode is fixed, since otherwise it would break a predefined contract, declared by the producer.
Event type cleanup policy. There are two possible values:
Validates the data and returns an EventTypeInput
if valid.
Trait Implementations
Returns the “default value” for a type. Read more
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error> where
__D: Deserializer<'de>,
[src]
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error> where
__D: Deserializer<'de>,
[src]Deserialize this value from the given Serde deserializer. Read more
Auto Trait Implementations
impl RefUnwindSafe for EventTypeInputBuilder
impl Send for EventTypeInputBuilder
impl Sync for EventTypeInputBuilder
impl Unpin for EventTypeInputBuilder
impl UnwindSafe for EventTypeInputBuilder
Blanket Implementations
Mutably borrows from an owned value. Read more