Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If the data is not aggregated at a daily level, an event could also be shared at a week, month, year level as well by just defining a startDate and endDate.

Code Block
languagejson
{
    "startDate": "2019-01-01",
    "endDate": "2019-02-01",
    "grade": 1,
    "school_id": 901,
    "count": 23
}

...

If you have a requirement to increase this limit, please reach out to us. The lowest bucket_size that cQube would support would be a day.

...

  1. Impact on Datasets

    • cQube Datasets are optimized for query based on dimensions. Indexes are defined as part of the schema.

  2. Impact on Input Data

    • The input data is validated against the dimension data before being persisted.

    • The event schema should always reference a dimension for this to work.

...

  1. How the dataset is defined

  2. How it is liked linked to dimensions

  3. Which fields needs need to be cached/indexed to be queried faster

...

  • counter (def) - allows for aggregations as sum, count, percentage, min, max, avg, percentile

  • Future instruments to be implemented - meter, gauge, histogram.

Assumptions

  1. Since it’s not a frequent use case, Dimension updates and deletion are not supported. In case this is needed they can just create a new dimension, update the mapping to datasets and refresh the datasets.

  2. Event Sourcing is used extensively in the entire architecture, which allows for

    1. Replaying events