EventTypes
Related Doc:
package api
Creates a new EventType.
Creates a new EventType.
The fields enrichment-strategies and partition-resolution-strategy have all an effect on the incoming org.zalando.kanadi.api.Event of this EventType. For its impacts on the reception of events please consult the Event submission API methods. Validation strategies define an array of validation stategies to be evaluated on reception of an Event of this EventType. Details of usage can be found in this external document http://zalando.github.io/nakadi-manual/ Enrichment strategy. (todo: define this part of the API). The schema of an EventType is defined as an EventTypeSchema. Currently only the value EventTypeSchema.Type.JsonSchema is supported, representing JSON Schema draft 04.
Following conditions are enforced. Not meeting them will fail the request with the indicated status (details are provided in the Problem object):
EventType name on creation must be unique (or attempting to update an EventType with this method), otherwise the request is rejected with status 409 Conflict. Using EventTypeSchema.Type other than EventTypeSchema.Type.JsonSchema or passing a EventTypeSchema.schema that is invalid with respect to the schema's type. Rejects with 422 Unprocessable entity. Referring any Enrichment or Partition strategies that do not exist or whose parametrization is deemed invalid. Rejects with 422 Unprocessable entity.
Nakadi MIGHT impose necessary schema, validation and enrichment minimal configurations that MUST be followed by all EventTypes (examples include: validation rules to match the schema; enriching every Event with the reception date-type; adhering to a set of schema fields that are mandatory for all EventTypes). The mechanism to set and inspect such rules is not defined at this time and might not be exposed in the API.
The flow id of the request, which is written into the logs and passed to called services. Helpful for operational troubleshooting and log analysis.
Deletes an EventType identified by its name.
Deletes an EventType identified by its name. All events in the EventType's stream' will also be removed. Note: deletion happens asynchronously, which has the following consequences:
Creation of an equally named EventType before the underlying topic deletion is complete might not succeed (failure is a 409 Conflict). Events in the stream may be visible for a short period of time before being removed.
Name of the EventType to delete.
The flow id of the request, which is written into the logs and passed to called services. Helpful for operational troubleshooting and log analysis.
Returns the EventType identified by its name.
Returns the EventType identified by its name.
Name of the EventType to load.
The flow id of the request, which is written into the logs and passed to called services. Helpful for operational troubleshooting and log analysis.
Returns a list of all registered EventType
Returns a list of all registered EventType
The flow id of the request, which is written into the logs and passed to called services. Helpful for operational troubleshooting and log analysis.
Updates the EventType identified by its name.
Updates the EventType identified by its name. Behaviour is the same as creation of EventType (See create) except where noted below.
Name of the EventType to update.
EventType to be updated.
The flow id of the request, which is written into the logs and passed to called services. Helpful for operational troubleshooting and log analysis.