Enum StoreId

pub enum StoreId {
    Experiments,
    Enrollments,
    Meta,
    Updates,
    EventCounts,
}

Enumeration of the different stores within our database.

Our rkv database contains a number of different “stores”, and the items in each store correspond to a particular type of object at the Rust level.

Variants

Experiments

Store containing the set of known experiments, as read from the server.

Keys in the Experiments store are experiment identifier slugs, and their corresponding values are serialized instances of the Experiment struct representing the last known state of that experiment.

Enrollments

Store containing the set of known experiment enrollments.

Keys in the Enrollments store are experiment identifier slugs, and their corresponding values are serialized instances of the [ExperimentEnrollment] struct representing the current state of this client’s enrollment (or not) in that experiment.

Meta

Store containing miscellaneous metadata about this client instance.

Keys in the Meta store are string constants, and their corresponding values are serialized items whose type depends on the constant. Known constraints include:

• “db_version”: u16, the version number of the most revent migration applied to this database.
• “nimbus-id”: String, the randomly-generated identifier for the current client instance.
• “user-opt-in”: bool, whether the user has explicitly opted in or out of participating in experiments.
• “installation-date”: a UTC DateTime string, defining the date the consuming app was installed
• “update-date”: a UTC DateTime string, defining the date the consuming app was last updated
• “app-version”: String, the version of the app last persisted

Updates

Store containing pending updates to experiment data.

The Updates store contains a single key “pending-experiment-updates”, whose corresponding value is a serialized Vec<Experiment> of new experiment data that has been received from the server but not yet processed by the application.

EventCounts

Store containing collected counts of behavior events for targeting purposes.

Keys in the EventCounts store are strings representing the identifier for the event and their corresponding values represent a serialized instance of a [MultiIntervalCounter] struct that contains a set of configurations and data for the different time periods that the data will be aggregated on.