How did we do?


Define event types and store events.

Event storage in HiveMP is one of the most powerful APIs; it allows you to store custom data for player activities in games, and map this data against time, location or version based series. You can aggregate, compare, manipulate and transform large datasets of events for reporting.

Events require event types to be defined; these specify the format (or schema) of the events that are being stored in the system. HiveMP requires that event types are defined upfront, as it enables efficient querying of the resulting datasets.

The creation, modification and deletion of event types in Hive is not instantaneous. Each request which creates, modifies or deletes an event type is placed in a queue, which is then processed by a background service. The status of each event type can be retrieved through the API so that you are aware of it's availability.

In addition, each event type is versioned. All event types initially start at version 1 when they are created; each modification of an event type increments the version number. When you modify an event type, it will take time for the new version to be available.

If you attempt to store an event in HiveMP where the event data does not match the format (or schema) defined by an available event type version, the request will fail.

Available Versions

Currently HiveMP APIs only ship with a single version, v1. In future, we'll be providing date-versioned APIs.