Cristian Figueroa

Currently when running analyzer checks previous to join it uses today as of system time. However that will most often be an empty partition since data may not have landed...

## Summary In the current state when an runtime exception is encountered (because the group by serving info is missing for example). The program fails to exit with an error...

## Problem Statement When testing, or debugging it is generally preferable to leave the production tables untouched while outputting data to a "dev" namespace. Having the ability to override the...

## Problem Statement Some of the more relevant stats such as score drift don't require a join to define. They can be defined a streaming aggregation of scores. It's desirable...

## Problem Statement Our compile api tends to limit the scope to the conf in question, this has a negative effect that encourages append only materialized configs and makes deprecation...

## Problem Statement Chronon jobs can run for a long time, can execute multiple partitions, scan large amounts of data in the configuration and sometimes run into skew where 1...

## Problem Statement The lifecycle of fixing data quality issues can be very long. The best way of reducing the turn-around is by making detection as fast as possible. The...

## Summary Release 63 * Using the left in stats for offline backfills. * Docs updates. * Tiling into fetcher. ## Why / Goal ## Test Plan - [ ]...

Hey, I read throught the README and had these thoughts (Mostly thoughts rather than corrections) @ezvz ## Summary ## Why / Goal ## Test Plan - [ ] Added Unit...

## Summary Setting a time limit of 40 minutes for circle CI as metadata calls can run into a 4hr+ loop of failure Example: https://app.circleci.com/pipelines/github/airbnb/chronon/3408/workflows/2fdc3dd8-904b-4d90-b062-d5879f4bd686/jobs/17449 From: https://support.circleci.com/hc/en-us/articles/11775183948827-How-to-run-a-job-in-the-background-on-CircleCI > A job...