Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation on how timestamps are used in Chronon #749

Open
kambstreat opened this issue Apr 22, 2024 · 0 comments
Open

Documentation on how timestamps are used in Chronon #749

kambstreat opened this issue Apr 22, 2024 · 0 comments

Comments

@kambstreat
Copy link

I tried exploring chronon for the past one week with one of the production usecase. Faced few issues in understanding the following

  1. How ts_ds is used in joins ? Looks like this field is created implicitly.
  2. There are many places where date argument is used. Confused on how to use different date args.
  • Source has date param,
  • GroupBy has backfill_start_date
  • run.py has ds, start_date, end_date.
  1. Which partition does backfill starts filling. May be documenting different scenarios might be helpful.

Example scenario. I have a groupBy with backfill_start_date : 2024-01-01 and I gave run.py --ds=2024-05-01 . If I have groupBy output for 2024-03-31 (but do not have 2024-01-01 to 2024-03-30) . From where my backfill will start populating partitions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant